From: Juri Linkov <juri@linkov.net>
To: 32673@debbugs.gnu.org
Subject: bug#32673: 27.0.50; wdired: broken 'wdired--restore-dired-filename-prop'
Date: Sun, 09 Sep 2018 18:52:55 +0300 [thread overview]
Message-ID: <87lg8byluo.fsf@mail.linkov.net> (raw)
As reported in https://lists.gnu.org/archive/html/emacs-devel/2018-09/msg00372.html
Wdired breaks delete-selection-mode in the latest master 27.0.50:
1. create scratch directory with a file
mkdir /tmp/test
cd /tmp/test
touch foo.c
2. start emacs
LC_ALL=C emacs -Q -nw
3. activate delete-selection-mode
M-x delete-selection-mode RET
4. go into the folder
C-x C-f /tmp/test
5. enter wdired mode
C-x C-q
6. replace 'foo' with 'test' by selecting the whole file name
and typing a new one, e.g.
M-2 C-M-SPC test
or
C-SPC C-e test
When typing the first letter, it removes delete-selection-pre-hook from
pre-command-hook, thus breaking delete-selection-mode, because of this
error seen in the *Messages* buffer:
Error in pre-command-hook (delete-selection-pre-hook): (error "No file on this line")
The same error is reproducible when simply deleting an old file name
before typing a new one in the step 6, e.g.:
M-d test
The raised error is:
Debugger entered--Lisp error: (error "No file on this line")
signal(error ("No file on this line"))
error("%s" "No file on this line")
dired-move-to-end-of-filename(nil)
dired-get-filename()
wdired--restore-dired-filename-prop(198 198 1)
delete-char(1 nil)
funcall-interactively(delete-char 1 nil)
call-interactively(delete-char nil nil)
command-execute(delete-char)
This is caused by changes in bug#32173.
next reply other threads:[~2018-09-09 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-09 15:52 Juri Linkov [this message]
2018-09-11 22:08 ` bug#32673: 27.0.50; wdired: broken 'wdired--restore-dired-filename-prop' Stephen Berman
2018-09-11 23:32 ` Juri Linkov
2018-09-12 10:02 ` Stephen Berman
2018-09-12 13:57 ` Eli Zaretskii
2018-09-13 20:21 ` Stephen Berman
2020-02-12 21:53 ` Juri Linkov
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=87lg8byluo.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=32673@debbugs.gnu.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 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.