From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: [patch] minor patch for register.el Date: Tue, 19 Feb 2013 20:30:33 -0800 Message-ID: <55DAF5C025494EE6A6552D8E63E9AEF9@us.oracle.com> References: <20130220.111807.1912441579815160723.yamato@redhat.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1361334649 25696 80.91.229.3 (20 Feb 2013 04:30:49 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 20 Feb 2013 04:30:49 +0000 (UTC) Cc: emacs-devel@gnu.org To: "'Masatake YAMATO'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 20 05:31:11 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1U81Kp-0006vN-NM for ged-emacs-devel@m.gmane.org; Wed, 20 Feb 2013 05:31:11 +0100 Original-Received: from localhost ([::1]:46055 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U81KU-0006U3-Vp for ged-emacs-devel@m.gmane.org; Tue, 19 Feb 2013 23:30:50 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:52636) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U81KO-0006Tp-A2 for emacs-devel@gnu.org; Tue, 19 Feb 2013 23:30:48 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1U81KM-00069S-TM for emacs-devel@gnu.org; Tue, 19 Feb 2013 23:30:44 -0500 Original-Received: from userp1040.oracle.com ([156.151.31.81]:16690) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1U81KM-00069H-N4 for emacs-devel@gnu.org; Tue, 19 Feb 2013 23:30:42 -0500 Original-Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id r1K4UeRM031997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 20 Feb 2013 04:30:41 GMT Original-Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r1K4UdVn016501 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 20 Feb 2013 04:30:40 GMT Original-Received: from abhmt120.oracle.com (abhmt120.oracle.com [141.146.116.72]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id r1K4UdnH016641; Tue, 19 Feb 2013 22:30:39 -0600 Original-Received: from dradamslap1 (/71.202.147.44) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Tue, 19 Feb 2013 20:30:39 -0800 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <20130220.111807.1912441579815160723.yamato@redhat.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 Thread-Index: Ac4PEIjWAV+Ib5gzQeGQtzQn8krC3wAD0NBA X-Source-IP: acsinet22.oracle.com [141.146.126.238] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 156.151.31.81 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:157186 Archived-At: > ( I'm cheering those who are working on improving register:) > I used to try but I could not show a good result[1][2]. > I still believe register facility should be imporved > massively. ) > > [1] > https://lists.gnu.org/archive/html/emacs-devel/2004-03/msg00345.html > [2] > https://lists.gnu.org/archive/html/emacs-devel/2004-03/msg00349.html I don't disagree that registers could be more useful. Dunno about "massively", but I'm sure some more could be done. (More could also be done with Lisp variables for interactive use, IMO.) Something I use are some trivial commands that copy register contents to a variable and vice versa. Likewise, copy between a register and the last kill. Nothing spectacular. (I took the `register-*able-p' functions for the patch from that code, BTW.) > > 4. In `list-registers': Raise error if `register-alist' is empty. > > Just question. Is this error raising really needed? Personally, I don't really care one way or the other - (a) show a message and do nothing or (b) raise an error. IMO, a message (error or not) is more useful in this case than opening an empty `*Output*' buffer showing there are no registers. In my case, FWIW, that pops up a new frame - silly, if not quite annoying. (I probably should also have proposed a new name for that buffer, BTW - `*Output*' suggests that little reflection went into the name. `*Registers*' or `*Register List*' would be better.) Now, there could be a question whether `list-registers' also has some non-interactive use. If so, and if we are concerned about a message (error or not) when not used interactively, then we can add a MSGP optional arg etc. The same holds for some of the other commands here. I think it's good the way I defined it (show an error msg if no registers), but I don't feel strongly about it at all. I do think it's a bit silly to create a window or frame showing an empty `*Output*' buffer.) > `list-processes' says nothing even if no child process is. > `list-directory' says nothing even if the directory given as > argument is empty. FWIW, I don't see either of those as very comparable to `list-registers'. Certainly not the Dired case. You can work in an empty directory, doing lots of things (including creating files and subdirs, search below in multiple subdirs, etc.).