From: "Giuseppe Bilotta" <oblomov@freemail.it>
Cc: "ConTeXt" <ntg-context@ntg.nl>
Subject: Re: Comments on \defineshortcut
Date: Sat, 3 Feb 2001 00:18:00 +0100 [thread overview]
Message-ID: <001a01c08df6$0a1392a0$a3ccfea9@nuovo> (raw)
In-Reply-To: <3.0.6.32.20010202100725.019aa100@server-1>
[the patch works perfect; about the other question:]
>
> >Second problem: ligs fail in some cases (if I \defineshortcut
> >[--][o][style\overstrike] then the following lines misses a few beats:
> >
> >it seems -o:to work- well--does it?---really?
>
> see it this way: in --- the first - picks up everything uuntil the next -
> so the third - triggers a new - which cannot find its matching -
>
> >Third problem: math fails too:
> >>
> >$(a+b)/(a-c-d)_{a+b}$
> >with -- and ++ defined as shortcuts fail (not on parenthesis, if I make those
> >active too; depends on the fact that parenthesis are delimiters in math
> mode?)
>
> Hm, this works ok here, unless of course you redefine + a few times since
> then the last meaning is used.
>
I checked out--the problem was the "pending" - form the --- on the previous
line.
Anyway, note that -- should *not* just disappear, since -- is not a shorcut, but
"-o:<whatever text>-" is; so maybe in these circumstances (when "pure" shortcut
is note defined, but it is used) charactes should revert to their original
meaning:
In the previous example:
-o:overstriken text- should be overstriked, but -- and --- should work normally
(getting ligs and alike);
with \defineshortcut[**][b][style=bold]:
*b:bolded text* should be bold, but ** and *** should work normally (no ligs in
this case);
> PS. Actually i implemented shortcuts as a kind of joke.
Then maybe such fuss is not to be wasted time upon.
Giuseppe Bilotta
Using Microsoft products is like
having sex without condoms---but
much less pleasurable
prev parent reply other threads:[~2001-02-02 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 12:16 Giuseppe Bilotta
2001-02-02 9:07 ` Hans Hagen
2001-02-02 21:47 ` Giuseppe Bilotta
2001-02-04 17:52 ` Hans Hagen
2001-02-04 17:53 ` Hans Hagen
2001-02-02 23:18 ` 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='001a01c08df6$0a1392a0$a3ccfea9@nuovo' \
--to=oblomov@freemail.it \
--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).