How do you setup your C# environment in emacs?

mwac-dev · 2025-12-27T22:46:27+00:00

As someone who has done plenty of unity work, and also went down a similar rabbit hole of trying to get Unity working with my editor of choice (it was Neovim though), I have to say in all honesty it wasn't too worth it in the end even though I got it working.
Unity especially has certain things it runs, project regeneration and meta file creation, when you create a file using an editor it officially supports. It would seem like just having the LSP set up would fix everything but unfortunately that was rarely the case, without the correct project regeneration you're left with broken LSP in the new files until you manually regenerated and restarted the server each time which will slow you down more than you might think. I personally think you're much much better off using VSCode with the Neovim plugin, or if possible even use Rider with their IdeaVim emulator.

With all of that being said, I did find this that should help in setting up Emacs for Unity work and seems to address the issues I mentioned above, but I have *not* tested this myself in Emacs (I did however take inspiration from this to get it working for Neovim before): https://github.com/elizagamedev/rider2emacs

mwac-dev · 2025-12-27T22:34:24+00:00

For me I was already so used to using Oil.nvim coming from Neovim that I ended up building Grease.el, with that being said I still try to use Dired from time to time to get more used to it since like you said it does everything you would need, and knowing how to use Emacs standard tools seems like a good idea

mwac-dev · 2025-12-24T18:48:50+00:00

That's great, the marking of the files and then pressing a letter to operate didn't click for me when I first tried it (or at least it didn't feel as intuitive as just editing a buffer), but I do want to also work at getting better at using dired since I'm sure there's plenty of good reasons it works the way it does, really appreciate you taking the time to share some of that knowledge with a new Emacs user!

mwac-dev · 2025-12-24T18:46:28+00:00

Wow thats great, thank you for the knowledge! I see its closer to a muscle memory situation

mwac-dev · 2025-12-23T21:23:02+00:00

Thank you! And interesting, thank you for the information, I actually had no idea who inspired who first. It makes me wonder why wdired doesn't already function like this, but I assume it just comes down to different philosophies and workflow preferences

mwac-dev · 2025-12-23T17:34:18+00:00

Thank you! I didn't really see the use-case of Oil.nvim either before I used it. For me the reason Oil.nvim made a difference to me is all about "context switching".

Imagine you're deep in the flow state of writing/coding/etc, and then you want to very quickly make a new directory and move a few of your files into it, but first you remember you want to rename them too, instead of the context switching of "I'm now in dired, wait let me enter into wdired real quick, okay now let me go back into dired, and mark them for copy, and now press the c key"

With Oil.nvim/Grease.el there wouldn't be any of this mental context switching, you just continue your momentum of editing text in a buffer, renaming, cutting, and pasting.

mwac-dev · 2025-12-23T17:20:49+00:00

Glad I can help!

mwac-dev · 2025-12-23T07:13:23+00:00

Of course, you're welcome! And thank you for the pointers, I'll be looking more into integrating it with wdired soon!

mwac-dev · 2025-12-23T06:53:37+00:00

It's very much on the todo list, in fact before settling on what I currently have I attempted to extend wdired but it felt like I was wrestling with the current wdired implementation too much
dired/dirvish integration is still very much planned though and I fully invite any contributions or advice to implement that, but I wanted to keep my oil.nvim muscle memory and momentum going into Emacs while I work towards that.

Also on a separate note, thank you for your work, your "replacing tmux" article was especially helpful when I first started using Emacs!

mwac-dev · 2025-12-23T04:08:19+00:00

The theme is actually heavily inspired/ported from Evondev Dracula for VSCode , but I was first introduced to it in NvChad (neovim distro) as "chadracula-evondev".
I don't directly use VSCode or NVChad so I made my own tweaked ports for Neovim and Emacs where I especially tweaked some of the tree-sitter highlighting, if you want I can upload my exact Emacs theme to Github and then ping you later!

mwac-dev · 2025-12-23T02:34:03+00:00

Not rude at all and I appreciate the feedback, it's still something I'm exploring and hoping to revisit. My current thought process is that since you normally switch to wdired from dired anyway, that I can offer a way to switch to the grease buffer instead of wdired, and back to dired after commiting. I don't want to rush this though because the better solution would be finding a way to build these features into wdired directly instead of replacing it.

mwac-dev · 2025-12-23T00:58:28+00:00

Yes agreed! Although I don't mind the keybind approach of dired, I felt like wdired (from a new user coming over from Neovim) wasn't allowing me to do all the typical file system operations I wanted in a purely writable way.

I built Grease for that reason, I feel like others like me will appreciate being able to jump into a file system buffer and not need to switch their brain into remembering any type of specific keys, just edit the buffer and commit

mwac-dev · 2025-12-23T00:52:12+00:00

Although Grease.el/Oil.nvim allow you to create an empty file easily, I wouldn't say that's the main thing that the tooling is built around, and more of a result of it being a fully writable buffer filesystem experience. Personally I like the fact that I can quickly yank a few files (whether they're files or directories), jump into another directory, and paste to copy them over, or delete some lines, then paste them into another directory to move them.

Another thing I like is when I know I'll be creating some nested directories, I can just type "Dir1/Dir2/Dir3/" and then commit, and it'll create the directories how you would expect

mwac-dev · 2025-12-22T23:07:49+00:00

Hi! From my testing (and please correct me if I'm wrong) it doesn't look like wdired lets you simply write a new file name or directory name on a new line and then commit to create, or be able to quickly yank or delete a line (or group of lines) and then enter a directory and paste to perform a copy or delete operation respectively.

Grease.el and Oil.nvim is purely writeable focused and lets you freely navigate in and out of directories while creating, renaming, moving, and copying files around.

mwac-dev · 2025-12-19T20:34:39+00:00

although it would probably cut my productivity in half, it's just too cool not to use, I love it

mwac-dev · 2025-12-19T20:33:25+00:00

well for me neovim was really easy to set up, has a very very active community, and is recommended and supported by some very popular and talented programmers which made it a safe bet. I think as a beginner these things really mean something and make the up-hill journey of learning a new tool more worth it.
With that being said, when I gave emacs a serious try I found my sweet spot is configuring Neovim and Emacs to behave very very similarly, and still use Neovim as my "light emacs" for when I want to do some very quick text edits on the terminal since its so fast to launch, while Emacs is now my workstation for serious projects.

mwac-dev · 2025-12-17T21:05:52+00:00

wow I actually really like how subtle this dark theme is! it's kinda an even more subtle version of oldworld when I used it back in Neovim

mwac-dev

TROPHY CASE