From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: fill-paragraph broken
Date: Tue, 09 Jul 2013 21:25:49 +0200 [thread overview]
Message-ID: <87k3kzlema.fsf@gmail.com> (raw)
In-Reply-To: <CAJcAo8u+Sse9VTxQ6m8hMVLHxVKBdnFv8Cjbu562QKBGeFOPSg@mail.gmail.com> (Samuel Wales's message of "Tue, 9 Jul 2013 11:47:25 -0700")
Hello,
Samuel Wales <samologist@gmail.com> writes:
> I think Org should support this variable and not fill two commented
> paragraphs with a commented empty line as if they were one.
I do not.
> When you fill in, for example, Emacs Lisp mode, each paragraph is
> filled as a paragraph, without combining them.
You're comparing apples and oranges. Emacs Lisp is a programming
language, i.e., derived from `prog-mode', whereas Org is about text,
i.e., ultimately derived from `text-mode'. Let's compare text modes with
text modes.
The only mode derived from `text-mode' with comments I can think of is
`rst-mode'. And it doesn't fill comments at all. We might do the same
for the sake of consistency...
> I think there is benefit for the user in keeping things consistent
> with other modes and supporting this Emacs variable.
Org doesn't support this variable. It doesn't even use "newcomment.el".
There is a simple reason for that: many functions in "newcomment.el"
assume comments may start anywhere on a line. This is not possible in
Org. "newcomment.el" is not meant for the `text-mode' family.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-07-09 19:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 20:53 fill-paragraph broken Samuel Wales
2013-07-09 12:00 ` Nicolas Goaziou
2013-07-09 17:47 ` Samuel Wales
2013-07-09 18:47 ` Samuel Wales
2013-07-09 19:25 ` Nicolas Goaziou [this message]
2013-07-10 8:07 ` Samuel Wales
2013-07-10 12:27 ` Nicolas Goaziou
2013-07-10 19:42 ` Samuel Wales
2013-07-11 7:11 ` Nicolas Goaziou
2013-07-11 8:01 ` Samuel Wales
2013-07-11 8:19 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3kzlema.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.