From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.bugs Subject: bug#7567: Please add a history variable to read-regexp Date: Mon, 6 Dec 2010 16:31:12 -0800 Message-ID: References: <2609D1C2B5E5457EA2582273774B4CE2@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1291682739 4758 80.91.229.12 (7 Dec 2010 00:45:39 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 7 Dec 2010 00:45:39 +0000 (UTC) Cc: 7567@debbugs.gnu.org To: "'Lennart Borgman'" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Dec 07 01:45:34 2010 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1PPlgR-0002z9-KD for geb-bug-gnu-emacs@m.gmane.org; Tue, 07 Dec 2010 01:45:31 +0100 Original-Received: from localhost ([127.0.0.1]:34285 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PPlgQ-0003Yq-V2 for geb-bug-gnu-emacs@m.gmane.org; Mon, 06 Dec 2010 19:45:31 -0500 Original-Received: from [140.186.70.92] (port=46817 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PPlgL-0003SR-Ci for bug-gnu-emacs@gnu.org; Mon, 06 Dec 2010 19:45:26 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PPlgK-0002Np-5P for bug-gnu-emacs@gnu.org; Mon, 06 Dec 2010 19:45:25 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:33375) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PPlgK-0002Ne-1m for bug-gnu-emacs@gnu.org; Mon, 06 Dec 2010 19:45:24 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1PPlNZ-0003LX-Q4; Mon, 06 Dec 2010 19:26:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: "Drew Adams" Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 07 Dec 2010 00:26:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 7567 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 7567-submit@debbugs.gnu.org id=B7567.129168153012819 (code B ref 7567); Tue, 07 Dec 2010 00:26:01 +0000 Original-Received: (at 7567) by debbugs.gnu.org; 7 Dec 2010 00:25:30 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1PPlN3-0003Ki-RS for submit@debbugs.gnu.org; Mon, 06 Dec 2010 19:25:30 -0500 Original-Received: from rcsinet10.oracle.com ([148.87.113.121]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1PPlN2-0003KU-EU for 7567@debbugs.gnu.org; Mon, 06 Dec 2010 19:25:28 -0500 Original-Received: from rcsinet13.oracle.com (rcsinet13.oracle.com [148.87.113.125]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id oB70VK08010097 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Dec 2010 00:31:21 GMT Original-Received: from acsmt353.oracle.com (acsmt353.oracle.com [141.146.40.153]) by rcsinet13.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id oB6Gb6W3007496; Tue, 7 Dec 2010 00:31:19 GMT Original-Received: from abhmt013.oracle.com by acsmt355.oracle.com with ESMTP id 849732591291681875; Mon, 06 Dec 2010 16:31:15 -0800 Original-Received: from dradamslap1 (/130.35.178.194) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 06 Dec 2010 16:31:11 -0800 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Thread-Index: AcuVnJnryxKQRKDTSUOI13+ER+tRfwABQ/Ew X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Mon, 06 Dec 2010 19:26:01 -0500 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:42246 Archived-At: > >> Why should that regexp be used to make buffer names? It is=20 > >> probably a regexp that has been used for matching strings in = buffers. > > > > Why is it "probably" that? > > > > I use regexps interactively all over the place. =A0Matching=20 > > text in a buffer is only one use. >=20 > Can you give examples of other interactive uses, please? That might > make it easier to know what we are really talking about. Use your imagination. But yes, of course anything _could_ be put in a = buffer, so conceivably any use of a regexp could involve matching some buffer's = text... What about the very functions you mentioned? Why wouldn't regexps they = read also be useful in some buffer? Or vice versa, why couldn't some = buffer-text regexp be useful for those functions? Anyway, if you insist, here are a few examples: = `icicle-customize-apropos': Customize all user options matching REGEXP. Likewise, customize faces = and groups. Likewise Icicles apropos functions. I even use it in the = Icicles version of `apropos-zippy' (but the vanilla version uses (interactive = "s...")). `icicle-find-tag': Navigate among all tags whose names match REGEXP. I = use it for `icicle-keyword-list', which reads a list of keywords, each of which = could actually be a regexp. I use it in `icicle-widen-candidates', which adds completion candidates based on an alternative regexp. And there are specialized vanilla regexp histories, such as `dired-regexp-history'. And you yourself mentioned matching a buffer name. (I do that in `icicle-add-buffer-config', for instance: buffer names to match for = inclusion and for exclusion as completion candidates.) Now you can imagine lots of others, I think. A regexp can be used = anywhere, and a function to read a regexp can be used in any regexp use case. I guess what I'd really like to ask you is this: Please give a reason = why `read-regexp', which is extremely general, should _not_ use the general = regexp history variable.