From: npostavs@users.sourceforge.net
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: 27405@debbugs.gnu.org
Subject: bug#27405: 25.2; Make eshell-next-prompt more reliable
Date: Sat, 17 Jun 2017 18:13:44 -0400 [thread overview]
Message-ID: <87zid6qn3b.fsf@users.sourceforge.net> (raw)
In-Reply-To: <20170617090813.GA889@gmail.com> (Pierre Neidhardt's message of "Sat, 17 Jun 2017 10:08:13 +0100")
severity 27405 minor
tags 27405 + confirmed
quit
Pierre Neidhardt <ambrevar@gmail.com> writes:
> Current definition of `eshell-next-prompt' merely skips a
> paragraph. This won't produce the right result as soon the output
> contains a paragraph separator (typically an empty line).
>
> I have been using the following redefinition for a while and it works much
> better for me:
Seems reasonable.
> (defun eshell-next-prompt (n)
> "Move to end of Nth next prompt in the buffer.
> See `eshell-prompt-regexp'."
> (interactive "p")
> (re-search-forward eshell-prompt-regexp nil t n)
> (when eshell-highlight-prompt
> (while (not (get-text-property (line-beginning-position) 'read-only) )
> (re-search-forward eshell-prompt-regexp nil t n)))
> (eshell-skip-prompt))
>
> (defun eshell-previous-prompt (n)
> "Move to end of Nth previous prompt in the buffer.
> See `eshell-prompt-regexp'."
> (interactive "p")
> (backward-char)
> (eshell-next-prompt (- n))))
What's the backward-char for?
next prev parent reply other threads:[~2017-06-17 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 9:08 bug#27405: 25.2; Make eshell-next-prompt more reliable Pierre Neidhardt
2017-06-17 22:13 ` npostavs [this message]
2017-06-18 13:29 ` Pierre Neidhardt
2017-06-18 13:52 ` npostavs
2017-06-18 14:19 ` Pierre Neidhardt
2017-07-12 2:16 ` npostavs
2017-07-12 13:06 ` Pierre Neidhardt
2017-07-12 19:26 ` Noam Postavsky
2017-07-21 2:44 ` npostavs
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=87zid6qn3b.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=27405@debbugs.gnu.org \
--cc=ambrevar@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 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).