unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: emacs-devel@gnu.org
Subject: Re: rename buffer but overwrite already existing one
Date: Mon, 23 Mar 2020 14:23:55 -0400	[thread overview]
Message-ID: <jwvk13baqg2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <874kuf9cbg.fsf@mat.ucm.es> (Uwe Brauer's message of "Mon, 23 Mar 2020 19:05:23 +0100")

> Couldn't rename-buffer, optionally, overwrite the content of a buffer.

Yes and no: it depends on what you mean by "overwrite the content of a buffer".

Here's what I think could be done easily:

- say you have buffers "mybuf" "otherbuf"
- you're in "mybuf" and you do `M-x rename-buffer RET otherbuf RET`.
- Emacs currently refuses it but it could accept your command by
  first renaming "otherbuf" to "otherbuf<1>", or by killing "otherbuf",
  or by asking you for a new name to use for that other buffer.

But the two buffers can be unified into a single one.

Of course, another option might be to tweak `rename-uniquely` so it
automatically chooses a more informative name than what you get by
adding a "<N>".  I think such a feature might be a good idea
in general.  E.g. we could add a variable `buffer-name-suffix-function`
which some major modes could set to provide "meaningful" unique names.




        Stefan




  reply	other threads:[~2020-03-23 18:23 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 [this message]
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
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

  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=jwvk13baqg2.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --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 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).