![]() ![]() The resource files and executable links and menu entries for the other flavours are still available, though, in the joe-jupp package. Th Debian version of JOE only comes with the Jupp flavour activated, to not conflict with the Debian joe package. Furthermore, it supports SELinux context copying on Debian systems with the Linux kernel. It's usable even at 2400 baud, and it will work on any kind of sane terminal. #TEXTADEPT SAM UPDATE#Joe also has a deferred screen update to handle typeahead, and it ensures that deferral is not bypassed by tty buffering. Through simple QEdit-style configuration files, Joe can be set up to emulate editors such as Pico and Emacs, along with a complete imitation of WordStar, and a restricted mode version (lets you edit only the files specified on the command line). It has command history, TAB expansion in file selection menus, undo and redo functions, (un)indenting and paragraph formatting, filtering highlighted blocks through any external Unix command, editing a pipe into or out of a command, block move, copy, delete or filter, a bracketed paste mode automatically enabled on xterm-xfree86 and decimal and hexadecimal gotos for lines, columns, and file offsets. #TEXTADEPT SAM WINDOWS#Joe has a great screen update optimisation algorithm, multiple windows (through/between which you can scroll) and lacks the confusing notion of named buffers. It also has eight help reference cards which are always available, and an intuitive, simple, and well thought-out user interface. #TEXTADEPT SAM FULL#Joe has all of the features a Unix user should expect: full use of termcap/terminfo, complete VI-style Unix integration, a powerful configuration file, and regular expression search system. #TEXTADEPT SAM PC#Terminals still work, and they're fast & efficient as hell.Joe, the Joe's Own Editor, has the feel of most PC text editors: the key sequences are reminiscent of WordStar and Turbo C editors, but the feature set is much larger than of those. But that doesn't inherently mean we have to start building everything on top of Electron. It's time our terminal-based text editors caught up. More to the point than that, though, is that the top players in the terminal-based text editor slash IDE space, were written so many years ago, that the Internet was barely a thing at the time, that there wasn't yet a standardization on keyboards or terminals or even operating systems. ![]() Ironically, stevekemp and antirez's work, combined, shows that it actually takes less time to make an editor from scratch, than to customize Emacs or Vim to your liking! Granted, that's kind of a stretch, since most of us won't want to dive into implementing the concept of buffers. Or to Vim, which, again, came out in 1991, 24 years ago! And trust me, setting up your environment so that it's actually usable, takes days to weeks. Emacs came out in 1976! 40 years ago! But when people want an editor that's fully customizable, they go to that. Writing a usable text editor is just not that hard.Īnd stevekemp's fork shows that it's still pretty trivial to add the kind of editor customization previously only thought possible in projects like Vim and Emacs. antirez's work shows that, honestly, there's no real reason for the sparsity of choices. Keep in mind, the text-editor market space is currently very sparse, with only a few real choices: Nano, Vim, Emacs, Notepad, TextMate, Sublime Text, and lately Atom, are the big players. This showed that fundamentally, a terminal-based text editor is trivial to build. And he wrote all this in a matter of hours. Some of the comments here are really missing the point.Īntirez's original text editor was a full featured text editor - meaning fully customizable (and fast!) syntax highlighting, and a very intuitive search feature - written in pure C, with no dependencies, not even ncurses, and written in less than 1,000 lines of C code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |