On Tue, Jan 29, 2013 at 4:55 PM, Rugxulo <rugx...@gmail.com> wrote:
> Some people (Dennis??) like built-in extension languages. But I guess
> that's for heavy text scripting etc. I don't personally use such, but
> it could be useful. THE uses Rexx, VIM has VIMscript (or can use Lua),
> Emacs has ELisp, etc. etc.
> http://www.texteditors.org/cgi-bin/wiki.pl?MacroLanguage

<smile>  As principal maintainer of TextEditors, it's nice to see my
work referenced...

I don't believe there's a one-size-fits-all editor for any
computer/OS.  Personally, I use several, though which set varies
depending on machine and OS.

One question with an editor is "Does it do macros?".  If the answer is
"Yes", the next question is whether they are keystroke macros, and
whether they can be saved under a name and loaded and reused.  The
last question is whether the macro facility is part of a macro
language with conditional execution constructs.

Under DOS, one editor I'm fond of is Brian H. Kelley's TM, a tiny
emacs style editor implemented in 4K.  It has emacs key assignments,
keystroke macros, incremental search, and undo.  He wanted to see what
he could cram into a 4K file, and TM was the result.  See

Another I liked war David Nye's E 1.4.  E edited files up to available
RAM, had search and replace, block copy/move/delete, and settable
right *and* left margins.  The main "gotcha" was that text was stored
as 80 column lines, and lines longer than that were silently
truncated.  It had a novel approach to macros.  You could create batch
files named 1.bat, 2.bat, etc.  Press the corresponding F-key and E
would write the text in memory to a temp file, call the batch file
attached to the F-key, and pass it the name of the temp file.  When
the batch file completed, E would read the temp file back into memory.
 So you could use batch files as external filters calling things like
SED or AWK to perform manipulations on the text you were editing
outside of E.  See http://texteditors.org/cgi-bin/wiki.pl?E.Com

Under DOS back when, I kept things like E or Tim Baldwin's T editor
(available for DOS and OS/2) on a RAM disk for speed.  For more
complex work, I used MicroEMACS because it *had* a full macro
See http://texteditors.org/cgi-bin/wiki.pl?T

When you talk about Emacs, the boundary lines get blurry.  Gnu Emacs
is essentially a Lisp interpreter, and most of it is written in Elisp.

When you get to Windows and Linux, you get editors written in Java,
Lisp, Python, and Tcl-Tk, where the implementation language *is* the
macro language.

Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
Freedos-user mailing list

Reply via email to