Coders or lemmy, what editors do you use? Is it worth learning a new one?
-
I use either the default GUI text editor from each distro or Vim with stock configuration. I must say it does take surprisingly little to get up to speed with Vim, but I still struggle with specific things like moving code across files.
I haven't changed any keybindings in firefox, but heard qutebrowser is nice for such use case.
-
VS, VSCode, Sublime, Neovim,
I use Sublime for short scripts in Python, VSCode for angular|typescript, VS for c# and neovim for elixir, elm and all new stuff I learn on my own.
-
-
Yeah, keybindings are well thought out. The most off-putting thing of default vim is that there are about 5 different "delete" commands. One for a character, one for the whole line, one for selected text, one for end of line. In helix, this is all just "delete selected text" and then "x" is for selecting a line. Make so much more sense.
-
was concerned about missing out on learning more standard vim bindings and functionality.
What do you mean? Do the standard vim bindings have some specific quality that you are after?
Or do you work with many different servers and would have to use what ever editor is installed there? -
Well, I've successfully used LSP for Sublime Text before. Would probably still use it if I hadn't transitioned to Neovim recently.
-
I use Helix
TLDR: Yes I think helix is worth trying out. It has some missing features but it is an amazing piece of software.
Yes I use helix daily. It is very fun to use and you can do many things faster. It is particularly good when navigating a (large) codebase you know fairly well. You are able to jump around and find/edit relevant code very quickly.
Compared to vs code:
- it is much faster and more minimal
- It might be harder to get things up and running than in vs code, e.g. to get auto-completion working in helix you need to have the LSP for that language installed. It can be a bit confusing if you have never done it before but it is easy once you have done it a few times.
Compared to neovim I think it is:
- easier to learn
- slightly faster - especially with large files
- you will have a much smaller/simpler configuration. AFAIK Helix has more features working out of the box than neovim (file picker, lsp support ect) and needs less configuration to get things to a workable state.
The downside of helix compared to both neovim and vscode is that it does not have plugin support yet so you will need to use other tools in combination with it to get an equivalent experience. Here are some tools that are commonly used with helix:
- yazi - terminal file manager
- gitui or lazygit - terminal git user interface
- zellij - terminal pane manager
Helix really shines when performance matters. I have edited files with millions of lines and had no trouble on codebases where my colleagues IDE's become very slow.
I recommend you use the tutor (
hx --tutor
) for a few minutes each day to learn the keybidings. -
On windows i use vscodium, on linux neovim.
As others say i think helix is cool, but the limited customization is kind of meh for me. I love the keybinds for it though.
-
I use Emacs and love it. It's an amazingly frustrating (and just plain amazing) piece of software, but it's hard to move away from it because it's the only thing like it. Maybe if Lem every gets mature enough I might switch.
I probably wouldn't recommend it though as it's doesn't sound like what you're looking for.
-
That's how I ended up with a latex plugin for intellij
-
Doom Emacs and lazyvim nvim.
Don't know about helix, and don't really care.
Modal is incomparably more comfortable, that's the main benefit.
The problem that I have is that learning new editing keybindings would probably take me a month of time, before I get to the same amount of productivity
Do you imagine vi-based editors don't let you use your mouse or what? Go through vim-tutor, learn the basic shortcuts you need, and you're back to your old productivity in a few days. You don't need to learn vi" to select a string, you can just use your mouse.
No offense to you or your habits, but C-arrow is an idiotic movement scheme. If you have to leave the home row to move around the text, you fucked up.
Just go through vim tutor...
-
A coworker has told me that in a previous job, he was talking to an intern and mentioned IRC and intern asked what was that. He told him that it is the "old instant messaging", which another senior coworker overheard and chimed in that "no, IRC is the new messaging thing".
If someone would be asking be what netbean is, I'd say "an IDE from the old generation of editors", but I guess that is all relative
-
Modal editing for just raw text input would actually be slower, because you also enter and leave Insert Mode. I find it's very fast and powerful for navigating around the text, which you probably do a lot more than actually editing it. And when it does come to editing, there are a lot of higher-level tools (at least in Vim) for accomplishing things more quickly, like the 's' command and 'q' macros.
I think getting into a mental "flow" state is really valuable, and muscle memory is important for being able to stay there. If your muscle memory is to navigate around using the mouse, that's great, but Vim feels faster to me.
-
I happily use Helix for Rust, etc projects, and as a general editor. I switch back to VSCode for TypeScript/Svelte projects because the plugins make it more productive for me. I do miss the editing experience and need to check if there's a VSCode plugin that lets me not confuse my muscle memory.
Helix was the thing that finally made me remap my
tab
key toesc
. -
I keep hearing about how modal editing is faster
I've always been skeptical that optimizing text input speed would make a significant difference to overall performance. IMO if you are unhappy with your setup then look around but if you're not you don't need to have FOMO about it.
-
Well I was mostly looking to learn vim and was trying to use Helix as a way to do that because it looked like vim, but with a commands window that popped up to help learn the commands. They're upfront about making some breaking changes from vim though, and while I may not need to jump into a bunch of different machines that often I do like the flexibility of being able to hop into vi, vim, nvim, or some GUI editors with vim bindings relatively comfortably. So I found that LazyVim was more what I was looking for personally and nearly as easy to work with out of the box.
I am glad to see the project seems to be going strong. That was another minor concern of mine, there's little risk of vim going anywhere, but I remember being excited about the Atom editor a while back and that just kinda faded away. If it passes the test of time I'd be happy to try it again in the future. I figure it would be easier to go from vim -> helix than vice versa.
-
That's the thing: I do feel vscode being slow. On my work machine, it's fine - it takes about two seconds to open a project from start. But on my older laptop, that's a solid 10 sec before I can start editing.
-
Sublime Text.
The only thing I need from my editor is syntax highlighting and not be slow.
(Assembler, C, Python, Java and Bash are the languages I mostly work with)
-
-
Panic Nova on macOS, VSCode on Windows, neovim in the Shell.