From: Hans Hagen <pragma@wxs.nl>
To: Sietse Brouwer <sbbrouwer@gmail.com>
Cc: dev-context@ntg.nl, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [dev-context] context.starttyping() prints two hash marks iff first printed character is a hash mark
Date: Sun, 22 Jan 2012 23:08:56 +0100 [thread overview]
Message-ID: <4F1C88F8.3030009@wxs.nl> (raw)
In-Reply-To: <CAF=dkzwcMbj-aMte7ohJ29vjzvy-yHkKkokz8dQAxFSoVKoAdA@mail.gmail.com>
On 22-1-2012 22:41, Sietse Brouwer wrote:
> After context.starttyping(), a hash mark in the first position gets
> printed twice. A hash mark in any other position gets printed
> normally.
> This bug does not occur after tex.print("\\starttyping"),
It's not so much a bug as a side effect of catcode regimes, tex
interpreting hashes and either or not delayed flushing. You can use
tex.print(tex.vrbcatcodes,"#")
(or context.verbatim cum suis)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
parent reply other threads:[~2012-01-22 22:08 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAF=dkzwcMbj-aMte7ohJ29vjzvy-yHkKkokz8dQAxFSoVKoAdA@mail.gmail.com>]
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=4F1C88F8.3030009@wxs.nl \
--to=pragma@wxs.nl \
--cc=dev-context@ntg.nl \
--cc=ntg-context@ntg.nl \
--cc=sbbrouwer@gmail.com \
/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).