From: Lars Ingebrigtsen <larsi@gnus.org>
To: Leo Liu <sdl.web@gmail.com>
Cc: 13492@debbugs.gnu.org
Subject: bug#13492: 24.2.92; Buffer changing in dired-mark-pop-up
Date: Sun, 06 Dec 2020 20:19:48 +0100 [thread overview]
Message-ID: <874kkyrbcb.fsf@gnus.org> (raw)
In-Reply-To: <m1y5fqb9cr.fsf@gmail.com> (Leo Liu's message of "Sat, 19 Jan 2013 03:05:08 +0800")
Leo Liu <sdl.web@gmail.com> writes:
> In discussion of http://debbugs.gnu.org/13152, it is noted that
> dired-mark-pop-up invokes FUNCTION in different buffers depending on if
> there are marked files. This is problematic and makes it harder to use
> dired-mark-pop-up correctly.
>
> In particular this is directly related to dired-guess-shell-alist-user,
> a user variable. Harder to predict the behaviour of COMMAND when it is a
> lisp expression. But in this case an error is thrown when the buffer is
> switched to a non-dired buffer. So no user code will be broken if
> dried-mark-pop-up stops switching buffers.
>
> I propose fix dired-mark-pop-up to be consistent where it invokes
> FUNCTION.
(This bug report unfortunately got no response at the time.)
I see that there's been some changes done to that function with regards
to how it selects windows before running FUNCTION, but I'm not sure
whether this fixes the problem or not, since there's no recipe to
reproduce the bug here.
Are you still seeing this problem in more recent versions of Emacs? If
so, can you provide a step-by-step recipe to reproduce it, starting from
"emacs -Q"?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-12-06 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-18 19:05 bug#13492: 24.2.92; Buffer changing in dired-mark-pop-up Leo Liu
2020-12-06 19:19 ` Lars Ingebrigtsen [this message]
2021-01-20 17:06 ` Lars Ingebrigtsen
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=874kkyrbcb.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=13492@debbugs.gnu.org \
--cc=sdl.web@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).