unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Visuwesh <visuweshm@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Zachary Kanfer <zkanfer@gmail.com>, 56229@debbugs.gnu.org
Subject: bug#56229: title: add a function to move a file from one place to another
Date: Sun, 26 Jun 2022 21:11:51 +0530	[thread overview]
Message-ID: <87zghza0u8.fsf@gmail.com> (raw)
In-Reply-To: <875ykne905.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 26 Jun 2022 17:31:54 +0200")

[ஞாயிறு ஜூன் 26, 2022] Lars Ingebrigtsen wrote:

> Zachary Kanfer <zkanfer@gmail.com> writes:
>
>> It's more complicated because if the buffer is *not* visiting a file,
>> the right thing for this function to just save the buffer to the
>> location selected. I don't know if the name that needs to take that
>> into account.
>>
>> Is there a name for the file a buffer is visiting? Maybe
>> "move-associated-file"?  "move-visited-file"?
>
> I like `move-visited-file'.  Or perhaps `rename-visited-file'?

I think `rename-visited-file' would fit in better especially since we
already have `rename-file'; it also parallels dired's R command.





  reply	other threads:[~2022-06-26 15:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-26  4:49 bug#56229: title: add a function to move a file from one place to another Zachary Kanfer
2022-06-26 14:50 ` Lars Ingebrigtsen
2022-06-26 15:16   ` Zachary Kanfer
2022-06-26 15:31     ` Lars Ingebrigtsen
2022-06-26 15:41       ` Visuwesh [this message]
2022-06-27  4:42         ` Zachary Kanfer
2022-06-27  7:55           ` Lars Ingebrigtsen
2022-06-28  3:24             ` Zachary Kanfer
2022-06-28 11:10               ` Eli Zaretskii
2022-06-28  3:24             ` Richard Stallman
2022-06-28  4:23               ` Zachary Kanfer
2022-06-28 12:15                 ` Lars Ingebrigtsen
2022-06-29  1:17                   ` Zachary Kanfer

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=87zghza0u8.fsf@gmail.com \
    --to=visuweshm@gmail.com \
    --cc=56229@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=zkanfer@gmail.com \
    /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).