Closeted bear, you say ? 👀

Does it need to be a new piece of software though?

I’m thinking it might be a lot easier to put some effort building a professional community on Mastodon (maybe on it’s own instance) than building it from scratch as a new platform.

Sweet! It’s actually my main language. C mode is built-in so no concern on that side.

Some general advice:

• I leaned it way too late, but you can use M-x compile and then type your build command (make clean && make all) instead of using a terminal to compile your project.
• Try to learn a bit about Makefiles, it’s useful. Avoid cmake like plague.
• C is great for embedded, so you should look up TRAMP if that’s your use case; it basically removes the need for SSH-ing from a shell.

To have Emacs behave like an IDE:

• Install clang17 clang17-extra-tools bear on the host system.
• Configure eglot and company in your Emacs config:

(use-package eglot)
(add-hook 'c-mode-hook 'eglot-ensure)
(with-eval-after-load 'eglot
  (add-to-list 'eglot-server-programs
               '((c-mode c++-mode)
                 . ("clangd"))))

(use-package company)
(add-hook 'after-init-hook 'global-company-mode)

• Use the bear tool (ex. bear --config bear_config.json -- make all) to make the non-trivial project understandable by Emacs. Since it re-uses your Makefile, it even works for cross-compilation!

Good luck!

Okay so here’s the thing: Emacs runs best on Linux and MacOS (allegedly, bc UNIX-like) but it is more difficult to make it do what you want on Windows (afaik, never tried this). You’ll probably need WSL.

So if you have to stick with Windows, I’d suggest to search specifically for configurations and advice from other people who have done this. It will give you a base for installing and probably running a custom configuration.

From there, that my point 2), you should focus on trying and making YOUR workflow to run in Emacs. I really suggest to focus on one thing at the time and configuring it until it works the way you want. Otherwise you’ll end up with many half-backed systems and that’s frustrating.

What is your main use-case then? Maybe I can give some more precise advice if I’m familiar with it!

Interesting for sure, but I would not recommend going for most of these packages unless you are already very familiar with Emacs.

Here are the steps I would recommend if you find motivation to learn the editor:

1. Install it, learn the basic use and navigation
2. Focus on learning and configuring it for your main use-case (writing code in a specific language, taking notes, writing papers, playing Tetris, etc.). This might take a while.
3. Question life, re-try VSCode and get instantly grossed out.
4. ???
5. Try weird packages, moving most of you digital life inside Emacs.

Enjoy =)

Thanks Satan, very cool ! 😎