Slashdot Mirror


Comparison: Linux Text Editors

jrepin writes: Mayank Sharma of Linux Voices tests and compares five text editors for Linux, none of which are named Emacs or Vim. The contenders are Gedit, Kate, Sublime Text, UltraEdit, and jEdit. Why use a fancy text editor? Sharma says, "They can highlight syntax and auto-indent code just as effortlessly as they can spellcheck documents. You can use them to record macros and manage code snippets just as easily as you can copy/paste plain text. Some simple text editors even exceed their design goals thanks to plugins that infuse them with capabilities to rival text-centric apps from other genres. They can take on the duties of a source code editor and even an Integrated Development Environment."

7 of 402 comments (clear)

  1. You're welcome to them. by jeffb+(2.718) · · Score: 5, Insightful

    It may not have been wise for me to spend years training vi into my muscle memory, but it's done now, and I'm not especially interested in giving up that advantage.

    1. Re: You're welcome to them. by TheRaven64 · · Score: 4, Insightful

      Code duplication is not free either. Even if execution time is the only thing that you care about, on anything that's vaguely like a modern CPU (GPUs and microcontrollers are somewhat different), instruction cache space is the most scarce resource, with data cache the second. A function call will likely be branch predicted and in an out of order system the prolog and epilog are mostly handled by the register renaming infrastructure, so the function call is almost free, but the cost of an instruction cache miss from having too many copies of the same code is quite measurable.

      --
      I am TheRaven on Soylent News
  2. Pfft by relisher · · Score: 5, Insightful

    You can do all of this in Emacs and Nano. No need for some shiny new text editor...

    1. Re:Pfft by Darinbob · · Score: 5, Insightful

      Ya, I'm surprised by the summary. Apparently the author has not actually used emacs or vim, and instead listed the BARE MINIMUM set of features that any editor should support. Maybe the author came with a pre-existing bias against emacs and vi as "tools for old farts" and assumed any new tools must automatically be better.

  3. What the fuck happened to gedit's UI? by Anonymous Coward · · Score: 5, Insightful

    I used to use gedit on Linux a lot a few years ago. I then used OS X for a few years, but I recently moved back to Linux. One of the first things I did after getting Linux installed was try to edit some files using gedit. And my first reaction was: JESUS FUCKING CHRIST, WHAT IN THE FUCKING HELL DID THEY DO TO GEDIT'S UI?!

    It used to have a good, traditional UI. There were useful menus and a toolbar, and it all worked very well. But now, JESUS FUCKING CHRIST, it looks stupid as all hell. There are no menus any longer, and the toolbar has been castrated into having like 4 buttons. The icons are pathetic, and don't indicate what the button actually does. Whoever the hell reworked the UI managed to break what was once a very usable text editor. Now it's rubbish.

    It's like they took the idiotic UI design of Chrome and brought it over to gedit. And now gedit is useless to me! So I've moved on to Kate. At least the KDE crew hasn't gone completely fucking stupid like the GNOME dipshits apparently have.

    Why the fuck did they have to ruin gedit's UI?

  4. Re:What's there to compare? by zAPPzAPP · · Score: 4, Insightful

    But Notepad(++) is pretty good...

  5. Who else makes this mistake? by rossz · · Score: 4, Insightful

    I have a few text files on my Windows box with :wq scattered around in random locations.

    --
    -- Will program for bandwidth