From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Documentation for "Clone Buffers" (corrected version) Date: 14 Mar 2004 16:55:26 -0500 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <877jxty4gg.fsf@emacswiki.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1079301540 4372 80.91.224.253 (14 Mar 2004 21:59:00 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 14 Mar 2004 21:59:00 +0000 (UTC) Cc: Alan Mackenzie , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun Mar 14 22:58:55 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1B2ddH-0005vg-00 for ; Sun, 14 Mar 2004 22:58:55 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1B2ddH-0003dZ-00 for ; Sun, 14 Mar 2004 22:58:55 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B2dax-0002Pw-QQ for emacs-devel@quimby.gnus.org; Sun, 14 Mar 2004 16:56:31 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.30) id 1B2dal-0002ON-Sl for emacs-devel@gnu.org; Sun, 14 Mar 2004 16:56:19 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.30) id 1B2daF-00021Y-0u for emacs-devel@gnu.org; Sun, 14 Mar 2004 16:56:18 -0500 Original-Received: from [132.204.24.67] (helo=mercure.iro.umontreal.ca) by monty-python.gnu.org with esmtp (Exim 4.30) id 1B2daE-00021N-Ox for emacs-devel@gnu.org; Sun, 14 Mar 2004 16:55:46 -0500 Original-Received: from asado.iro.umontreal.ca (asado.iro.umontreal.ca [132.204.24.84]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 1187A20FA1; Sun, 14 Mar 2004 16:55:40 -0500 (EST) Original-Received: by asado.iro.umontreal.ca (Postfix, from userid 20848) id F15308C8E4; Sun, 14 Mar 2004 16:55:38 -0500 (EST) Original-To: Alex Schroeder In-Reply-To: <877jxty4gg.fsf@emacswiki.org> Original-Lines: 27 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-0.001, requis 5, BAYES_44 -0.00) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:20472 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:20472 [ For the record: I'm the perpetrator of the FORK argument. ] > What I'm trying to say is that yes, the interface is not elegant. > But it seems that both variants are equally unpopular, so we just > need to pick one, stick to it, and make a generic solution the > problem for all these instances. Renaming the buffer before calling > the function again was deemed to be good enough a long while back (I > guess because we were not sure that using a prefix was better or > possible at all). The question I have is: what alternative is better. I personally don't like the M-x rename-uniquely option too much because it forces me to first find the-buffer-that-I-don't-want, then rename it, then run the command I wanted to run in the first place. The clone-buffer is a bit better in that I can just run the command and afterwards just M-x clone-buffer, but it still brings up the-buffer-that-I-don't-want which I might have to bury. Maybe another generic solution would be a prefix arg which causes a subsequent `get-buffer-create' (or somesuch) to not find the buffer it's looking for. I.e. after M-x magic-prefix RET calling (get-buffer-create "*shell*") would look for *shell* and if it exists, it would rename it uniquely, and then create a new *shell*. Stefan