If you edit python, Atom would be suggested. Which editor is "best" quickly becomes a personal choice based on the type of file editing you do. There are a bunch of middle-of-the-road editors like Atom, Geany, and almost 1 for each major scripting language. Spell checking is a dangerous thing in config files, however. Those are a little like nano, but with a few more features, like spell checking. Then there are the minimal GUI editors like GEdit, Kate xedit, pluma. GUI editors tend to become bloated as the development team decides to add one more menu or one more menu item to the feature list. Unix/Linux servers typically do not have any GUI, so for people who do server work, none of those are worth our time. All GUI programs, including editors, have the same fatal flaw in that a GUI is required to use them. To the OP: There are GUI editors and terminal editors. but that didn't provide the background for using vi/vim. I had been programming on DOS, MS-Windows, OS/2, MacOS and TSO/ISPF for years. I had no Unix background at the time and the idea of a modal editor was completely foreign to me. The first time I used vi, I had to power off the computer to get out of it. Vim is as tiny as you like or as huge as you like thanks to the addon capabilities.īut, someone who thinks they've been hacked might think vim was part of that hack if they didn't know any better. But I've never seen notepad on any router. Trying to use it will just send you screaming from your keyboard and running for the tranquilizers.Īll true. Given that you are inquiring about a Windows notepad clone, I can confidently say that Vi/Vim is not in the running. I consider myself a Linux power user and I cannot get used to it. The only point that I will contest is that of TheFu's. Combined with the use of the aforementioned multiplexer and such delicate surgery can even be done quite safely. Moreover, getting used to command line editors has further benefits: it has allowed me to remotely edit configuration files in distant servers that have no graphical user interface. Mind you, nothing like this has happened for going on 10 years, but I'd rather be safe than sorry. I don't want the file to be left in a corrupted state should the graphical environment go down. I use this strategy when I am working on critical system files. Another example of superior Linux versatility, safety and power. You could even kill your graphical session on purpose and not have your editing session compromised. If you run graphical editors like gedit or mousepad, then in the event your GUI dies they will die just as completely as notepad does when Windows crashes.īut if you first launch a command line multiplexer like screen or tmux and then run a purely command line editor like nano within it, then even if your graphical environment crashes, you can almost always reattach to the multiplexer session without losing your work. I just had to relaunch the graphical environment without having to reboot or even logout/login. On the few occasions when my graphical environment has crashed, I have found that that foundation was still fine. In contrast, in the Linux world, the whole graphical environment is just a pretty dress that rests on top of a much more solid foundation. You have no choice but to reboot and mourn the work that is now just scattered electrons. In the Windows world, when Windows crashes, all is lost. While I can't say that notepad in and of itself has crashed on me, it has died and lost my unsaved work when Windows itself crashed. But let me try instead to address the context behind your question. I have nothing to add to those good suggestions. Others have answered you directly and given you some alternatives.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |