all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: "Simen Heggestøyl" <simenheg@gmail.com>
Cc: 21417@debbugs.gnu.org
Subject: bug#21417: Subject: 25.0.50; Paragraph movement in Eshell
Date: Wed, 06 Nov 2019 02:36:34 +0100	[thread overview]
Message-ID: <87tv7h4wgt.fsf@marxist.se> (raw)
In-Reply-To: <1441395721.2458.0@smtp.gmail.com> ("Simen Heggestøyl"'s message of "Fri, 04 Sep 2015 21:42:01 +0200")

Simen Heggestøyl <simenheg@gmail.com> writes:

> Moving by paragraph in Eshell doesn't work when there's command output
> containing newlines. Consider the following case:
>
> ~ $ foo
> bar
>
> baz
> ~ $
>
> The user has entered the command "foo", which has put out
> "bar\n\nbaz\n". Point is after the second "$".
>
> Now the user hits `C-c C-p' which runs `eshell-previous-prompt', and
> point ends up at the blank line between "bar" and "baz", instead of
> going back to the previous prompt.
>
> It seems that setting `paragraph-separate' to something else than the
> default "[ ]*$" solves the problem, though I'm uncertain what it
> should be set to.

I'm unable to reproduce this on current master.  I tried:

0. emacs -Q
1. M-x eshell
2. emacs --help
3. C-c C-p

At the last command, point correctly moved to the previous prompt.

Can you reproduce this on Emacs 27 or 26?  If yes, could you please
provide more details on how to reproduce it?

Perhaps there is something in the output of the particular command you
used that confused Eshell?  That's just a wild guess, though.

Best regards,
Stefan Kangas





  reply	other threads:[~2019-11-06  1:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 19:42 bug#21417: Subject: 25.0.50; Paragraph movement in Eshell Simen Heggestøyl
2019-11-06  1:36 ` Stefan Kangas [this message]
2019-11-06 12:45   ` simenheg

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

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

  git send-email \
    --in-reply-to=87tv7h4wgt.fsf@marxist.se \
    --to=stefan@marxist.se \
    --cc=21417@debbugs.gnu.org \
    --cc=simenheg@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.