From: Giuseppe Bilotta <gip.bilotta@iol.it>
Subject: Re[2]: nath: \wall and \return doesn't work?
Date: Tue, 19 Oct 2004 00:50:57 +0200 [thread overview]
Message-ID: <1202601085.20041019005057@iol.it> (raw)
In-Reply-To: <41713A04.6010404@creutzig.de>
Saturday, October 16, 2004 Christopher Creutzig wrote:
> Giuseppe Bilotta wrote:
>>>I thought the \return were to go to the horizontal position of the
>>>\wall, in the next line? For me, both lines are flush left.
>> You are returning too soon. Lines should be ended by \\, not
>> \return, unless they are the last indented line; your snipped
>> should rather go:
> I see -- \return is not return to the horizontal position, but
> rather, \return is the end of the \wall-indented part, right?
Exactly. \wall sets a "new home position" that gets obeyed by
all *subsequent* lines (each of them ended by \\) until a
\return is met, which "backtracks" the home position to the
previous one (you can have multiple \walls).
--
Giuseppe "Oblomov" Bilotta
prev parent reply other threads:[~2004-10-18 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 8:57 Christopher Creutzig
2004-10-14 10:09 ` Giuseppe Bilotta
2004-10-16 15:11 ` Christopher Creutzig
2004-10-18 22:50 ` Giuseppe Bilotta [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=1202601085.20041019005057@iol.it \
--to=gip.bilotta@iol.it \
--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).