From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: typing and linenumbering
Date: Thu, 16 Mar 2006 10:02:46 +0100 [thread overview]
Message-ID: <441929B6.1000704@elvenkind.com> (raw)
In-Reply-To: <ops6g56d0i9niby6@localhost>
nico wrote:
> Hello,
> The output is pretty as I wish, but unfortunately the line numbers are
> *not* the numbers of the listing lines, but the numbers of the lines once
> wrapped in the frame. In the example below the first line is very long
> (the "blah blah" line), but in the output it is shown as 4 lines (with 4
> line numbers).
I've tried this with a "method" trick, but that does not work too well
with 'location=intext'. Anyway, here is what I did:
\setuptyping[prog]
[bodyfont=small,
before={\begingroup\setuplinenumbering[style=small,%
step=2,start=3,location=inmargin,method=type]
\startframelisting \obeylines
\startlinenumbering},
after={\stoplinenumbering\stopframelisting\endgroup}]
> Is there a way to achieve this in a more integrated way with the typing
> environment?
Probably, but I do not know.
> The other side effect of the method used is that it changes
> the linenumbering behaviour outside the typing environment. I tried the
> "reset" option, but it doesn't change the intext location. Is there a
> possibility to come back to default settings?
The setup obeys normal grouping rules (hence the \begingroup ...
\endgroup in the code above)
> Last but not least, is it possible to customize the wrapping behaviour so
> that an arbitrary command can be called before the cut, and another
> command after the cut? What I would like to have is {\space\wrapsign}
> before the cut and an indentation after the cut to show that the line is
> wrapped.
That should be possible in typing environments. I even think there was
a wiki page on that. But in non-verbatim environments, the breaking is
simply TeX's paragraph builder, and I do not think context allows
tinkering with that (I could be proven wrong, of course)
Cheers, Taco
next prev parent reply other threads:[~2006-03-16 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 22:02 nico
2006-03-16 9:02 ` Taco Hoekwater [this message]
2006-03-16 21:41 ` nico
2006-03-16 22:16 ` 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=441929B6.1000704@elvenkind.com \
--to=taco@elvenkind.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).