ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: "Idris Samawi Hamid ادريس سماوي حامد" <ishamid@colostate.edu>
Subject: Re: feature request
Date: Sun, 13 Nov 2011 11:55:14 +0100	[thread overview]
Message-ID: <C7C2E7B1-6278-44D6-98AD-0A313632EA61@st.estfiles.de> (raw)
In-Reply-To: <op.v4so5trw60pfzx@ihamidnb.libarts.colostate.edu>

Hi Idris,

Am 11.11.2011 um 19:47 schrieb Idris Samawi Hamid ادريس سماوي حامد:

> On Fri, 11 Nov 2011 08:34:28 -0700, Steffen Wolfrum <context@st.estfiles.de> wrote:
> 
>> quite often I wish we could have a kind of in line comment:
>> Something like ¿this is my comment¡ this.
> 
> I think the mechanism for fancy in-line comments is already there, developed one-or-two years ago as we were working on some critical-edition-related stuff ...
> 
> I saw the other answers: Could you elaborate more about exactly what you're looking for, just in case their suggestions don't quite hit the spot?



I am looking for the same functionality as the traditional TeX comment (starting with %), but used in-line not only after a paragraph.

This means, it is only meant for writing/reading comments in the source. 
And its presence must not affect the typeset file, eg. the resulting PDF, in any respect, of course!

Is the mechanism you mention best suited for that purpose?


Steffen
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2011-11-13 10:55 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 15:34 Steffen Wolfrum
2011-11-11 15:53 ` Andreas Harder
2011-11-11 15:57   ` Wolfgang Schuster
2011-11-11 16:01 ` Wolfgang Schuster
2011-11-11 18:47 ` Idris Samawi Hamid ادريس  سماوي حامد
2011-11-13 10:55   ` Steffen Wolfrum [this message]
2011-11-13 21:33     ` Andreas Schneider
2011-11-14  7:57       ` Steffen Wolfrum
2011-11-14  8:07         ` Hans Hagen
2011-11-14  9:22           ` Steffen Wolfrum
2011-11-14 18:38             ` Idris Samawi Hamid ادريس  سماوي حامد
2011-11-15 22:03               ` Idris Samawi Hamid ادريس   سماوي حامد
2011-11-15 22:11                 ` Wolfgang Schuster
2011-11-15 22:28                 ` Aditya Mahajan
2011-11-15 22:47                   ` Idris Samawi Hamid ادريس   سماوي حامد
2011-11-14  8:47 ` Aditya Mahajan
2011-11-14 14:03   ` Hans Hagen
2011-11-15  3:35     ` Aditya Mahajan
2011-11-15  5:43       ` Aditya Mahajan
2011-11-15  8:56         ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2019-07-03  6:00 Atsuhito Kohda
2019-07-03  6:35 ` Henri Menke
2019-07-03  6:42 ` Henri Menke
2019-07-04  5:18   ` Atsuhito Kohda
2019-07-04  5:48     ` Henri Menke
2019-07-05 23:31       ` Atsuhito Kohda
2019-07-04 15:16     ` Aditya Mahajan
2019-07-04 15:54       ` Alan Braslau
2019-07-05 23:44         ` Atsuhito Kohda
2019-07-05 23:35       ` Atsuhito Kohda
2007-07-05 17:41 Feature request John R. Culleton
2007-07-05 21:37 ` Patrick Gundlach
2007-07-05 22:27   ` John R. Culleton
2007-07-06  8:09     ` Patrick Gundlach
2005-07-27  9:58 Steffen Wolfrum
2005-07-27 22:16 ` Hans Hagen
     [not found] <a06210200bf0958f2bc0f@87.193.3.198>
2005-07-26 16:20 ` Mojca Miklavec
2005-07-26 22:56   ` Hans Hagen
2005-07-27  5:15     ` luigi.scarso
2005-07-26 15:33 Steffen Wolfrum
2005-07-26 22:38 ` Hans Hagen
2005-07-26 15:00 Steffen Wolfrum
2005-07-26 13:32 Steffen Wolfrum
2005-07-26 14:21 ` Hans Hagen
2005-07-26 14:32 ` Hans Hagen

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=C7C2E7B1-6278-44D6-98AD-0A313632EA61@st.estfiles.de \
    --to=context@st.estfiles.de \
    --cc=ishamid@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).