From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: wainstead@gmail.com Newsgroups: gmane.emacs.help Subject: Re: emacs shell cursor movement is broken in 22.1 Date: Fri, 14 Mar 2008 19:41:49 -0700 (PDT) Organization: http://groups.google.com Message-ID: References: <3c0dda17-2476-4d2b-b1f2-c101b4a0f576@s13g2000prd.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 1205556728 15417 80.91.229.12 (15 Mar 2008 04:52:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 15 Mar 2008 04:52:08 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Mar 15 05:52:37 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 1JaONm-0007dL-4i for geh-help-gnu-emacs@m.gmane.org; Sat, 15 Mar 2008 05:52:34 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JaONC-00069n-Ax for geh-help-gnu-emacs@m.gmane.org; Sat, 15 Mar 2008 00:51:58 -0400 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!postnews.google.com!2g2000hsn.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 61 Original-NNTP-Posting-Host: 24.90.108.63 Original-X-Trace: posting.google.com 1205548909 32214 127.0.0.1 (15 Mar 2008 02:41:49 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Sat, 15 Mar 2008 02:41:49 +0000 (UTC) Complaints-To: groups-abuse@google.com Injection-Info: 2g2000hsn.googlegroups.com; posting-host=24.90.108.63; posting-account=X497cgoAAAB7BiTJ3VNbOuXrk-rnMWWL User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.12) Gecko/20080201 Firefox/2.0.0.12,gzip(gfe),gzip(gfe) Original-Xref: shelby.stanford.edu gnu.emacs.help:157051 X-Mailman-Approved-At: Sat, 15 Mar 2008 00:51:26 -0400 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:52423 Archived-At: On Mar 13, 4:44 pm, jimka wrote: > I've used the emacs shell for 20 years and emacs 22.1 has added a > bunch > of "features" which make like difficult. > > Can someone explain to me how to make the cursor navigation functions > work in a more sane way. > > E.g., > > 1) if i use the shell command !!:p to print the previous shell > command. > In previous versions of emacs i could simply edit that line and press > return and > it would enter it as the next input to the shell. Now, emacs 22.1 > ignores it > when i press enter on such a line. > > 2) if i use !!:p to print the shell command such as "ls -R > xyzzy*.x.y.*" > then move the curser up to the line and insert something at the > beginning of the line > like cd /xyzzy; so that the new line content is "cd /xyzzy;ls -R > xyzzy*.x.y.*" > > At that point if i press C-E to go to the end of the line and C-A to > go to > the beginning of the line, the cursor stops at the ls -l, and does not > move back to the REAL > beginning of the line. I've checked and C-A is still bound to move- > beginning-of-line > and i looked at the elisp code for move-beginning-of-line and cannot > figure out > why it is not really going to the beginning, and how to influence it > to do sl. > > 3) similarly on the above line "cd /xyzzy;ls -R xyzzy*.x.y.*" pressing > C-K > only cuts the part from cd /xyzzy;. ie. it does not cut to the end of > the line > like it did for the past 20 years. kill-line seems to still be bound > to kill-line > and in every other mode kill-line really kills the rest of the line. > > Can someone please give me some clues about what is going wrong? > Maybe it is some minor mode i need to disable??? > > many thanks > -jim Hi Jim, Like you I've used shell mode for years. The problems you see started a few years ago, showing up in the OS X build; now they are in the Linux build as well. This week I'm in Japan and am meeting with one of the maintainers. I am hoping to demo these bugs to him and get his feedback. It's high time these were addressed. ~swain