From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: JD Smith Newsgroups: gmane.emacs.devel Subject: Re: comint-accumulate-marker Date: Tue, 18 Apr 2006 15:48:23 -0700 Message-ID: References: <15803.128.165.0.81.1145398875.squirrel@webmail.lanl.gov> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1145400553 3671 80.91.229.2 (18 Apr 2006 22:49:13 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 18 Apr 2006 22:49:13 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 19 00:49:10 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FVz0H-0007AC-8x for ged-emacs-devel@m.gmane.org; Wed, 19 Apr 2006 00:49:01 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FVz0G-0005Xy-S4 for ged-emacs-devel@m.gmane.org; Tue, 18 Apr 2006 18:49:00 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FVz05-0005WE-Lz for emacs-devel@gnu.org; Tue, 18 Apr 2006 18:48:49 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FVz03-0005Vt-BJ for emacs-devel@gnu.org; Tue, 18 Apr 2006 18:48:48 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FVz03-0005Vq-3y for emacs-devel@gnu.org; Tue, 18 Apr 2006 18:48:47 -0400 Original-Received: from [80.91.229.2] (helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA:32) (Exim 4.52) id 1FVz11-0008V1-9a for emacs-devel@gnu.org; Tue, 18 Apr 2006 18:49:47 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FVyzr-00075Y-6I for emacs-devel@gnu.org; Wed, 19 Apr 2006 00:48:35 +0200 Original-Received: from turtle.as.arizona.edu ([128.196.208.207]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Apr 2006 00:48:35 +0200 Original-Received: from jdsmith by turtle.as.arizona.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 19 Apr 2006 00:48:35 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 31 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: turtle.as.arizona.edu User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table) 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:53037 Archived-At: On Tue, 18 Apr 2006 15:21:15 -0700, Stuart D. Herring wrote: >> I will install it shortly, but wanted to run one more variant of the >> patch by everyone first. This version is permanently enabled. It >> also saves input even when you use M-r/M-s, and it binds "C-c C-g" to >> a new function `comint-restore-input', so no matter where you are on >> the history ring, you can zap back to your stranded partial input >> with C-c C-g. Let me know if that's a good binding (and where it >> should be documented). > > This might make this into a "don't install now" new feature, but would it > be preferable to treat all lines of the history like the current input? > Readline does this, I believe, at least until you finally submit a line > (at which point any changes to other lines might be forgotten -- I forget > on this part). In other words, typing > > foo > bar > red > > sends `rebar' as a command, and (possibly) replaces `foo' with `food' in > the history. This is of course technically orthogonal to the current > question, since it's about preserving editing done to history elements > rather than to the current input (which is not a history element), but > it's much the same to the user. While the concept of editing history does have a particular resonance given our current political climate ;), I thought about this and decided it deviated too far from the "fix the broken behavior" flavor of the current proposed patch.