unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 41624@debbugs.gnu.org
Subject: bug#41624: 28.0.50; wdired-change-to-wdired-mode sometimes infloops
Date: Sat, 24 Oct 2020 21:46:12 +0200	[thread overview]
Message-ID: <87zh4bcsqj.fsf@gnus.org> (raw)
In-Reply-To: <874kmli1bl.fsf@web.de> (Michael Heerdegen's message of "Fri, 23 Oct 2020 14:17:18 +0200")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> I found out that the infloop can be fixed easily if we change
> `find-dired-sentinel' to let the buffer end in a newline.

[...]

>> Then I can change permissions with wdired, I only still get the
>> inappropriate message that it would have failed, though it has
>> succeeded.
>
> Hah, and this issue is also present in a "standard" dired buffer.
>
> So, apart from the missing newline at the end of the find-dired buffer,
> I see no difference to regular dired buffers.

Ah, then I think this should indeed be fixed (changing
`find-dired-sentinel' sounds good to me).  Are you pushing a fix for
this?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2020-10-24 19:46 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
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 [this message]
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=87zh4bcsqj.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=41624@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).