From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: fill-paragraph vs. financial institutions
Date: Mon, 4 Sep 2006 09:40:56 -0700 [thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMIEAPCLAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1GJtig-0003Za-NZ@fencepost.gnu.org>
Now you've really done it. M-x fill-paragraph on
487.2875,
487.3375,
487.4000,
...
gives
487.2875, 3375, 4000, 4500, 4750, 5250, 5500, 6000, 7250,
8000, 8500, 487.8750,
adaptive-fill-regexp has an explicit alternative to match prefixes
such as `NNN.' This would only apply in the case where the first two
lines of a paragraph both start that way.
Maybe we should delete that case.
Sorry I didn't reply earlier. I just got bit by this. Yes, please get rid of
this feature. The traditional behavior is fine: fill and indent properly
when only the first line starts that way.
IOW, this:
1. Some text here in a long line that gets filled.
should not turn into this:
1. Some text here in a long
1. line that gets filled.
It should instead turn into this:
1. Some text here in a long
line that gets filled.
Is that really a case that people
use? In some kinds of outlines, the first line of a paragraph would
start that way, but you wouldn't put the prefix on every line.
Can anyone think of a reason why we should keep this case?
Not I.
I propose therefore the following change. Does anyone see a
problem in it?
If that puts things back the way they were in previous versions, then that's
good.
next prev parent reply other threads:[~2006-09-04 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1GHdnZ-000101-2w@jidanni1>
2006-08-29 17:18 ` fill-paragraph vs. financial institutions Richard Stallman
2006-08-29 22:08 ` Juri Linkov
2006-09-03 15:17 ` Richard Stallman
2006-09-04 16:40 ` Drew Adams [this message]
2006-09-05 9:43 ` Richard Stallman
2006-09-05 14:08 ` Drew Adams
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=EIENLHALHGIMHGDOLMIMIEAPCLAA.drew.adams@oracle.com \
--to=drew.adams@oracle.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.