Horrih

joined 1 year ago
[–] Horrih@alien.top 1 points 11 months ago

web-mode is well suited for most web dev.

I used it extensively for vue.js (html/css/typescript in the same file) and it worked well. Pretty sure it should be fine for typescript + jsx

As for the language server, it seems that typescript-language-server is the way to go (see)

Give it a try, i'm pretty sure that those two things will cover 90% of your needs

[–] Horrih@alien.top 1 points 11 months ago (2 children)

For me, it is not the ability to write plugins : most editors have those to some extent.

For me it's more about the ease of writing your own customizations and not be limited to those provided by your plugins.

A few examples

  • don't like some built in or plugin behavior ? Copy paste the original source code, tweak it to your likint and use add-advice to use your new version
  • just yesterday i had some tests which generated a log in a temporary folder, 5 folders deep. I wrote a new command and bound it to a shortcut that looked for the new log file and opened it after running my tests
  • i wrote a simple log browser : use a few commands to preformat the file with query/replace, and boom with emacs' outline mode i can fold sections /subsections. This command is 10 lines long.

The strength of emacs is not its plugins, it's your ease of making it your own

[–] Horrih@alien.top 1 points 11 months ago

This is the way, adress pain points, don't do things for the sake of it.

You will naturally dig deeper in the things that matter to you

If you hear of some fancy new package, read/watch an introduction about it and ask yourself if it would actually solve one of your issues. If it doesn't really, pass

[–] Horrih@alien.top 1 points 1 year ago (1 children)

There was quite a debate on wether it should inherit prog-mode here, maybe the fact that it does not is the cause of what you describe ?

https://lists.gnu.org/archive/html/emacs-devel/2023-02/msg01009.html

[–] Horrih@alien.top 1 points 1 year ago (1 children)

This is the way, for basic IDE features it should be enough.

Treemacs is also useful if you are used to having a left menu to navigate your project files with the mouse like in most IDE

Anything more is about personal preference an customizing your emacs experience.

In this regard, installing a color theme could help you feel at home, for example this one is a dark mode reusing vs code's colors : https://github.com/ianyepan/vscode-dark-plus-emacs-theme

[–] Horrih@alien.top 3 points 1 year ago

Start with vanilla emacs, watch and follow system cafter's "emacs from scratch series"

 

Hello to all, As some of you probably did, i jumped on the treesitter train with emacs 29.1.

I replaced my major modes by their ts counterparts, and gave it a try. For the keywords colors, it was mostly fine, and at first I only checked that and was content with it.

Things went a bit sour when I starting writing code, in particular the indent-rules. I have used mainly the following so far :

  • cmake-ts-mode
  • c++-ts-mode
  • yaml-ts-mode

Over the past two weeks there has not been a work day where I did not have to complete or "fix" indentation rules to my liking.

On the one hand it is much easier than before to tweak things, where either there was a customizable variable, either you were screwed. Now you can add rich rules, kind of easily

On the other hand, the out of the box experience was much worse, barely usable indentation especially for the c++ mode which, despites its 4 presets, lacks the many quick toggles from cc-mode.

I do commend maintainers though for their amazing core implementation, the api + utilities make debugging tree sitter rules a breeze.

How has your treesitter Journey been so far ?