Shared publicly  - 
 
Linux users: What's your favorite programming text editor?
8
5
Jonathan Landrum's profile photoMuhammad Azeem's profile photoRobert MacAnthony's profile photothe Krev's profile photo
116 comments
 
It depends on the task, vim for small tasks or emacs for regular expression replacements spanning lines.
 
I use Geany the most, but I've come to like Bluefish recently.
 
I basically use Nano...don't know why, but it's easy to use and I'm not a programmer.
 
+Shawn Dreelin you can find almost every nano shortcuts on Emacs.

I personally actively use vim. Vimscript is just awesome for developers.
 
I am on Mac. For scripting tasks I use nano and vim.
 
Kate. Quick/minor stuff in Nano at times.
 
It's been a long time, but I used to be a die-hard vim user. If I'm ever on a Linux machine again, I'd love to go back to it.
 
Komodo Edit - Cross Platform, and I can sync it with Dropbox so I can work from my laptop or desktop; as a web developer, that's important.
 
Vim and the busybox build of vi for embedded systems.
Translate
 
Geany for GUI or Vim for the command line.
 
Kate for the basic stuff, Eclipse for the advanced
 
It seems these questions are mainly to get replies, since you would do a post for contenders if you really wanted to know. I use linux all day long through a little black window, so I primarily use vim, irb or straight bash. Are you asking people who use it functionally or people who use one of the desktop versions?
 
gedit, when extended with plugins, is a very powerful text editor.
 
Vim all the way, for everything. Once you get past the quite considerable learning curve, you can fly through anything as your hands never leave the keyboard. I actually write about 99% of my code with vim. The only exception is eclipse for java, which is rare.
 
Kate or vim depending on the task
 
I really want the geek cred that goes with having mastered vim, but I use nano at the command line and gedit from nautilus.

As an aside, I'm impressed by the absence of flaming in this thread. Anywhere else, the "which editor" question qualifies as inciting a riot.
 
I use it for web development rather than programming: Sublime Text 2. It's like the Chrome of the text editors.
 
Sublime Text 2 is without any doubts the best editor I've ever used in any platform.
 
at the moment I'd say Gedit for Linux and Notepad++ for windows. Scratch is good too :)
 
If I want a gui, Scratch from the elementary project :)
 
Geany, vi when on tty
 
The best part of all these responses: It shows just how versatile Linux is :)
 
I use Mac and Linux (Ubuntu). On Mac, I use vim for Python coding, and Text Edit very occasionally. I tried gedit for Mac, but it was too glitchy. On Linux, I use vim, and gedit (which I find works much better than the Mac version...)
 
Very usable in console editing is mcedit from mc (midnight commander)...
 
nano for now.
but one of these days i'll go all the way to vi(m) or emacs.
 
I used to use FTE back when I was running OS/2. I think the developers lost interest. It was a nice editor.
 
KDE Kate for general text editing and small programming, KDevelop for work on larger projects, in text mode I use nano and Emacs
 
Nano for quick edits (usually tweaking Arch config files and such), gedit for larger stuff.
 
gEdit to get all the small stuff done.
Eclipse for all the serious java/android stuff...
 
geany. Baisc IDE with good highlighting and execution features.
 
Thanks for this thread! I was a vim and geany user who had never heard of Sublime Text 2 before reading these comments. I just tried it and found it to be magnificent.
 
For awhile it was emacs, but over the last year or so I've been using vim. It's (vim) more lightweight and seems a bit more seamless with the console. 
 
Vim for command line
Kate for code
Leafpad for general text
 
Vim for bash / C++ 
Eclipse for Java
Gedit for Python / HTML / CSS

Hearing great things about Sublime though.
 
Notepad under WINE.

Not really, just vim.  Sometimes I have to open a file in gedit, but that's usually for prose, not programming (but I only really program in bash, though I'm beginning to dabble in Python and C).  I messed about with Geany a little, but I couldn't see any advantage over VIM.  Plus, vi is such a huge part of *nix culture that the bindings are useful for many other terminal apps and even many gui apps.  At the moment, my browser uses vim-esque bindings, as does my file manager, my music player, my window manager, my terminal multipexer, my command shell, etc...  once you begin to live in VIM bindings, you only really need the mouse of those few GUI apps you can't do without which, for some stupid reason, can't be made to act like VIM.
 
