unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: [raman@users.sf.net: shell-mode: cursor Point loses on long prompts:]
Date: Wed, 18 Oct 2006 00:59:30 -0400	[thread overview]
Message-ID: <87pscq43t9.fsf@furball.mit.edu> (raw)
In-Reply-To: <E1GXKlD-0004ni-2k@fencepost.gnu.org> (Richard Stallman's message of "Tue\, 10 Oct 2006 12\:47\:19 -0400")

Richard Stallman <rms@gnu.org> writes:

> It sounds like this is a bug in the field handling of line-move.
> Would someone please investigate, then respond with the diagnosis?

The trouble is that line-move-1 calls `beginning-of-line', then
(vertical-motion -1).  On field on a continued line, this doesn't move
far enough, and we return to the original position when trying to
return to the old column.  I installed a hack to work around this.

> Here is a test case, comprised  the lines pasted from the shell
> buffer, interspersed with comments:
>
> #cd to /tmp and make a bogus directory there:
> mkdir 'a     directory         with     a     very     long     file name '
> 18:27:21 labrador tmp $ cd a\ \ \ \ \ directory\ \ \ \ \ \ \ \ \ with\ \ \ \ \ a\ \ \ \ \ very\ \ \ \ \ long\ \ \ \ \ file\ name\ /
> 18:27:28 labrador a     directory         with     a     very long     file name  $ ls
> 18:27:39 labrador a     directory         with     a     very     long     file name  $ 
>
> #execute ls, after the next prompt is displayed, pressing c-p
>  leaves  point trapped after the prompt. Hitting C-c C-p moves
>  prompt correctly to the line where ls was executed.

  reply	other threads:[~2006-10-18  4:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 16:47 [raman@users.sf.net: shell-mode: cursor Point loses on long prompts:] Richard Stallman
2006-10-18  4:59 ` Chong Yidong [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-10-17 12:34 Richard Stallman
2006-10-24 17:43 Richard Stallman
2006-10-24 19:51 ` Chong Yidong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pscq43t9.fsf@furball.mit.edu \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).