From: Idris Samawi Hamid <ishamid@lamar.colostate.edu>
Subject: bug in indentation
Date: Thu, 18 Aug 2005 21:44:58 -0600 [thread overview]
Message-ID: <430699FE@webmail.colostate.edu> (raw)
Dear knights,
There is apparently something wrong with the indenting mechanism in the latest
context: I have to invoke indenting twice to cut it on (uncomment the second
\setupindenting):
============================
% output=pdf interface=en
\setupwhitespace[none]
\setupindenting[medium,next] % does not indent
%\setupindenting[medium,next] % need both to indent
\definestartstop
[quote]
[before={\startnarrower[1*middle]\blank[big]},
after={\stopnarrower\blank[big]}]
\starttext
\input knuth
\startquote
\input knuth
\stopquote
\input knuth
\stoptext
============================
log verifying version
=============================
This is pdfeTeX, Version 3.141592-1.21a-2.2 (Web2c 7.5.3) (format=cont-en
2005.8.18) 18 AUG 2005 21:47
entering extended mode
\write18 enabled.
(c:\CONTEXT\tex\texmf-local/web2c/natural.tcx)
**&cont-en testblank.tex
(./testblank.tex
ConTeXt ver: 2005.08.15 fmt: 2005.8.18 int: english mes: english
=============================
Similarly, if I want a local exception to the indentation I need something
like
\start\setupindenting[none]\setupindenting[none]
<paragraph>
\stop
Also, dropped capes does not work well when indentation is on, calling for the
local exception above.
Finally, \indenting and \noindenting don't work like they used to: bug or
feature?
I actually spent hours trying to debug a huge manuscript (with messed up now
fixed indentation) before finally realizing and isolating the problem.
Upgrading ConTeXt is always an adventure...
Best
Idris
============================
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-08-19 3:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-19 3:44 Idris Samawi Hamid [this message]
2005-08-19 12:46 ` Taco Hoekwater
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=430699FE@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--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).