From: Hans Hagen <pragma@wxs.nl>
Subject: Re: templates
Date: Mon, 26 Apr 1999 11:11:35 +0200 [thread overview]
Message-ID: <37242DC7.31855010@wxs.nl> (raw)
In-Reply-To: <14116.14559.514634.395614@PC709>
Taco Hoekwater wrote:
> So the name really should be \defineshortcut, IMO. Otherwise, you
Ok.
> 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.
Sounds reasonable. (I have to look into the \type<<...>> i.e. slanted
verbatim but I don't expect problems there.) \catcode`< is btw always
reset when reading in files.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
prev parent reply other threads:[~1999-04-26 9:11 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 ` templates Taco Hoekwater
1999-04-26 9:11 ` Hans Hagen [this message]
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=37242DC7.31855010@wxs.nl \
--to=pragma@wxs.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).