From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Re[4]: Displayed material, again
Date: Tue, 11 Mar 2003 18:04:16 +0100 [thread overview]
Message-ID: <17528077252.20030311180416@iol.it> (raw)
In-Reply-To: <5.1.0.14.1.20030311155338.04921ed8@server-1>
Tuesday, March 11, 2003 Hans Hagen wrote:
HH> At 12:47 PM 3/11/2003 +0100, you wrote:
>>Anyway, I built a "quick and dirty" patch which seems to work for
>>most environments which, I think, require it: itemgroups,
>>definitions, formulas, verbatim. You can put it in your cont-loc
>>between \unprotect ... \protect pairs:
HH> This is dangerous! better put it into cont-min.tex and load that one in
HH> yoru cont-sys.tex file
HH> \readfile{yourfile}\donothing\donothing
HH> or so. Cont-loc.tex is a personal extensions (there i put patches that i
HH> test for some time before they make it into the kernel; i also have a
HH> cont-exp for experiment, like dirty speedups); since these file are not
HH> distributed, there is a danger in them being on someones system and being
HH> loaded.
I thought that cont-new was for the temporary patches and cont-loc
for the local extensions? Since cont-loc is not distributed with
the normal ConTeXt distribution, it makes sense to put it there,
doesn't it?
HH> Also, something:
HH> \overloaded \def \somehack ...
HH> may warn you for such dangers.
That's good to know.
HH> \def\synchronizeindentation
HH> {%
HH> \doifvalue{\??dd#1\c!springvolgendein}\v!nee\noindentation
HH> \doifvalue{\??dd#1\c!springvolgendein}\v!auto\noindent}
HH> }%
HH>
HH> saves keying and also provides a hook
Right :) I expect to see it in the core for the next release! ;)
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2003-03-11 17:04 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 16:25 Giuseppe Bilotta
2003-03-10 16:50 ` Bruce D'Arcus
2003-03-10 20:22 ` Re[2]: " Giuseppe Bilotta
2003-03-10 22:15 ` s-mag-01 Bruce D'Arcus
2003-03-11 8:00 ` s-mag-01 Hans Hagen
2003-03-11 14:11 ` s-mag-01 Bruce D'Arcus
2003-03-11 14:31 ` s-mag-01 Hans Hagen
2003-03-11 14:34 ` s-mag-01 Bruce D'Arcus
2003-03-11 14:46 ` Fonts again in ConTeXt Patrick Gundlach
2003-03-11 15:10 ` Bruce D'Arcus
2003-03-12 13:04 ` Maarten Sneep
2003-03-12 13:23 ` Bruce D'Arcus
2003-03-12 13:26 ` Maarten Sneep
2003-03-12 14:05 ` Patrick Gundlach
2003-03-12 15:11 ` Hans Hagen
2003-03-12 15:43 ` Patrick Gundlach
2003-03-12 19:35 ` Jens-Uwe Morawski
2003-03-13 8:31 ` Patrick Gundlach
2003-03-14 8:27 ` Hans Hagen
2003-03-12 20:26 ` Hans Hagen
2003-03-13 8:54 ` Patrick Gundlach
2003-03-13 12:37 ` Hans Hagen
2003-03-13 15:07 ` John Culleton
2003-03-13 15:52 ` Hans Hagen
2003-03-21 18:05 ` Patrick Gundlach
2003-03-22 11:10 ` Hans Hagen
2003-03-14 21:34 ` Henning Hraban Ramm
2003-03-14 21:24 ` Henning Hraban Ramm
2003-03-21 18:06 ` Patrick Gundlach
2003-03-12 15:09 ` Hans Hagen
2003-03-11 15:02 ` s-mag-01 Adam Lindsay
2003-03-11 20:52 ` s-mag-01 Hans Hagen
2003-03-11 9:13 ` s-mag-01 Patrick Gundlach
2003-03-10 17:00 ` Displayed material, again Hans Hagen
2003-03-10 23:24 ` Hans Hagen
2003-03-11 10:08 ` Re[2]: " Giuseppe Bilotta
2003-03-11 10:52 ` Hans Hagen
2003-03-11 11:47 ` Re[3]: " Giuseppe Bilotta
2003-03-11 14:57 ` Hans Hagen
2003-03-11 17:04 ` Giuseppe Bilotta [this message]
2003-03-12 20:36 ` Re[4]: " Hans Hagen
2003-03-13 9:36 ` Re[5]: " Giuseppe Bilotta
2003-03-13 12:23 ` Hans Hagen
2003-03-11 15:12 ` Re[3]: " Hans Hagen
2003-03-12 21:07 ` Hans Hagen
2003-03-13 9:38 ` Re[4]: " Giuseppe Bilotta
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=17528077252.20030311180416@iol.it \
--to=gip.bilotta@iol.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).