From: Benjamin Motz <b.motz@uni-muenster.de>
To: emacs-orgmode@gnu.org
Subject: Re: fill-paragraph: wrong behaviour after latex-environments
Date: Thu, 03 May 2012 17:23:59 +0200 [thread overview]
Message-ID: <u13bkobq5gueo.fsf@majorana.uni-muenster.de> (raw)
In-Reply-To: 87zk9pe255.fsf@gmail.com
azw@fastmail.fm (Albert Z. Wang) writes:
[...]
> This sets several new paragraph boundary markers to prevent wrapping
> them into paragraphs: \begin{, \end{, and the unnumbered display
> equation shortcut \[, \].
Thank you, that did the trick!
Shouldn't that be the default behaviour, i.e. should this be
considered a bug?
Benjamin
next prev parent reply other threads:[~2012-05-03 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 12:57 fill-paragraph: wrong behaviour after latex-environments Benjamin Motz
2012-05-03 15:05 ` Albert Z. Wang
2012-05-03 15:23 ` Benjamin Motz [this message]
2012-05-05 6:39 ` Bastien
2012-05-05 16:13 ` Nicolas Goaziou
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=u13bkobq5gueo.fsf@majorana.uni-muenster.de \
--to=b.motz@uni-muenster.de \
--cc=emacs-orgmode@gnu.org \
/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).