Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am new to linux and tried few editors (vi/nano). Currently use nano but still little off from dos/windows world.

Which is the easiest editor in linux(ubuntu) for windows person?

share|improve this question

closed as not constructive by voretaq7 Feb 8 '12 at 4:47

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

For what purpose? While I agree with vmfarms that its usually worthwhile learning vi (or even emacs) there are a lot of code editors out there which are very good (although personally I still prefer vim) – symcbean Aug 27 '10 at 10:12
Command line, GUI or both? – John Gardeniers Aug 30 '10 at 8:49
Personally, I like ed – ringø Sep 1 '10 at 4:33
Command line... – mamu Sep 8 '10 at 19:26
up vote 11 down vote accepted

You can try joe or nano. They are pretty straight forward and easy to use. Although I suggest putting some time into learning vi or vim, as they can be quite powerful and make you wonder how you got along without it (in my opinion anyways).

share|improve this answer

Graphical one: gedit, it's the default text editor in Gnome/Ubuntu. If vi is too complex, maybe you can try its simpler, creamy version, Cream. It's pretty cool :)

share|improve this answer
Wish there was a way to embed this to terminal/bash.. – user19725 Aug 30 '10 at 7:18

Be careful with nano - it doesn't always handle word wrap correctly, so config files that expect things to be on a single line are sometimes wrapped in nano and treated as two separate lines.

Vi/Vim does not exhibit this behavior and is also the defacto standard for other reasons as well including plugin support, scriptability, etc. If you try and adapt your Linux experience to be more like Windows, you will be disappointed. You should make a real effort at "doing Linux the Linux way" and trying to get familiar with the core userland applications.

share|improve this answer
The nano problem can easily be fixed with the -w flag. But forgetting it can be a sure way to kill your config files. So if you use nano, make sure you alias it to nano -w – Wolph Aug 27 '10 at 3:55

This question is likely to garner very subjective answers. Personally I wouldn't look at it as an exercise in finding something similar to DOS\Windows but look at it as an exercise in learning the Linux OS, shell, and applications that you've chosen to use. Just as you had to learn DOS and Windows when they were new to you, you've got to learn Linux if you want to travel that road.

share|improve this answer
Linux is opensource and probably has 100s of different options, learning linux and learning editor are two different things – mamu Aug 27 '10 at 3:28
mamu: I disagree. Try using "more" or "less" without knowing any of the vi keystrokes. – Christian Paredes Aug 27 '10 at 18:48

I would recommend "mcedit" (Midnight commander) for a windows person.

share|improve this answer

nedit was very popular with the ex-Windows programmers last time I worked at a Unix software house, which, admittedly, is getting on for a decade ago.

From its Wikipedia entry: "It has an interface similar to text editors on Microsoft Windows and Macintosh, rather than to older UNIX editors like Emacs".

share|improve this answer

Working on the asusmption that you're working on the command line I see 3 main alternatives.

  1. Use a simple editor (I prefer pico)
  2. Use a complex and difficult to learn editor, such as vi or emacs (definitely not recommended for casual use but very powerful if you're prepared to learn them and use them frequently enough to remember the key sequesnces)
  3. Use your preferred Windows editor

Option 3 may sound a little strange but is in fact my personal preference. I've bee using the same editor (Boxer) since Windows 95, and the DOS version of the same prior to that, and don't see any reason to change. So, when doing anything beyond the most elementary editing of Linux files I connect from a Windows machine using WinSCP, in which I have Boxer configured as the default editor.

share|improve this answer

I use nano and I am yet to need to use anything else.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.