From: Zachary Kanfer <zkanfer@gmail.com>
To: Visuwesh <visuweshm@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, 56229@debbugs.gnu.org
Subject: bug#56229: title: add a function to move a file from one place to another
Date: Mon, 27 Jun 2022 00:42:58 -0400 [thread overview]
Message-ID: <CAFXT+RM86g2-iPauen317Ba-5m__Wkn-DKmTKgGdoTeiiNWvtQ@mail.gmail.com> (raw)
In-Reply-To: <87zghza0u8.fsf@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 902 bytes --]
Attached a patch with the function name changed to `rename-visited-file`.
I like the analogy to `rename-file`.
On Sun, Jun 26, 2022 at 11:41 AM Visuwesh <visuweshm@gmail.com> wrote:
> [ஞாயிறு ஜூன் 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.
>
[-- Attachment #1.2: Type: text/html, Size: 1412 bytes --]
[-- Attachment #2: 0001-Add-a-function-to-rename-the-file-visited-by-the-cur.patch --]
[-- Type: text/x-patch, Size: 2050 bytes --]
From f8d1473824b7120a1d0f1440cf0179ffebebbc0e Mon Sep 17 00:00:00 2001
From: Zachary Kanfer <zkanfer@gmail.com>
Date: Sat, 25 Jun 2022 01:48:38 -0400
Subject: [PATCH] Add a function to rename the file visited by the current
buffer.
* lisp/files.el (rename-visited-file)
---
etc/NEWS | 3 +++
lisp/files.el | 19 +++++++++++++++++++
2 files changed, 22 insertions(+)
diff --git a/etc/NEWS b/etc/NEWS
index 6c04ae164c..78e810ac9f 100644
--- a/etc/NEWS
+++ b/etc/NEWS
@@ -339,6 +339,9 @@ match those regexps will be ignored by 'switch-to-prev-buffer' and
** Menus
+** New command 'move-file'.
+This command moves a file to a new location.
+
---
*** The entries following the buffers in the "Buffers" menu can now be altered.
Change the 'menu-bar-buffers-menu-command-entries' variable to alter
diff --git a/lisp/files.el b/lisp/files.el
index a804f0088e..278f80679a 100644
--- a/lisp/files.el
+++ b/lisp/files.el
@@ -4817,6 +4817,25 @@ write-file
;; It's likely that the VC status at the new location is different from
;; the one at the old location.
(vc-refresh-state)))
+
+(defun rename-visited-file (new-location)
+ "Rename the file visited by the current buffer to NEW-LOCATION.
+
+Interactively, this prompts for NEW-LOCATION.
+
+If the file has not been visited, this works similarly to #'write-file".
+ (interactive (list (if buffer-file-name
+ (read-file-name "Rename file to: ")
+ (read-file-name "Rename file to: "
+ default-directory
+ (expand-file-name (file-name-nondirectory (buffer-name))
+ default-directory)))))
+ (let ((old-location (buffer-file-name)))
+ (write-file new-location t)
+ (when (and old-location
+ (file-exists-p new-location))
+ (delete-file old-location))))
+
\f
(defun file-extended-attributes (filename)
"Return an alist of extended attributes of file FILENAME.
--
2.25.1
next prev parent reply other threads:[~2022-06-27 4:42 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
2022-06-27 4:42 ` Zachary Kanfer [this message]
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=CAFXT+RM86g2-iPauen317Ba-5m__Wkn-DKmTKgGdoTeiiNWvtQ@mail.gmail.com \
--to=zkanfer@gmail.com \
--cc=56229@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=visuweshm@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).