From: "Chris Rawnsley" <rawprawns@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Syntax highlighted output
Date: Sat, 28 Apr 2007 23:16:49 +0100 [thread overview]
Message-ID: <a1dc3f560704281516me5b3000p43036712e6338c1@mail.gmail.com> (raw)
In-Reply-To: <alpine.WNT.0.98.0704281707250.2068@nqvgln>
On 28/04/07, Aditya Mahajan <adityam@umich.edu> wrote:
> Suppose you have a file called program.php. You create a batch file
> that runs the texmfstart bin:vim ... line to create
> program-vimsyntax.tmp file. Then in your ConTeXt code, you can say,
>
> \typevimfile[convert=no][program.php]
Ah that's going to save me a bunch of time. Thank you.
> > Just as a side note, is there a way to fix it so that line numberings
> > are always on the left?
>
> \sesupvimtyping[numbering=on]
I've done that. I should've been more clear sorry. I've setup my pages
with the "alternative=doublesided" option. So for even numbered pages
I have numbering in the left margin like I want, however, for odd
pages it switches to the right side.
> By default, \tftt and \tt fonts are used for code listing. The easiest
> way to change to a different font is to use it as your
> default teletype font. If that is not possible, then you will need to
> define a new colorscheme, along the lines of the default colorscheme,
> but changing \v!mono with whatever font you want.
Umm what's a teletype font for starters?
--
Chris
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-04-28 22:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a1dc3f560704280301g7cfa1e92rcb1d684e85053912@mail.gmail.com>
2007-04-28 10:04 ` Chris Rawnsley
2007-04-28 10:59 ` luigi scarso
2007-04-28 14:06 ` Chris Rawnsley
2007-04-28 16:23 ` Aditya Mahajan
2007-04-28 16:28 ` Aditya Mahajan
2007-04-28 18:09 ` Chris Rawnsley
2007-04-28 18:26 ` Aditya Mahajan
2007-04-28 19:36 ` Chris Rawnsley
2007-04-28 19:41 ` Chris Rawnsley
2007-04-28 19:50 ` Chris Rawnsley
2007-04-28 20:10 ` Chris Rawnsley
2007-04-28 20:23 ` Aditya Mahajan
2007-04-28 20:25 ` Chris Rawnsley
2007-04-28 20:33 ` Aditya Mahajan
2007-04-28 20:49 ` Chris Rawnsley
2007-04-28 21:17 ` Aditya Mahajan
2007-04-28 22:16 ` Chris Rawnsley [this message]
2007-04-29 1:57 ` Aditya Mahajan
2007-04-29 11:38 ` Chris Rawnsley
2007-04-29 13:12 ` Wolfgang Schuster
2007-04-29 15:48 ` Chris Rawnsley
2007-04-29 14:53 ` Aditya Mahajan
2007-04-29 15:56 ` Chris Rawnsley
2007-04-29 16:07 ` Aditya Mahajan
2007-04-29 18:09 ` Chris Rawnsley
2007-04-29 18:43 ` Aditya Mahajan
2007-04-29 18:48 ` Aditya Mahajan
2007-04-29 19:38 ` Chris Rawnsley
2007-04-30 4:30 ` Aditya Mahajan
2007-04-29 18:57 ` Chris Rawnsley
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=a1dc3f560704281516me5b3000p43036712e6338c1@mail.gmail.com \
--to=rawprawns@gmail.com \
--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).