From: Stephen Berman <stephen.berman@gmx.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 64230@debbugs.gnu.org
Subject: bug#64230: 30.0.50; Ibuffer reports 1 file too many with ibuffer-auto-mode enabled
Date: Wed, 13 Sep 2023 23:49:57 +0200 [thread overview]
Message-ID: <87edj1920q.fsf@gmx.net> (raw)
In-Reply-To: <CADwFkmncx7aKGvAdb3QdHgvM5wiVY=NoiyvhUkPgJiEPLQ7GgA@mail.gmail.com> (Stefan Kangas's message of "Wed, 13 Sep 2023 13:58:03 -0700")
On Wed, 13 Sep 2023 13:58:03 -0700 Stefan Kangas <stefankangas@gmail.com> wrote:
> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> Should I install both patches? I've tested all combinations of deleting
>> just one or more than buffer with ibuffer-auto-mode disabled and enabled
>> and ibuffer-expert nil and non-nil, but perhaps I've again overlooked
>> something, so I'll wait for a go-ahead.
>
> Thanks, please install. Your reasoning and patches make sense to me,
> though I only gave them the most cursory testing.
>
>> Also, since the second patch is strictly unrelated to the original bug
>> report, a new bug report for it might be preferred.
>
> I don't have any preference. Perhaps it's fine to keep it in the same
> report since the issue was discovered here.
Thanks, I went ahead and pushed both patches (after fixing a small typo
in the comment to read "`ibuffer-expert' nil") as commit 9d9570bfbf5.
Steve Berman
prev parent reply other threads:[~2023-09-13 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 17:35 bug#64230: 30.0.50; Ibuffer reports 1 file too many with ibuffer-auto-mode enabled Stephen Berman
2023-09-10 14:11 ` Stefan Kangas
2023-09-11 14:18 ` Stephen Berman
2023-09-11 14:44 ` Stefan Kangas
2023-09-13 18:51 ` Stephen Berman
2023-09-13 20:58 ` Stefan Kangas
2023-09-13 21:49 ` Stephen Berman [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87edj1920q.fsf@gmx.net \
--to=stephen.berman@gmx.net \
--cc=64230@debbugs.gnu.org \
--cc=stefankangas@gmail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).