From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: jimka Newsgroups: gmane.emacs.help Subject: Re: emacs shell cursor movement is broken in 22.1 Date: Sun, 16 Mar 2008 09:03:22 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: <3c0dda17-2476-4d2b-b1f2-c101b4a0f576@s13g2000prd.googlegroups.com> <7eff3d6e-7425-418b-8c94-0cbc9b60a7fe@v3g2000hsc.googlegroups.com> <79d5945c-cfff-4029-a3ab-adc896c10d9e@m36g2000hse.googlegroups.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1205685687 16427 80.91.229.12 (16 Mar 2008 16:41:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 16 Mar 2008 16:41:27 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Mar 16 17:41:56 2008 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Javvn-0005aT-6A for geh-help-gnu-emacs@m.gmane.org; Sun, 16 Mar 2008 17:41:55 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JavvD-0007ED-Li for geh-help-gnu-emacs@m.gmane.org; Sun, 16 Mar 2008 12:41:19 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!postnews.google.com!x30g2000hsd.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 29 Original-NNTP-Posting-Host: 83.236.2.86 Original-X-Trace: posting.google.com 1205683402 17836 127.0.0.1 (16 Mar 2008 16:03:22 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Sun, 16 Mar 2008 16:03:22 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: x30g2000hsd.googlegroups.com; posting-host=83.236.2.86; posting-account=hcE4OwoAAADycW4UgYxbAF_GOWiPYhXJ User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.8.1.12) Gecko/20080203 SUSE/2.0.0.12-0.1 Firefox/2.0.0.12, gzip(gfe), gzip(gfe) Original-Xref: shelby.stanford.edu gnu.emacs.help:157075 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:52446 Archived-At: On Mar 16, 4:49 pm, Peter Dyballa wrote: > > Why do you useshellmechanisms? GNU Emacs has more efficient ways to > retrieve an elderlyshellcommand ... (comint-previous-matching-input > or M-r for example) > > > Pete > yes it is always the case with emacs that there is a more efficient way in terms of fewer keystokes. but i think the question of how to most efficiently do a job-X in emacs is an independent question from why did the full-screen-editing features of the emacs shell regress. Don't you agree? By the way i do often use C-r to find the previous comand which matches some pattern and either press enter twice to execute it again, or press enter to leave the search mode, then edit the command and enter it again. C-r has a great advantage over M-r because it lets me see the context in which something happened and also lets me match things that were not shell commands at all but might look like shell commands. -jim