From: Giuseppe Bilotta <bourbaki@bigfoot.com>
Cc: ntg-context@ntg.nl
Subject: Re[2]: Environments and shortcuts
Date: Tue, 5 Jun 2001 12:34:53 +0200 [thread overview]
Message-ID: <1708537342.20010605123453@bigfoot.com> (raw)
In-Reply-To: <3.0.6.32.20010604121415.009daa00@server-1>
Monday, June 04, 2001 Hans Hagen wrote:
HH> At 02:45 PM 6/2/01 +0200, Giuseppe Bilotta wrote:
>>Hello,
>>
>>I know I should not be using shortcuts (they are not "official"),
>>but they're so usefull ... ok, here's the problem.
>>
>>If I define a shortcut in an environment file, like
>>
>>\startenvironment novel
>>
>>\defineshortcut[color=red]
>>
>>\stopenvironment
>>
>>and the use \environment novel, the shortcut definition does not
>>work (all other definitions do, though). What might the problem
>>be?
HH> since < > are used in macros (\ifnum etc) they are pushed popped when
HH> loading critical files which means that after loading the env, the < has
HH> it's old meaning. So, you need to add
HH> \catcode`\<=\active
HH> to the main file (\def\enableshortcuts{\catcode...} \enableshortcuts)
Works like a chamr, thank you.
--
Giuseppe "Oblomov" Bilotta
prev parent reply other threads:[~2001-06-05 10:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-02 12:45 Giuseppe Bilotta
2001-06-04 10:14 ` Hans Hagen
2001-06-05 10:34 ` Giuseppe Bilotta [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=1708537342.20010605123453@bigfoot.com \
--to=bourbaki@bigfoot.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).