From: Eli Zaretskii <eliz@gnu.org>
To: stefankangas@gmail.com
Cc: thibault@thb.lt, 58967@debbugs.gnu.org
Subject: bug#58967: 29.0.50; `g` in list-directory fails with error
Date: Sun, 13 Nov 2022 11:48:09 +0200 [thread overview]
Message-ID: <83o7tbkwx2.fsf@gnu.org> (raw)
In-Reply-To: <83fsennbm6.fsf@gnu.org> (message from Eli Zaretskii on Sat, 12 Nov 2022 22:47:45 +0200)
> Cc: thibault@thb.lt, 58967@debbugs.gnu.org
> Date: Sat, 12 Nov 2022 22:47:45 +0200
> From: Eli Zaretskii <eliz@gnu.org>
>
> > Cc: 58967@debbugs.gnu.org
> > From: Stefan Kangas <stefankangas@gmail.com>
> > Date: Sat, 12 Nov 2022 12:33:47 -0800
> >
> > Thibault Polge <thibault@thb.lt> writes:
> >
> > > Steps to reproduce:
> > >
> > > - M-x list-directory RET
> > > - (Pick a directory)
> > > - Type `g`
> > > - Results in:
> > > Debugger entered--Lisp error: (void-function nil)
> > > nil()
> > > help-mode-revert-buffer(t nil)
> > > revert-buffer(t)
> > > funcall-interactively(revert-buffer t)
> > > command-execute(revert-buffer)
> > > Instead of refreshing the view (or just doing nothing)
> >
> > I believe that this bug was fixed on master?
>
> No, I can reproduce it with today's master.
The problem here is that list-directory puts the buffer in Help mode,
and that mode's revert-buffer-function is inappropriate for the kind
of stuff we display in this case.
So either we change list-directory to concoct a help-xref-stack-item
which would work, or we implement a revert-buffer-function for
list-directory's buffer.
This is a very old problem: I see it as far back as Emacs 24.
next prev parent reply other threads:[~2022-11-13 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 14:56 bug#58967: 29.0.50; `g` in list-directory fails with error Thibault Polge
2022-11-12 20:33 ` Stefan Kangas
2022-11-12 20:47 ` Eli Zaretskii
2022-11-13 9:48 ` Eli Zaretskii [this message]
2022-11-12 20:52 ` Thibault Polge
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=83o7tbkwx2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58967@debbugs.gnu.org \
--cc=stefankangas@gmail.com \
--cc=thibault@thb.lt \
/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.