Which code editor do you use ?

Which code editor do you use ?

  • vim

    Votes: 13 38.2%

  • neovim

    Votes: 6 17.6%

  • vscode

    Votes: 8 23.5%

  • other which one ?

    Votes: 15 44.1%

  • emacs

    Votes: 8 23.5%
  • Total voters
    34
  • This poll will close: .
Doom emacs #1 plus occasional use of micro / mousepad and if SHTF then vi when no GUI available.
Once I saw the power of emacs Org-mode / Org-Roam (plus Org-roam-UI) I just had to have it.
Doom emacs allegedly makes emacs easier to use plus adds vi keybindings - to make all vi/vim users familiar.

My goal was to reduce dependency on using the mouse (RSI / time wasted on repetitive actions etc).
As others have said, emacs presents a steep learning curve/cliff, but once you master a few commonly used actions, muscle memory needs strengthening via daily usage.
 
Never used any. It's mostly ee. Only need something else to copy/paste entire lines while the end is out of view. And they should add an option to see current file info instead of the keyboard shortcuts summary. :cool:
 
emacs, nvi, ed only in scripts, not for code.

Not happy, but they are standard, most used, reliable.

I do not want that an editor spoil my text files.

Cthulhux said:
emacs, fallback to sam
Click to expand...

In tty mode would be OK, as a better ed.

I like the ideas of plan9, but it is too mouse dependent, underdeveloped for pure tty as I use it.

I also do not like the background color in GUI.

kent_dorfman766 said:
Where is TECO?
Click to expand...
I had the opportunity to use it with DEC 10, but at that time I used the more primitive SOS.
 
Which reminds me of this https://eclim.sourceforge.net/ , which was a way to run vim as a head on top of a headless eclipse instance. I played around with it years ago... maybe around 2005, I can't remember. It did more or less work, I think. I don't know if the project is still active, but they made a valiant effort, so I thought it deserves a mention. Kind of an interesting thing to attampt, that was really going to the limit to allow you to keep using your favourite editor when the boss said "use this gui!"

Checking the change history, looks like the last updates were in 2016, so it's dead by the looks of it.
 
graudeejs said:
vim/nvim/macvim/vi
And sometimes some JetBrains tools (absolutely great for code Exploring) such as DataGrip, RubyMine, WebStorm, PyCharm

In case it's of interest to anyone, my vim config is available on gitlab https://gitlab.com/graudeejs/dot.vim.
It's been in development for eternity. Lately I started experimenting with importing all vim plugins directly into my config without using git SubModules or anything like that.

4x problems that I'm trying to solve this way:
1) I don't want to fork every plugin that I use (still may do it)
2) Full control of what is configured - no surprises such as missing repos all of a sudden
3) Full control of what is configured - I don't want to install vim plugin to find out that upstream was hacked with all the possible consequences.
4) Just clone repo and your good to go given than all dependecies are installed on system

Last to can probably handled better, bet hey, I'm experimenting currently this works fine for me.
Click to expand...
Nice but, I see some gui stuff in your vimrc. It may be easier to utilize both a .vimrc and .gvimrc file (you can ship just the .vimrc to systems without a vim gui for one example).
 
Alain De Vos said:
tips for init.el are welcome
Click to expand...

Here's mine: Fossil repository.

Programming with it looks like this (on macOS, but it is portable):

Bildschirmfoto 2026-01-11 um 19.43.53.png

But I warmly recommend to start from scratch. Other people's configurations will never match your needs.
 
For instance i have major modes, Clojure, Crystal, Scala, D . But i'll have a look at your script. Maybe i'll just copy the relevant parts.
 
Alain De Vos said:
with doom emacs i have coloring but problems with autocompletion.
Click to expand...
I will take a look at which autocompletion options I have enabled and let you know.

In my doom emacs ~/.config/doom/init.el file I have:
Code: 
(doom! :input
       ;;bidi              ; (tfel ot) thgir etirw uoy gnipleh
       ;;chinese
       ;;japanese
       ;;layout            ; auie,ctsrnm is the superior home row

       :completion
       company           ; the ultimate code completion backend
       ;;(corfu +orderless)  ; complete with cap(f), cape and a flying feather!
       ;;helm              ; the *other* search engine for love and life
       ;;ido               ; the other *other* search engine...
       ;;ivy               ; a search engine for love and life
       vertico           ; the search engine of the future
...

Looks like I have company and vertico completion options enabled.
 
I would say that Emacs is the wrong environment for Vim keybindings and much of Emacs's efficiency is lost with them. I agree that vi/Vim users who want to "just try Emacs quickly" could have a lower entry level by using different keybindings, but that's basically "I use Emacs as Vim", not "I use Emacs".
 
I would say that in 50% of cases I use either ed(1) or ee(1) (these would be console-based editors) and in other 50% of cases I use graphical editor editors/featherpad, but not this editor itself, but rather a huge set of my own patches to it. I took its version 0.16 a couple of years ago and started removing the stuff I don't need and add some stuff I want. Now this is a different program, but with the original editor as the base/core. It's super simple and looks like this:
 

Attachments

  • 22_36_03.png
    22_36_03.png
    18.8 KB · Views: 0
You must log in or register to reply here.
Back
Top