From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 41624@debbugs.gnu.org
Subject: bug#41624: 28.0.50; wdired-change-to-wdired-mode sometimes infloops
Date: Fri, 23 Oct 2020 12:03:30 +0200 [thread overview]
Message-ID: <87sga55kel.fsf@web.de> (raw)
In-Reply-To: <87tuuml6jy.fsf@gnus.org> (Lars Ingebrigtsen's message of "Thu, 22 Oct 2020 15:43:45 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> > M-x find-dired ~/ RET -iname \*.pdf RET (any find-dired buffer will do)
> >
> > M-: (setq wdired-allow-to-change-permissions 'advanced) RET
> >
> > M-x wdired-change-to-wdired-mode RET
> >
> > ==> infloop
>
> This bug is still present on the trunk, but I'm not quite sure whether
> this is supposed to be supported or not? The find-dired buffers aren't
> very much like normal dired buffers... so should wdired just signal an
> error here?
I can't answer that, but I can tell that when I manually delete the last
lines of text and whitespace in such a buffer (saying "find finished
..."), it works as expected (though I'm getting a message saying that "1
rename actions failed"). But I'm definitely able to change permissions
with wdired then. So it seems possible to make the feature work, the
infloop results from the unsuitable termination condition of the loop in
`wdired-preprocess-perms'.
Michael.
next prev parent reply other threads:[~2020-10-23 10:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 4:47 bug#41624: 28.0.50; wdired-change-to-wdired-mode sometimes infloops Michael Heerdegen
2020-10-22 13:43 ` Lars Ingebrigtsen
2020-10-23 10:03 ` Michael Heerdegen [this message]
2020-10-23 11:22 ` Lars Ingebrigtsen
2020-10-23 11:38 ` Michael Heerdegen
2020-10-23 12:17 ` Michael Heerdegen
2020-10-23 13:18 ` Michael Heerdegen
2020-10-24 19:46 ` Lars Ingebrigtsen
2020-10-31 14:43 ` Michael Heerdegen
2020-10-23 11:15 ` Stefan Kangas
2020-10-23 11:22 ` 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=87sga55kel.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=41624@debbugs.gnu.org \
--cc=larsi@gnus.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 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).