all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Gillespie <epg@pretzelnet.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 61189@debbugs.gnu.org
Subject: bug#61189: 29.0.60; Strange log-edit-mode M-q bug introduced in 27.1
Date: Wed, 01 Feb 2023 09:04:40 -0600	[thread overview]
Message-ID: <76117.1675263880@hassadar.pretzelnet.org> (raw)
In-Reply-To: <83k0123nb2.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

> It's because of the parenthesized "(e.g. bork)" thingy.

Right.  I didn't strip it out of my minimal test case because it
is essential.

Obviously, it was an actual parenthetical emacs broke the day I
encountered the bug.  I was curious if I could find the commit
where this actually happened to me...  and I did!

Unfortunately, it's a private repository, but if you want a
real-world example, here you go:

#+begin_example
Fix RPM upload.

More fallout from the deduplication.  I mistakenly put the os name
(e.g. 'centos') rather than major number (7) in the previous "fix".
#+end_example

You don't even need to mess with 'Summary:' or log-edit-hook; I
wish I hadn't brought those up.

Just move point into that second paragraph and then M-q

In addition to the strange space-deletion and colon-insertion, I
see now that M-q shouldn't be doing anything at all to this
paragraph.  My fill-column is 72 and those lines are already
filled as is...

Thanks!





  reply	other threads:[~2023-02-01 15:04 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
2023-02-01 15:04   ` Eric Gillespie [this message]
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=76117.1675263880@hassadar.pretzelnet.org \
    --to=epg@pretzelnet.org \
    --cc=61189@debbugs.gnu.org \
    --cc=eliz@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.