From: "Drew Adams" <drew.adams@oracle.com>
To: 7751@debbugs.gnu.org
Subject: bug#7751: 24.0.50; `fill-paragraph' on doc string with colons
Date: Tue, 28 Dec 2010 12:45:12 -0800 [thread overview]
Message-ID: <3F4673E9CCED46A0BD9BA6B9BDF5DF8D@us.oracle.com> (raw)
This is a regression introduced in Emacs 22.1. There is no such problem
in Emacs 20 or 21.
emacs -Q
Put this in *scratch* or an Emacs-Lisp mode buffer:
(defun foo ()
"WHAT'S WITH THIS?
The usual menu keywords are allowed: :enable, :visible, :keys, :filter,...."
42)
Put the cursor on the second sentence of the doc string and hit `M-q'.
The sentence gets wrapped this way:
The usual menu keywords are
allowed: :enable, :visible, :keys, :filter,...."
The line should instead be broken between ":keys" and ":filter", since
there is enough space for "... allowed: :enable, :visible, :keys,".
Remove the colon before ":enable" or add a space to get ": enable" and
the line gets broken as one would expect. But with the colons as they
are, and no matter how much space is between "allowed:" and ":enable",
the line is broken incorrectly.
The same problem occurs if you change "allowed:" to "allowed.",
"allowed!", "allowed?", "allowed,", or just "allowed", and no matter how
much space you leave after it. The same problem occurs if you remove
"allowed:" altogether, i.e., with "The usual menu keywords are :enable,
...".
In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
of 2010-12-20 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.4) --no-opt --cflags
-Ic:/imagesupport/include'
next reply other threads:[~2010-12-28 20:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-28 20:45 Drew Adams [this message]
2010-12-28 21:36 ` bug#7751: 24.0.50; `fill-paragraph' on doc string with colons Lawrence Mitchell
2012-02-17 12:55 ` Lawrence Mitchell
2012-02-17 14:13 ` Chong Yidong
2012-02-17 14:55 ` Drew Adams
2012-09-17 0:15 ` Drew Adams
2016-04-28 10:05 ` Lars Ingebrigtsen
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=3F4673E9CCED46A0BD9BA6B9BDF5DF8D@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=7751@debbugs.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 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.