From: Malte Stien <malte@stien.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Problem with \inmargin on \item lines
Date: Wed, 2 May 2012 14:33:55 +1000 [thread overview]
Message-ID: <6AD49FC8-3558-4538-B5C3-21D14D3C3A3B@stien.de> (raw)
Hi everyone,
I am experiencing a problem with \inmargin{some text} in \itemized lists. I am using them a lot in my documents, and it is kind of annoying. It appears that if one uses the \inmargin macro just prior to the \item macro, the in-margin text is typeset against the previous line, not the line with the \item. Minimal example.
\starttext
\startitemize
\item This is just a normal completely innocent paragraph against which one will be able to judge the amount of indentation of the next paragraph.
\inmargin{Duck}\item This paragraph has a duck inmargin comment
\stopitemize
\stoptext
That seems fair enough and even makes sense on some level. If however, one reverses the two macros, like so:
\item\inmargin{Duck} This paragraph has a duck inmargin comment
the leading space just after the closing brace is actually printed. I take this to be a bug, or is this by design? The only way I can around this is to not use a space, like so:
\item\inmargin{Duck}This paragraph has a duck inmargin comment
But I don't find that to be a satisfying solution. After all I am using ConTeXt because I am a bit pedantic about text, even the source code in this case.
Regards,
Malte.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2012-05-02 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 4:33 Malte Stien [this message]
2012-05-02 8:07 ` Hans Hagen
2012-05-02 11:30 ` Rogers, Michael K
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=6AD49FC8-3558-4538-B5C3-21D14D3C3A3B@stien.de \
--to=malte@stien.de \
--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).