![]() For casual, unsophisticated applications by someone who grew up with green screen character based computers, it's probably OK. For this reason, I would not recommend Emacs to anyone who is under 50 year old, or who needs power user capabilities. Would shell support like TextMate's mate command line tool be useful It's something I really miss in MacDown, but not sure about others. If the goal is to clarify what the language is, do it on the preceding paragraph. The things I just mentioned, are all present in some limited and inept form, but falls far short of current standard of good user interface design. Don’t prefix shell code with dollar signs unless you will be showing the command output on the same code block. If you are looking to highlight a shell session command sequence as it looks to the user (with prompts, not just as contents of a hypothetical script file), then the right identifier to use at the moment is console: console foobar: whoami foo Share. To this day, it lacks or struggles with very basic things, like interactive dialogs, toolbars, tabbed interface, file system navigation, etc., etc. So Emacs does 5% or what an editor should do quite will, and is surprisingly under-powered and old fashioned at the other 95%. Unfortunately, it didn't keep up with the times and fails to take advantage of the entire world of GUI design that's revolutionized computer science since then. In fairness to Emacs, its original design was conceived in that context and is rather good at some things, like flexible ability to bind commands to keyboard shortcuts. ![]() ![]() I was using Emacs in the early 1980's, before there were GUIs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |