From: Bastien <bastienguerry@googlemail.com>
To: "Sébastien Vauban" <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: How to get \\ in title or author?
Date: Wed, 09 Sep 2009 11:33:29 +0800 [thread overview]
Message-ID: <878wgou706.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87my55rw1b.fsf@mundaneum.com> ("Sébastien Vauban"'s message of "Tue, 08 Sep 2009 23:01:04 +0200")
Sébastien Vauban <wxhgmqzgwmuf@spammotel.com> writes:
>> Maybe \linebreak is less context-sensitive than \newline, which would mean
>> that there are more contexts (like \title and \author) in which it behaves
>> as expected. Just a guess.
>
> I've asked the question on FCTT (fr.comp.text.tex) and already got an answer
> of Maneul Pegourie-Gonnard (who is expert on that matter):
>
> http://groups.google.fr/group/fr.comp.text.tex/browse_thread/thread/1b1af2e5291270e2#
>
> Sorry (for the others), it's in French.
Merci! Here is a summary:
- none of \\ \linebreak or \newline change a paragraph, they just start
a new line
- with \linebreak, LaTeX tries to justify the resulting text, not with
\newline
- \linebreak can take an argument to let LaTeX decides whether the line
should be broken or not. The default \linebreak always triggers a
break, but \linebreak[2] will let LaTeX decides depending on whether
the result is acceptable or not, and \linebreak[0] prevents any line
break...
- \\ can take two arguments: one star and one digit. The star prevents
the line break to trigger a page break, and the digit lets you add a
vertical space between the two lines.
In environments like \flushleft \flushright \centering \raggedleft
\raggedright, \\ doesn't have its normal definition (whereas \newline
behaves normally).
- \newline is the version of \\ with no argument
HTH,
--
Bastien
next prev parent reply other threads:[~2009-09-09 3:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-07 12:59 How to get \\ in title or author? Sébastien Vauban
2009-09-07 22:33 ` Bastien
2009-09-08 7:50 ` Sébastien Vauban
2009-09-08 3:33 ` Bastien
2009-09-08 21:01 ` Sébastien Vauban
2009-09-09 3:33 ` Bastien [this message]
2009-09-09 5:00 ` Nick Dokos
2009-09-09 9:47 ` Sébastien Vauban
2009-09-09 10:34 ` Bastien
2009-09-10 14:30 ` Sébastien Vauban
2009-09-10 18:02 ` Carsten Dominik
2009-09-10 18:30 ` Nick Dokos
2009-09-09 14:26 ` Nick Dokos
2009-09-09 14:43 ` Bastien
2009-09-10 14:27 ` Sébastien Vauban
2009-09-09 21:08 ` Tim Burt
2009-09-09 2:15 ` Brian van den Broek
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878wgou706.fsf@bzg.ath.cx \
--to=bastienguerry@googlemail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).