From: Taco Hoekwater <taco.hoekwater@wkap.nl>
Cc: ntg-context@ntg.nl
Subject: Re: templates
Date: Mon, 26 Apr 1999 09:58:55 +0000 (/etc/localtime) [thread overview]
Message-ID: <14116.14559.514634.395614@PC709> (raw)
In-Reply-To: <37236780.E03F58BC@wxs.nl>
>>>>> "Hans" == Hans Hagen <pragma@wxs.nl> writes:
Hans> Hi All, Sometimes keying in macros can be annoying. For this
Hans> reason, sometimes macro packages use | to shorten things,
Hans> like |word| for verbatim in macros related to programming
Hans> source code or manuals. In itself such macros are not that
Hans> expressive, but they at least save typing keys.
While the idea of shortcuts is nice, I'm not too happy about this
implementation. These things are really key-shortcuts, not templates.
So the name really should be \defineshortcut, IMO. Otherwise, you
might run into conflicts later when and if Context starts using real
templates (a 'real' template is like for instance the message
libraries' -- notation for the extra information).
For syntax, I am a little unsure about the |. Why not use a syntax
like <b:bold>? I wouldn't be worried about hacing \catcode`<=13;
because that char almost never used outside of math.
Taco
next prev parent reply other threads:[~1999-04-26 9:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-25 19:05 templates Hans Hagen
1999-04-26 9:58 ` Taco Hoekwater [this message]
1999-04-26 9:11 ` templates Hans Hagen
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=14116.14559.514634.395614@PC709 \
--to=taco.hoekwater@wkap.nl \
--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).