Skip to main content

emacs typescript eglot

Emacs Typescript setup

I previously wrote an article on settting up Emacs for Typescript projects. It was years ago. I want to test new things..
Searching the Internet for new ways to setup, I found: TypeScript development with Emacs, tree-sitter and LSP in 2022
This did not work out of the box for me. I had to perform several intermediate actions, I do apologize that I dont fully remember everything, but here are what I remind...
Installing tree-sitter requires to have Rust installed before:
    sudo pacman -S rust
corfu did not auto-complete anything, and I noticed that if I read the doc, I would have understood why: default setting does almost nothing. I stupidly switched to company
I dont know if it is related or not... but I installed tree-sitter-cli Node package.
npm install -g tree-sitter-cli
Remid that I was in a try / error loop so I dont really know if this is relevant or not
Finally, this is my setting:
    (use-package tree-sitter
  :ensure t
  ;; activate tree-sitter on any buffer containing code for which it has a parser available
  ;; you can easily see the difference tree-sitter-hl-mode makes for python, ts or tsx
  ;; by switching on and off
  (add-hook 'tree-sitter-after-on-hook #'tree-sitter-hl-mode))

(use-package tree-sitter-langs
  :ensure t
  :after tree-sitter)
(use-package eglot
  :ensure t)

    ;; Ensure Eglot is launched on Typescript buffers
    (add-hook 'typescript-mode-hook 'eglot-ensure)

    ;; Ensure Company is maunched in all buffers (not Typescript only)
    ;; Please tell me a way to make it selective
    (add-hook 'after-init-hook 'global-company-mode)


Popular posts from this blog

npm run build base-href

Using NPM to specify base-href When building an Angular application, people usually use "ng" and pass arguments to that invocation. Typically, when wanting to hard code "base-href" in "index.html", one will issue: ng build --base-href='' I used to build my angular apps through Bamboo or Jenkins and they have a "npm" plugin. I got the habit to build the application with "npm run build" before deploying it. But the development team once asked me to set the "--base-href=''" parameter. npm run build --base-href=' did not set the base href in indext.html After looking for a while, I found where it says: You need to use −− to pass arguments to npm scripts. This did the job! The command to issue is then: npm run build -- --base-href='

Jenkins invalid privatekey

Publish over SSH, Message "invalid privatekey:" With quite recent (June-July 2020) installations of Jenkins and OpenSSH, I have the following error message when using the "Deploy overs SSH" Jenkins plug-in and publishing artifacts to the target overs SSH: jenkins.plugins.publish_over.BapPublisherException: Failed to add SSH key. Message [invalid privatekey: [B@d8d395a] This problem seems to be referenced here: Just regenerate a key with the right parameters To solve it: ssh-keygen -t rsa -b 4096 Or ssh-keygen -t rsa -b 4096 -m PEM

Emacs Pulumi LSP

Install Pulumi Emacs Mode The source code is on At the very bottom of the page are the instructions on how to install. You Need to have make installed. $ make install emacs-client mkdir -p ./bin go build -ldflags "-X" -o ./bin -p 10 ./cmd/... go: downloading v3.53.1 ... ... ... go install -ldflags "-X" ./cmd/... mkdir -p editors/emacs/bin cd editors/emacs && emacs -Q --batch --eval "(progn (setq package-user-dir \"$(pwd)/bin\" \ package-archives '((\"melpa\" . \"\") \