From: Eli Zaretskii <eliz@gnu.org>
To: Eric Gillespie <epg@pretzelnet.org>
Cc: 61189@debbugs.gnu.org
Subject: bug#61189: 29.0.60; Strange log-edit-mode M-q bug introduced in 27.1
Date: Tue, 31 Jan 2023 14:23:29 +0200 [thread overview]
Message-ID: <83k0123nb2.fsf@gnu.org> (raw)
In-Reply-To: <71595.1675119121@hassadar.pretzelnet.org> (message from Eric Gillespie on Mon, 30 Jan 2023 16:52:01 -0600)
> From: Eric Gillespie <epg@pretzelnet.org>
> Date: Mon, 30 Jan 2023 16:52:01 -0600
>
> It's an old bug, but it requires such a specific kind of log
> message to trigger that it took me until a few months ago to
> finally hit it!
>
> To reproduce:
> 0. open modified file under version control
> 1. C-x v v
> 2. Enter the following two-line message (i.e. replace "Summary:" and the rest):
> bork bork bork bork bork bork bork bork bork bork bork bork bork
> bork (e.g. bork) bork bork bork bork bork bork bork bork
> 3. M-q
> 4. M-q
>
> (I have run with (setq log-edit-hook '(log-edit-show-files)) for a long time
> and that's how I encountered the bug.)
>
> Expected:
> First M-q fills the paragraph to 70 columns.
> Second does nothing.
>
> Actual:
> First M-q fills the paragraph to 70 columns.
> Second moves one bork back from line one to line two, adds a colon, and
> deletes the sapce before the opening parenthesis, resulting in:
>
> bork bork bork bork bork bork bork bork bork bork bork bork bork
> bork:(e.g. bork) bork bork bork bork bork bork bork bork
It's because of the parenthesized "(e.g. bork)" thingy.
next prev parent reply other threads:[~2023-01-31 12:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 22:52 bug#61189: 29.0.60; Strange log-edit-mode M-q bug introduced in 27.1 Eric Gillespie
2023-01-31 12:23 ` Eli Zaretskii [this message]
2023-02-01 15:04 ` Eric Gillespie
2023-02-04 8:41 ` Eli Zaretskii
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=83k0123nb2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61189@debbugs.gnu.org \
--cc=epg@pretzelnet.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.