From: "Eckhart Guthöhrlein" <eckhart.guthoehrlein@uni-bielefeld.de>
Subject: Re: \typebuffer and tabs / specify code type
Date: Thu, 4 Nov 2004 18:38:38 +0100 [thread overview]
Message-ID: <20041104173838.GC5681@cebitec.uni-bielefeld.de> (raw)
In-Reply-To: <20041103131919.GE22571@cebitec.uni-bielefeld.de>
On Wed, Nov 03, 2004 at 02:19:19PM +0100, Eckhart Guthöhrlein wrote:
> On Wed, Nov 03, 2004 at 01:39:45PM +0100, Hans Hagen wrote:
> > Eckhart Guthöhrlein wrote:
> > >Hi all,
> > >
> > >I'm using \typebuffer to typeset some metapost code. How can I tell it
> > >to either ignore tabs or treat them like 1,2,3,... spaces, instead of
> > >printing ^^I?
> > >Another question: There has been a thread on telling \typebuffer what
> > >type of code on this list some time ago, without a final solution. Is
> > >there a switch to use metapost or whatever appropriate highlighting?
> >
> > \setuptyping[tab=on] % or off
>
> That does not work here. Example file:
>
> \starttext
> \startbuffer[ex]
> draw unitsquare scaled 1cm;
> \stopbuffer
> % \setuptype[tab=on]
> % \setuptype[tab=off]
> % \setuptyping[tab=on]
> \setuptyping[tab=off]
> \typebuffer[ex]
> \stoptext
>
> None of the \setuptyp* has any effect, I alwas get ^^I^^I for the two
> tabs.
I have furthermore observed that typing of files via \typefile as well
as \starttyping..\stoptyping are affected, opposed to \typebuffer.
\typefile and the typing environment do never print ^^I for a tab, but
either a space or several spaces, depending on the tab=on/off option.
This behavior is what I would like to have for \typebuffer, too. How to
do it?
--
Eckhart
prev parent reply other threads:[~2004-11-04 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-03 12:15 Eckhart Guthöhrlein
2004-11-03 12:39 ` Hans Hagen
2004-11-03 13:19 ` Eckhart Guthöhrlein
2004-11-04 17:38 ` Eckhart Guthöhrlein [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=20041104173838.GC5681@cebitec.uni-bielefeld.de \
--to=eckhart.guthoehrlein@uni-bielefeld.de \
--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).