ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to prevent empty page after MPpage?
Date: Mon, 13 Jul 2009 10:02:54 +0200	[thread overview]
Message-ID: <4A5AEA2E.4090209@wxs.nl> (raw)
In-Reply-To: <605202f20907122318s6d2ba3f5ga571d7c21abde75c@mail.gmail.com>

Vafa Khalighi wrote:
>>
>> Thanks a lot!!! The magic apparently works. I don't understand what
>> exactly the "obeylines" macro does (it seems that it just makes sure
>> that none of line endings get lost, not even inside definition
>> itself).
>>
>>
> 
> sometimes when you typeset a piece of text like poems, you actually want to
> go to the next line, so one solution would be to put a \par at the end of
> each line but if there are too much of these lines, then you will get sick
> of typing \par at the end of each line and so there is a CS namely
> \obeylines that does this automatically. Lets look at one example:
> 
> I am a Plain \TeX\ user,\par
> and you are a Con\TeX t User,\par
> There are other people who use La\TeX,\par
> but we all are \TeX\ users.
> 
> {\obeylines
> I am a Plain \TeX\ user,
> and you are a Con\TeX t user.
> There are other people who use La\TeX,
> but we all are \TeX\ users.}
> 
> See in the above one, whenever I wanted to end the line and go to the next
> line, I had to put a \par, but in the second one I just put \obeylines which
> is the same that means ecah end of my lines will be treated like a \par.

\startlines
I am a Plain \TeX\ user,
and you are a Con\TeX t user.
There are other people who use La\TeX,
but we all are \TeX\ users.
\stoplines


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2009-07-13  8:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12 16:02 Mojca Miklavec
2009-07-12 20:45 ` Hans Hagen
2009-07-12 20:49   ` Mojca Miklavec
2009-07-12 21:02     ` Wolfgang Schuster
2009-07-12 21:19       ` Mojca Miklavec
2009-07-13  6:18         ` Vafa Khalighi
2009-07-13  8:02           ` Hans Hagen [this message]
2009-07-13  7:50         ` Hans Hagen
2009-07-13  8:56           ` Mojca Miklavec
2009-07-13 12:40             ` Hans Hagen
2009-07-13  7:47     ` 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=4A5AEA2E.4090209@wxs.nl \
    --to=pragma@wxs.nl \
    --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).