unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Christopher Sean Morrison <brlcad@mac.com>, 44556@debbugs.gnu.org
Subject: bug#44556: 27.1; Ido deletes file without configuration with C-x C-v C-k
Date: Wed, 9 Dec 2020 23:58:56 +0300	[thread overview]
Message-ID: <X9E6kMf8t7XPNQwl@protected.rcdrun.com> (raw)
In-Reply-To: <87pn3ivhsz.fsf@gnus.org>

* Lars Ingebrigtsen <larsi@gnus.org> [2020-12-09 23:43]:
> Christopher Sean Morrison <brlcad@mac.com> writes:
> 
> > As I said, I provided the recipe that affected me in the original
> > report — see the “For example” line.  I do not know if this issue
> > occurs in any other context, e.g., with/without Graphene and am not
> > any more available to explore those possibilities.
> 
> I interpreted your bug report to say that you needed Graphene to
> reproduce the problem, but I see now that you didn't really say that.
> 
> The recipe is:
> 
> touch file1 file2
> emacs -Q -f ido-mode file1
> C-x C-v C-k
> 
> Emacs will now say "Delete /tmp/file1 (yes or no)", and that is indeed
> pretty surprising behaviour.

When I do it, it asks nothing, as I have delete-by-moving-to-trash.

But there is one general problem with that function and that is that
C-j is close to C-k and people like me work in the dark not looking at
keyboard. C-j means to complete the file but if C-k is pressed by
mistake file will end up in trash without question and possibly get
lost.

It is good to remove the malfunction from key bindings. Better is to
remove it completely.





  reply	other threads:[~2020-12-09 20:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 19:55 bug#44556: 27.1; Ido deletes file without configuration with C-x C-v C-k Christopher Sean Morrison via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-11 10:12 ` Lars Ingebrigtsen
2020-12-09 15:12   ` Lars Ingebrigtsen
2020-12-09 15:24     ` Jean Louis
2020-12-09 19:23     ` Christopher Sean Morrison via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-12-09 20:22       ` Jean Louis
2020-12-09 20:35       ` Lars Ingebrigtsen
2020-12-09 20:58         ` Jean Louis [this message]
2020-12-09 21:19           ` Christopher Sean Morrison via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-13 10:24             ` Lars Ingebrigtsen
2022-02-28 12:44               ` Morgan Willcock
2022-03-01 15:43                 ` Lars Ingebrigtsen
2020-12-09 21:15       ` Jean Louis

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=X9E6kMf8t7XPNQwl@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=44556@debbugs.gnu.org \
    --cc=brlcad@mac.com \
    --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).