From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: rename buffer but overwrite already existing one
Date: Mon, 23 Mar 2020 20:46:51 +0100 [thread overview]
Message-ID: <87h7ye97mc.fsf@mat.ucm.es> (raw)
In-Reply-To: 83d092c19h.fsf@gnu.org
[-- Attachment #1: Type: text/plain, Size: 1132 bytes --]
>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
>> From: Uwe Brauer <oub@mat.ucm.es>
>> Date: Mon, 23 Mar 2020 20:23:15 +0100
>>
>> >> Couldn't rename-buffer, optionally, overwrite the content of a buffer.
>>
>> > Yes, but it's called copy-to-buffer, not rename-buffer.
>>
>> Thanks for pointing this out to me, but I have to mark the whole buffer
>> first, which is a but inconvenient, I say.
> That's just "C-x h" away.
I know, but decades of abusing rename-buffer are difficult to come by..
>> Couldn't there an argument added so that with the argument the whole
>> buffer is copied?
> I suggest to submit a feature request.
I thought that even I could implement this
but
(defun my-copy-to-buffer (buffer)
"Copy to specified BUFFER the whole buffer."
(interactive "BCopy to buffer: \n")
(let ((oldbuf (current-buffer)))
(with-current-buffer (get-buffer-create buffer)
(barf-if-buffer-read-only)
(erase-buffer)
(save-excursion
(insert-buffer-substring oldbuf (point-min) (point-max))))))
Copies 0 bytes. sigh
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2020-03-23 19:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 18:05 rename buffer but overwrite already existing one Uwe Brauer
2020-03-23 18:23 ` Stefan Monnier
2020-03-23 19:24 ` Uwe Brauer
2020-03-23 19:18 ` Eli Zaretskii
2020-03-23 19:23 ` Uwe Brauer
2020-03-23 19:35 ` Eli Zaretskii
2020-03-23 19:46 ` Uwe Brauer [this message]
2020-03-23 19:41 ` Andreas Schwab
2020-03-23 19:43 ` Uwe Brauer
2020-03-23 20:02 ` Stephen Berman
2020-03-23 20:49 ` Uwe Brauer
2020-03-23 21:21 ` Stephen Berman
2020-03-24 9:17 ` Uwe Brauer
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=87h7ye97mc.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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.