From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: different vertical space with \definelines and \setuplines
Date: Sun, 9 Dec 2012 20:25:52 +0100 [thread overview]
Message-ID: <5E7479C2-5474-44DE-996F-F7CBD03E0BF9@gmail.com> (raw)
In-Reply-To: <50C4E193.3090708@web.de>
Am 09.12.2012 um 20:08 schrieb Pablo Rodríguez <oinos@web.de>:
> Hi Hans,
>
> I have the following sample:
>
> \definelines[narrow][before=\blank,after=\blank]
> \stopsetups
>
> \starttext
> This is a paragraph.\par
> \startnarrow
> this is a verse
>
> this is a verse
> \stopnarrow
> This is paragraph.\par
> \stoptext
>
> If I replace \definelines with \setuplines, before and after aren't honored.
>
> \definelines adds an extra paragraph separation space within the lines
> that isn't inserted with \setuplines.
>
> Is this intended?
1. When you add a blank line in a “lines” environment context inserts the value from the “inbetween” key.
\starttext
\startlines[inbetween=INBETWEEN]
this is a verse
this is a verse
\stoplines
\stoptext
You can remove the line by setting “inbetween=”.
2. The \startnarrow command is already defined in the core as narrower command.
\definenarrower[mynarrow][left=4em,default=left]
\starttext
Normal Text.
\startnarrow
Indented Text.
\stopnarrow
Normal Text.
\startnarrow[mynarrow]
Indented Text.
\stopnarrow
Normal Text.
\stoptext
3. Replacing \definelines with \setuplines changes nothing because you haven’t created a lines environment with the name “narrow” yet.
Wolfgang
___________________________________________________________________________________
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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2012-12-09 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-09 19:08 Pablo Rodríguez
2012-12-09 19:25 ` Wolfgang Schuster [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=5E7479C2-5474-44DE-996F-F7CBD03E0BF9@gmail.com \
--to=wolfgang.schuster@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).