# Re: [NTG-context] Problem with \inmargin on \item lines

Hi,

It is not a bug. It is standard TeX: a space counts after "}" and is ignored
immediately after a control sequence such as "\item".  To override either, you
have to be explicit, "\ignorespaces" as Hans suggested in your case and "\ "
(backslash-space) in the other to put a space in.  My preferred, idiosyncratic,
pedantic way to ignore spaces in this case is a comment symbol and newlines:

\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.
\item\inmargin{Duck}%
This paragraph has a duck inmargin comment
\stopitemize
\stoptext

But I like newlines in my code, probably because I started editing text on
24x80 crt that would show only the first 80 characters of a line.

Michael

On May 2, 2012, at 12:33 AM, Malte Stien wrote:

> 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.
>

________________________________

This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.

the sender by reply e-mail message and destroy all copies of the
original message (including attachments).
___________________________________________________________________________________