From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Mathias Dahl" Newsgroups: gmane.emacs.devel Subject: Re: let HISTORY arg to read functions be a list of history variables Date: Sun, 1 Jul 2007 15:48:10 +0200 Message-ID: <7dbe73ed0707010648q6b2cd54fn9c1955eeb1729f6f@mail.gmail.com> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1183297702 2404 80.91.229.12 (1 Jul 2007 13:48:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 1 Jul 2007 13:48:22 +0000 (UTC) Cc: Emacs-Devel To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jul 01 15:48:21 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1I4zmm-0006ag-EK for ged-emacs-devel@m.gmane.org; Sun, 01 Jul 2007 15:48:20 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I4zml-0002bO-Om for ged-emacs-devel@m.gmane.org; Sun, 01 Jul 2007 09:48:19 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I4zmh-0002Zf-2V for emacs-devel@gnu.org; Sun, 01 Jul 2007 09:48:15 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I4zmg-0002ZD-Go for emacs-devel@gnu.org; Sun, 01 Jul 2007 09:48:14 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I4zmf-0002Z6-U6 for emacs-devel@gnu.org; Sun, 01 Jul 2007 09:48:13 -0400 Original-Received: from mu-out-0910.google.com ([209.85.134.191]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I4zmf-0006Id-1N for emacs-devel@gnu.org; Sun, 01 Jul 2007 09:48:13 -0400 Original-Received: by mu-out-0910.google.com with SMTP id g7so1566095muf for ; Sun, 01 Jul 2007 06:48:11 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ZFh+TtMXWdlwGfTC5ZO5OJ605nTCb+rkpR8/Ki7hOGAciYHAdubZoHUtHiXe/ib/hTO+IvS/DHZZvS2vTikNclsQTqEWqBuPGgXDtek7drsXtYE72xy4WmCVdqTQROc8gj16O1E3qC09NTrov5RTnwNR69sfREHLqpeBgyQFLEM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=OZhpBysDyA6HoW/2jwbC1IIJH7E9DL0jXvAfYsktQjgE55QVXIoTPQwW9jvezEcFQ6AXz32OwqddfLNTuPUEXN4v9NHm+gGa2r0w60pUIfzCF8bOMltLnGAXyIVu7wKRucMzlll/hxqhyty9mXPD3jg9op5MfhVYgtEoK8AnbKc= Original-Received: by 10.82.182.1 with SMTP id e1mr10715558buf.1183297690587; Sun, 01 Jul 2007 06:48:10 -0700 (PDT) Original-Received: by 10.82.119.11 with HTTP; Sun, 1 Jul 2007 06:48:10 -0700 (PDT) In-Reply-To: Content-Disposition: inline X-detected-kernel: Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:74106 Archived-At: On 7/1/07, Drew Adams wrote: > 1. How about letting the HISTORY argument to read functions (e.g. > `read-string') be a list of history variables, in addition to letting it be > a single history variable? The histories would be appended for user > retrieval. The convention for saving the user input could be either that it > is added to only the first history or that it is added to each of the > histories. > > Then, for example, you could write this and let users use a regexp from > either history: > > (read-string "Regexp: " nil '(hi-lock-regexp-history regexp-history)) We could also allow a function as argument, then you could implement whatever kind of strange source of input history you wanted. Maybe that could be done for the "save back" variable argument you proposed. Just an idea.