From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Comment, verbatim
Date: Wed, 16 Jun 1999 17:39:28 +0200 [thread overview]
Message-ID: <3767C530.BF8E3A44@wxs.nl> (raw)
In-Reply-To: <3767A734.D2B749EC@gmx.de>
Tobias Burnus wrote:
> using \startcomment[title] ... \stopcomment to comment out an part of the script
> (which should appear as note), I noticed that the linefeed is obeyed but not the
> space when used for indenting. Can this be changed?
Hm. Something \obeyspaces. Maybe an option?
> I use syntax highlighted verbatim (JV alias Java), but I haven't figured out how
> to change the fonts so, that keywords become bold, the rest should be roman
> (\tt).
> (Ok if I'd manage to get the comment signs and the comments in italic (or
> slanted) I would be glad).
> Somehow trials with something like \definefont[JVidentifierfont][MonoBold at
> \bodyfontsize] or so (borrowed from Berend's verb-sql) end with noting or even
> with an error message :-(
It's somewhere else, see core-ver:
\def\setupcommonverbatim#1%
{\def\verbatimfont {\tttf}%
\def\prettyidentifierfont {\ttsl}%
\def\prettyvariablefont {}%
if you change this to:
\def\setupcommonverbatim#1%
{\def\verbatimfont {\tttf}%
\def\prettyidentifierfont {\bf}%
\def\prettyvariablefont {\it}%
you will succeed. If we can work out proper keys, I will add an option
[somestyle=...]
normal
reserved
whatever
Now who has ideas on keys?
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~1999-06-16 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-16 13:31 Tobias Burnus
1999-06-16 15:39 ` Hans Hagen [this message]
1999-06-16 22:33 ` Tobias Burnus
1999-06-17 7:35 ` 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=3767C530.BF8E3A44@wxs.nl \
--to=pragma@wxs.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).