From: "Jarosław Rzeszótko" <jrzeszotko@gmail.com>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Rename, delete and move current buffer and file
Date: Tue, 8 May 2018 09:05:55 +0200 [thread overview]
Message-ID: <CAO_X8WBH+jtAyVKqeGGvLyAFKJPh99OjhxKVvVEbXYGPU9rncA@mail.gmail.com> (raw)
In-Reply-To: <jwv4ljjx7mf.fsf-monnier+gmane.emacs.devel@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 3014 bytes --]
On Tue, May 8, 2018 at 3:28 AM, Stefan Monnier <monnier@iro.umontreal.ca>
wrote:
> > I have a file open in a buffer in front of me. I want to rename this file
> > and have the buffer be changed accordingly: it should now be visiting the
> > file under the new name.
> >
> > rename-file will instead:
> > - rename the file but do nothing with the buffer, if I now save the
> buffer
> > it will get saved under the old file name. The buffer still visits the
> file
> > under the old name.
>
> That's how it works currently. But we're talking about making changes.
>
> > - it will also first prompt for a file to rename, while I want to rename
> > the file I am currently editing in a buffer, along with the buffer.
>
> Right. That's why I suggested to use C-x C-w for this particular case.
> (but rename-file (c|sh)ould still be changed accordingly).
>
I do not understand what you have in mind with write-file. This creates a
copy, which is natural given the name. Do you envision some changes to it?
Or do you mean I should just use write-file and delete the old file? Some
years ago there was a conversation on emacs-devel on this topic and you
yourself proposed something like rename-current-file:
https://lists.gnu.org/archive/html/emacs-devel/2009-08/msg01132.html
Someone even sent a patch, RMS objected to the name, and then the
conversation stalled and I think nothing was changed. Some of the names I
have thrown around like rename-visited-file-with-buffer attempt to deal
with the ambiguity & asymmetry with respect to existing functions RMS might
possibly had in mind back then. I think in this case the function names
will either be short, intuitive and slightly ambiguous or the names will be
long, unintuitive and precise - due to the distinction between buffer,
visisted file, the fact that you have a current buffer but not really a
current file, the fact that many buffers might visit the same file etc., it
is very easy to come up with a lot of different names and equally easy to
find something slightly wrong with each of them. Maybe it is better to have
a shorter name that is not 100% precise but is intuitive to the users than
have a very precise name that nobody remembers and few people will be able
to discover.
To try to move this forward constructively: I like the idea of
delete-file/rename-file prompting whether to also kill/rename the
associated buffers. However, by itself it does not yet fulfill the use case
I had in mind, of dealing the file visited by the current buffer. I would
be fine with something like delete-current-file/rename-current-file that
just calls delete-file/rename-file on the current buffers file, and then
having delete-file/rename-file prompt for modifying some or all of the
(potentially several) visiting buffers. That's I think a pretty
conservative change that helps accomplish a basic task many people want to
do, quickly, easily and without distractions.
Cheers,
Jarosław Rzeszótko
[-- Attachment #2: Type: text/html, Size: 5128 bytes --]
next prev parent reply other threads:[~2018-05-08 7:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 13:58 Rename, delete and move current buffer and file Jarosław Rzeszótko
2018-05-07 14:53 ` Stefan Monnier
2018-05-07 16:20 ` Jarosław Rzeszótko
2018-05-07 17:01 ` Stefan Monnier
2018-05-07 17:47 ` Jarosław Rzeszótko
2018-05-08 1:28 ` Stefan Monnier
2018-05-08 7:05 ` Jarosław Rzeszótko [this message]
2018-05-09 12:28 ` Stefan Monnier
2018-05-09 18:12 ` Radon Rosborough
2018-05-09 22:44 ` Stefan Monnier
2018-05-10 17:01 ` Radon Rosborough
2018-05-10 21:49 ` Stefan Monnier
2018-05-11 7:31 ` Andreas Schwab
2018-05-11 15:33 ` Stefan Monnier
2018-05-11 15:45 ` Paul Eggert
2018-05-11 16:06 ` Clément Pit-Claudel
2018-05-11 16:14 ` Stefan Monnier
2018-05-09 23:50 ` Van L
2018-05-10 5:37 ` Jarosław Rzeszótko
2018-05-10 13:18 ` Van L
2018-05-10 8:20 ` Amit Ramon
2018-05-10 8:59 ` Phil Sainty
2018-05-10 16:04 ` Eli Zaretskii
2018-05-07 18:20 ` Andreas Schwab
2018-05-08 1:28 ` Stefan Monnier
2018-05-07 15:28 ` Yuri Khan
2018-05-07 16:20 ` Jarosław Rzeszótko
2018-05-09 11:46 ` Tino Calancha
2018-05-07 15:29 ` Andreas Röhler
2018-05-07 15:38 ` Andreas Röhler
2018-05-10 0:46 ` net june
2018-05-11 6:26 ` Andreas Röhler
2018-05-11 16:10 ` net june
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=CAO_X8WBH+jtAyVKqeGGvLyAFKJPh99OjhxKVvVEbXYGPU9rncA@mail.gmail.com \
--to=jrzeszotko@gmail.com \
--cc=emacs-devel@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.