Sublime Text really does it for me.
 
Kate is simply amazing as both a simple text editor and a programmer's text editor. It has no learning curve but it's so powerful if you do learn its advanced features. Support for about 180 types of syntax highlighting, fast find-in-files support, brilliant handling of several open documents, code folding, split pane view, bracket highlighting and soon to come minimap view (similar to sublime). It's one of the few classic KDE apps that has not degraded with age but has actually improved. I even use it on my windows boxes (via KDE for windows) because it blows away any free windows editor i've ever used (including notepad++).
 
I do not appreciate huge overhead in a program as simple as a text editor, so GUI is usually a deterrent for me. I like speed and syntax highlighting. So my faves are Nano, vim, and gedit. Gedit for more complex tasks like mass-tabbing, find/replace, etc that I can't figure out how to do in Nano/vim.
 
+Braden Best , If you  want to indent a section in vim, hilight the section and hit ">" to add a level of indentation, or "<" to remove a level.

Google will tell you anything you want to know about vim. If it fails, #vim  on irc.freenode.net will have someone who knows.

Everything is in the documentation too, of course, but it can be difficult to find things there until you get a bit more familiar with the terminology. Believe me when I say that vim can do anything gedit can (or any other editor, for that matter).
 
+Aaron Christianson Yes, I realize vim is a powerful editor that can probably do more than a GUI editor ever could, and I use it and nano as my primary text editors. Still trying to figure out which I like more. I mean, the whole reason I looked into these is because, by common sense, CLI/TUI is inherently faster than GUI, and for something like a text editor, I believe it should work fast. #1 priority for me. I am pleased with how fast they are, and, being a programmer, the syntax highlighting makes it almost too good to be true.

Anyways, there are a few other things I have to say after experimenting with the command:

1) It should be noted that you have to be in command mode when doing this, and the command is ":>", not ">".

2) It should also be noted that you can use ":>>" to space twice, ":>>>" to space three times, etc.

3) After spending some time experimenting with variations of the command, I found that ":>n" will tab n lines after the current line (inclusive).

Also, is there a way to show a line count?
 
Eh, :> also works, but it also works in visual mode with just >

edit: you can see a line count and other useful infor with  g<C-g>. The info bar is also very customizable, and I'm sure you could get it to show a line count, but I've never done anything with that...

But I'm sure you would have an answer in a second if you put the question in a search bar.
 
+Aaron Christianson That's what I tried at first, and it was buggy as hell. I found when I tried it as a command was when it finally worked.
 
+Aaron Christianson Yeah :/ I even had to explicitly install the vim package (even though vim already exists as "vi") just so I could edit text in the friggin' thing without having every keystroke (including arrow keys) insert stuff like "^]" into the document, making it impossible to write text. I did test this; I 'sudo apt-get --purge remove'd it, and then tried to use vi (which just opens the native copy of vim), and every keystroke did the same thing that they did before I installed the actual vim package.

Also, I found that you can search using ":/[regexp term]", and jump to a specific line with ":n", where n is the line number. This begs the question: is there a way to show the line numbers to the left of each line? And is there a command to jump to the very beginning and end of the document (and not just the beginning and end of the page)? In fact, I can just use ":1" for the beginning, but what about the end? There has got to be something like ":end" that goes to the end of the document. That seems to be the only basic operation I'm missing. In any GUI text editor (including the <textarea> I'm typing in now), that would be Ctrl+End
 
If your on ubuntu or debian, vim is vim-tiny. This is basically a vi clone that uses the core of the vim runtime components. It's not big-boy vim.

line numbers:
   :set nu
(or add 'set nu' to your vimrc)

jump to top:
    gg

jump to end:
    G 

you can also line jump to a specific line without using command mode using:
   [count]G
 
+Aaron Christianson Whoops, I updated my comment before I saw your reply. Yes I'm on Ubuntu, and I'm running vim/vim-tiny via the terminal. Thanks for the info.
 
if you want to jump to the end of the document in command mode, It's ':$'
 
+Aaron Christianson nice, and it's something I recognize from regular expressions, so it makes a lot more sense than G. Thanks again!
 
G is for "go" as in "go to line N". It just defaults to end without an argument. This is faster than :$, but I guess it isn't any faster if you can't remember it.
Add a comment...