Quote:
Originally Posted by sivaextralarge
1. For how long have you worked as a programmer?
2. Any particular programming languages you mostly use?
3. For what purposes?
4. Which text editors do you use?
5. What defined your choice?
6. Which text editors you might have been using before?
7. Do you follow the other text editors updates?
8. Which text editors you DID NOT like? Why?
9. What functions might some text editors be missing in your opinion?
|
1. About 30 years.
2. Assembler, C, C++, Forth, Java, Perl, PHP, Python, VisualBASIC, PICBASIC, BASCOM AVR, Spin.
3. Application, embedded application and web development.
4. vi, Emacs, DOS Edit, Notepad(++), WordPad, Word, LibreOffice...and more.
5. Whatever gets the job done.
6. ed, edlin...far too many to list.
7. Some of the editors I use have syntax tools for programming I download the updates. It's a text editor: like a typewriter with less correction fluid.
8. Gripes: text editors that break *nix/Windows end of lines, text editors with obvious bugs, text editors with inconsistent interfaces over platforms, text editors that do not offer line numbers as an option, text editors that can not print (with line numbers), text editors that do not number pages when they print, text editors without macros, text editors that do not offer backups as an option, text editors with no undo, text editors with no redo, text editors that embed codes that I can't see, text editors that puke on ALT-255, text editors that don't understand ANSI, text editors that convert my code to something other than text without option to do otherwise or always bugging me, text editors that don't make timed backups, text editors that don't line wrap within margins, text editors with non-optional syntax correction, text editors with no facility for spell or syntax check, text editors that are expensive...need I go on
?
9. Most text editors can not open a file that is extremely large (I wrote my own for this purpose). Many text editors lack a pull out character table for ASCII characters.