From: Hans Hagen <pragma@wxs.nl>
Subject: Re: \typebuffer and tabs / specify code type
Date: Wed, 03 Nov 2004 13:39:45 +0100 [thread overview]
Message-ID: <4188D191.1020009@wxs.nl> (raw)
In-Reply-To: <20041103121548.GD22571@cebitec.uni-bielefeld.de>
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
\setuptyping[file][option=TEX]
and alike
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2004-11-03 12:39 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 [this message]
2004-11-03 13:19 ` Eckhart Guthöhrlein
2004-11-04 17:38 ` Eckhart Guthöhrlein
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=4188D191.1020009@wxs.nl \
--to=pragma@wxs.nl \
--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).