From: "Trent W. Buck" <trentbuck@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 57376@debbugs.gnu.org
Subject: bug#57376: 28.1; rcirc-fill-flag ignored after 27->28 upgrade
Date: Mon, 26 Sep 2022 10:33:14 +1000 [thread overview]
Message-ID: <YzDzSgvQuhQnvTjQ@hera.lan> (raw)
In-Reply-To: <87sfkf7t41.fsf@posteo.net>
Philip Kaludercic wrote:
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > Philip Kaludercic <philipk@posteo.net> writes:
> >
> >> At the very least I was wrong about the (fill-region (point-min)
> >> (point-max)), so that has to go. But I will modify the code locally to
> >> check if squeezing white-space before the prompt is still necessary or
> >> not.
> >
> > This was a month ago -- was a fix for this pushed?
>
> I've pushed the change to remove 'fill-region'. If nobody reports any
> issues in the coming days, I'll close the bug report.
For the record,
I can't easily run/test git HEAD, but
with this I have not been annoyed:
;; squeeze spaces out of text before rcirc-text
- (fill-region (point-min) (point-max))
+ ;; https://debbugs.gnu.org/57376
+ ;; (fill-region (point-min) (point-max))
+ ;; (canonically-space-region (point-min) (point-max))
next prev parent reply other threads:[~2022-09-26 0:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 8:25 bug#57376: 28.1; rcirc-fill-flag ignored after 27->28 upgrade Trent W. Buck
2022-08-24 11:45 ` Lars Ingebrigtsen
2022-08-25 15:34 ` Philip Kaludercic
2022-08-27 4:10 ` Trent W. Buck
2022-08-27 8:14 ` Philip Kaludercic
2022-08-27 13:22 ` Lars Ingebrigtsen
2022-08-27 13:37 ` Philip Kaludercic
2022-09-24 14:58 ` Lars Ingebrigtsen
2022-09-24 15:51 ` Philip Kaludercic
2022-09-25 8:31 ` Philip Kaludercic
2022-09-26 0:33 ` Trent W. Buck [this message]
2022-10-06 10:34 ` Philip Kaludercic
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=YzDzSgvQuhQnvTjQ@hera.lan \
--to=trentbuck@gmail.com \
--cc=57376@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=philipk@posteo.net \
/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.