Difference between revisions of "Talk:561: Well"
| Line 6: | Line 6: | ||
What is ironic is that I am setting up a keyboard based on [https://github.com/michaeldickens/Typing Michael Dicken's optimizer]. Also, while I prefer vim (light weight!), I also have Xemacs out of my own choice. [[User:Greyson|Greyson]] ([[User talk:Greyson|talk]]) 20:37, 24 December 2013 (UTC) | What is ironic is that I am setting up a keyboard based on [https://github.com/michaeldickens/Typing Michael Dicken's optimizer]. Also, while I prefer vim (light weight!), I also have Xemacs out of my own choice. [[User:Greyson|Greyson]] ([[User talk:Greyson|talk]]) 20:37, 24 December 2013 (UTC) | ||
| + | |||
| + | The uncomfortable truth is that both emacs and vi are quite difficult to learn, just in different ways. | ||
| + | |||
| + | Emacs, after you learn it, allows you to write the highly flexible macros for the text processing but requires to type some very long command names to do most things. Being largely written is Lisp, historically Emacs had also been very slow and memory-hungry but with the modern computers it doesn't matter any more. Oh, and Emacs messes up the proper Tab characters, replacing them with spaces. | ||
| + | |||
| + | Vi doesn't have this flexibility but has a built-in set of commands extremely well suited to editing the programs. Vi is well-suited for the remote administration because it works well even over the very slow and high-latency connections and allows to do everything with just the alphanumeric keys, thus working even when the handling of the function keys (including arrows ans such) was not set up correctly. One of the newer versions of vi, vim, allows to do some very extensive programmable text manipulation, getting closer to Emacs in this respect; and vim can be set up to mess up the Tab characters just like Emacs. [[Special:Contributions/108.162.246.5|108.162.246.5]] 21:58, 31 January 2014 (UTC) | ||
Revision as of 21:58, 31 January 2014
Shouldn't we elaborate on the questioned superiority of DVORAK? --129.206.196.49 20:45, 11 October 2013 (UTC)
The final two frames appear to be foreshadowed by the title text within Connected (http://xkcd.com/807/) Lakeside (talk) 19:02, 4 November 2013 (UTC)
I like how the 'uncomfortable truth' for the man is that he never meant it when he said 'I love you', but for the woman, it's that she always did! 108.162.219.223 23:47, 23 December 2013 (UTC)
What is ironic is that I am setting up a keyboard based on Michael Dicken's optimizer. Also, while I prefer vim (light weight!), I also have Xemacs out of my own choice. Greyson (talk) 20:37, 24 December 2013 (UTC)
The uncomfortable truth is that both emacs and vi are quite difficult to learn, just in different ways.
Emacs, after you learn it, allows you to write the highly flexible macros for the text processing but requires to type some very long command names to do most things. Being largely written is Lisp, historically Emacs had also been very slow and memory-hungry but with the modern computers it doesn't matter any more. Oh, and Emacs messes up the proper Tab characters, replacing them with spaces.
Vi doesn't have this flexibility but has a built-in set of commands extremely well suited to editing the programs. Vi is well-suited for the remote administration because it works well even over the very slow and high-latency connections and allows to do everything with just the alphanumeric keys, thus working even when the handling of the function keys (including arrows ans such) was not set up correctly. One of the newer versions of vi, vim, allows to do some very extensive programmable text manipulation, getting closer to Emacs in this respect; and vim can be set up to mess up the Tab characters just like Emacs. 108.162.246.5 21:58, 31 January 2014 (UTC)
