ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: issue with \comment
Date: Tue, 16 Jun 2020 20:00:01 +0200	[thread overview]
Message-ID: <10635489-8bd3-be3f-bfe6-5ede130f5302@gmail.com> (raw)
In-Reply-To: <a56d6ef5-f87c-e002-fd02-62c0690f0472@gmx.es>

Pablo Rodriguez schrieb am 16.06.2020 um 19:20:
> Dear list,
>
> when trying to report another issue, I found the following one (using
> latest from 2020.06.12 17:43):
>
>    \setupinteraction[state=start]
>    \starttext
>      a\contextversion
>
>      \comment[location={rightmargin}]{comment}
>    \stoptext
>
> For some strange reason, \comment isn’t added when there is no other
> content in the paragraph.
>
> I think it might be a bug. Could anyone confirm this?

Why is everything a bug?


Some elements like margin blocks or register entries need an anchor.

\enabletrackers[typesetters.margindata]

\starttext

\inrightmargin{Hello!}xxx

\inrightmargin{Here!}
%\inrightmargin{Here!}\dontleavehmode

\stoptext

Wolfgang

___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2020-06-16 18:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 17:20 Pablo Rodriguez
2020-06-16 18:00 ` Wolfgang Schuster [this message]
2020-06-16 18:41   ` Pablo Rodriguez

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=10635489-8bd3-be3f-bfe6-5ede130f5302@gmail.com \
    --to=wolfgang.schuster.lists@gmail.com \
    --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).