I can tell you what editors I use, but I really think you are interested in GUI productivity. I only use GNU/Linux desktops and hope my advice is helpful.
fastest: cat | less fast: vi fast gui: kwrite fast and nice gui: kate nicer gui: bluefish and others for specific tasks. Kwrite is like notepad and is faster than gedit but not "instant". Kate is like notepad with syntax highlighting and session management. It remembers what files you are using in the session name and you can run more than one session at once. The editor window has a concealable file system and document browser and tabs. The file list is saved to the session automatically. For all of that, it's still fast because it's still just an editor. Virtual desktops and stability are the crowning glory of GNU/Linux GUIs. If you have a group of files you need to edit often, you leave them open in a kate session on a virtual desktop. That way you don't have to worry about start up times, you work is just there waiting for you when you need it. I've got two coding projects, a log and a thesis I'm working on but I don't do everything every day. Each coding project has a kate session, the log has bluefish and the thesis is another editor. Each has thing has it's own desktop with nine screens where all of the supporting programs like browsers and spreadsheets are laid out. If something bad happens and my window manager barfs, most of the place keeping is done in the sessions and project management of the specific editors. E16's pagers makes it very easy to find everything is fast and looks good too. The E menu system is not the best, so I also run the kicker. I would pull my hair out if I could not lay everything out in such an easy way to find or I had to boot more than every few weeks and have to remember what I was doing. On Friday 02 February 2007 09:10, Joe Fruchey wrote: > okay, okay, you got me. > > Howabout a gui editor? I never could get into vi, or even emacs. nano > -icKx for me.
