unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Subject: [raman@users.sf.net: shell-mode: cursor Point loses on long prompts:]
Date: Tue, 10 Oct 2006 12:47:19 -0400	[thread overview]
Message-ID: <E1GXKlD-0004ni-2k@fencepost.gnu.org> (raw)

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

I am not sure whether it is better to fix this or leave it alone,
but we should figure out what's wrong before deciding that.

------- Start of forwarded message -------
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 9 Oct 2006 18:36:00 -0700
To: emacs-devel@gnu.org
From: "T. V. Raman" <raman@users.sf.net>
Subject: shell-mode: cursor Point loses on long prompts:
Reply-To: raman@users.sf.net
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed 
	version=3.0.4

I admit this is somewhat pathological --- but I've hit it a
couple of times when  in directories that have long names (with
lots of white space chars in the dir name).
(you end up running into more and more of these as you rip CDs to
MP3)

If you have bash showing the working directory, for instance my
PS1 is 

\t \h \W $


then after executing commands like ls in such a directory, c-p no
longer moves  point past the recently displayed prompt.

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.

- -- 
Best Regards,
- --raman

      
Email:  raman@users.sf.net
WWW:    http://emacspeak.sf.net/raman/
AIM:    emacspeak       GTalk: tv.raman.tv@gmail.com
PGP:    http://emacspeak.sf.net/raman/raman-almaden.asc
Google: tv+raman 
IRC:    irc://irc.freenode.net/#emacs


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
------- End of forwarded message -------

             reply	other threads:[~2006-10-10 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 16:47 Richard Stallman [this message]
2006-10-18  4:59 ` [raman@users.sf.net: shell-mode: cursor Point loses on long prompts:] Chong Yidong
  -- 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=E1GXKlD-0004ni-2k@fencepost.gnu.org \
    --to=rms@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).