unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tomas Nordin <tomasn@posteo.net>
Cc: Nicolas Gimenez <n.gimenez66@gmail.com>, 40140@debbugs.gnu.org
Subject: bug#40140: 26.3; Renaming a directory with an external tool
Date: Mon, 14 Jun 2021 16:25:16 +0200	[thread overview]
Message-ID: <87a6nsy14j.fsf@gnus.org> (raw)
In-Reply-To: <87y2rtls0v.fsf@fliptop.i-did-not-set--mail-host-address--so-tickle-me> (Tomas Nordin's message of "Sat, 21 Mar 2020 15:08:32 +0100")

Tomas Nordin <tomasn@posteo.net> writes:

>> 5) Get back to Emacs. Attempt to write file from Emacs, minibuffer in 
>> the bottom shows: "Please answer y or n. Directory 
>> '/home/nicolas/elixir_learn/mastery/test/support/tmp/' does not exist; 
>> create? (y or n)"
>
> If you try this experiment with any other text editor I think you will
> see similar effects. I tried with gedit and vim and got the
> corresponding effects.

I don't really think there's anything reasonable Emacs can do (by
itself) in these cases -- what should happen here depends on each
individual case (the tree is totally gone; it's moved somewhere else;
etc), so that has to be left to the user, like Tomas says:

> Using Emacs in this case I would do C-x C-w and then navigate to the
> existing directory, then one with the new name tmp2. Then I will have to
> allow over-writing the copy of test.ex on disc in tmp2.

So I'm closing this bug report.

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





      reply	other threads:[~2021-06-14 14:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 22:53 bug#40140: 26.3; Renaming a directory with an external tool Nicolas Gimenez
2020-03-21 14:08 ` Tomas Nordin
2021-06-14 14:25   ` Lars Ingebrigtsen [this message]

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=87a6nsy14j.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=40140@debbugs.gnu.org \
    --cc=n.gimenez66@gmail.com \
    --cc=tomasn@posteo.net \
    /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).