From: Bill Meahan <wmeahan94@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: A series of articles about text-editors for the MAPS
Date: Wed, 08 Aug 2012 12:51:52 -0400 [thread overview]
Message-ID: <50229928.2080203@gmail.com> (raw)
In-Reply-To: <CAG5iGsCVD=hA0aY061gJ34aiAMjCJqEwdyYeOf8cupF_0srmMw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1698 bytes --]
On 08/08/2012 11:02 AM, luigi scarso wrote:
> Anyone involved in TeX programming has no fear of all others languages.
I've never programmed in Plain TeX. I'm not afraid of other languages,
though. I've programmed in Assembler (several varieties for 8-bit,
12-bit, 16-bit and 32-bit machines), SPS, FORTRAN II, FORTRAN IV
(several varieties), WATFOR, FORTRAN 77, FOCAL, BASIC/Visual Basic
(several varieties), C, Ada, PL/SQL, SQL, Perl, sh, ksh, bash, FORTH and
several others I've forgotten including some application-specific
"macro" languages. LISP, however, isn't structured like any of those.
Lua is. For the way my brain works, the learning-curve for Lua is much
shorter than the learning-curve for LISP.
> why not Scite ? It's the Hans's preferred editor.
Tried it, have it installed, added Hans's lexers but still wasn't
satisfied. If I have to hack on something to get what I want, Textadept
is easier to hack than SciTE since it's pretty much a "reimagining" (as
the folks in Hollywood like to say) of emacs for the 21st Century and
designed for user-driven additions/expansions.
I've already added interactive spell-checking with aspell (in a separate
window), dictionary lookup (and thesaurus-only lookup) via dict, running
context with a single key and launching a PDF viewer with a single key
This is getting way OT. Let's end it here.
--
Bill Meahan, Westland, Michigan USA
“Writing is a combination of intangible
creative fantasy and appallingly
hard work.”
—Anthony Powell
This message is digitally signed with an X.509 certificate
to prove it is from me and has not been altered since it was sent.
[-- Attachment #1.2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4933 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2012-08-08 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 9:34 Willi Egger
2012-08-08 0:22 ` john Culleton
2012-08-08 13:19 ` Martin 'golodhrim' Scholz
2012-08-08 13:34 ` luigi scarso
2012-08-08 14:24 ` Henning Hraban Ramm
2012-08-08 23:07 ` Martin 'golodhrim' Scholz
2012-08-08 23:15 ` luigi scarso
2012-08-08 14:46 ` Bill Meahan
2012-08-08 15:02 ` luigi scarso
2012-08-08 16:51 ` Bill Meahan [this message]
2012-08-08 17:12 ` luigi scarso
2012-08-08 20:09 ` Peter Münster
2012-08-08 14:52 ` john Culleton
2012-08-08 21:10 ` Alan BRASLAU
2012-08-08 13:43 ` Procházka Lukáš Ing. - Pontex s. r. o.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50229928.2080203@gmail.com \
--to=wmeahan94@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).