ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pablo Rodriguez <oinos@gmx.es>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: suggestion on [option=TEX]
Date: Wed, 12 Feb 2014 21:10:40 +0100	[thread overview]
Message-ID: <52FBD540.5010406@gmx.es> (raw)
In-Reply-To: <AC7EF67D-245D-4D2E-AB94-67FEBBD0ABF6@gmail.com>

On 02/07/2014 12:36 AM, Wolfgang Schuster wrote:
> Am 06.02.2014 um 19:29 schrieb Pablo Rodriguez:
>> [...]
>> After reading the document, I think it could be achieved with:
>> [...]
>> But this doesn’t work. I must be missing something obvious.
> 
> You have to add a comma after \letterpercent. You should also be
> careful with the text in the comments because commands are expanded,
> e.g. take a look at the \TeX in the comment.
> 
> \setupbodyfont[dejavu]
> 
> \defineprocessor[myescape][style=\ttbf,color=gray,left={\letterpercent}]
> 
> \setuptyping[TEX][escape=myescape->{\letterpercent,}]
> 
> \starttext
> \startTEX
> This is \TeX\ code % and this is a \TeX\ comment.
> \stopTEX
> \stoptext

Sorry for not having replied before and many thanks for your help, Wolfgang.

The code works as you told me. I really appreciate your help.

I have a further question about the option=TEX to color code. This was
my original issue, but I haven’t expressed myself clearly. The question
is directed primarily to Hans.

With option=TEX, comment seems to be the only element that isn’t colored
and formatted as a whole. Other elements are formatted as a whole and
the format even extends in multiple lines.

My question here isn’t technical (unless the described behavior is a
bug). The issue is on visual coherence. At least for newbies, it would
be better to differentiate visually between regular text and commented text.

Is there any reason not to format whole comments option=TEX? (Sorry, but
I don’t understand why this is different.)

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk
___________________________________________________________________________________
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:[~2014-02-12 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05 18:50 Pablo Rodriguez
2014-02-05 23:57 ` Wolfgang Schuster
2014-02-06 18:29   ` Pablo Rodriguez
2014-02-06 23:36     ` Wolfgang Schuster
2014-02-12 20:10       ` Pablo Rodriguez [this message]

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=52FBD540.5010406@gmx.es \
    --to=oinos@gmx.es \
    --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).