From: Joe Riel <joer@san.rr.com>
To: help-gnu-emacs@gnu.org
Subject: Re: comint-previous-input mangles current line
Date: Tue, 18 Aug 2015 09:30:44 -0700 [thread overview]
Message-ID: <20150818093044.0f3c8438@gauss> (raw)
In-Reply-To: <20150818083256.6edef13d@gauss>
On Tue, 18 Aug 2015 08:32:56 -0700
Joe Riel <joer@san.rr.com> wrote:
> Is there a simple fix for the following problem.
> I'm running shell. I then use C-up (comint-previous-input)
> to scroll through the history of inputs. This
> mangles the input on the screen. For example,
> if I had
>
> src $ echo nonsense
> nonsense
> src $ [type C-up]
>
> The last line becomes
>
> echo nonsensesrc $
>
> That is, the previous command is displayed before the prompt.
>
> Sometimes, when starting emacs this works fine.
> Sometimes it does not. When not, it never works
> properly.
>
Figured it out, need to set the regexp for the prompt.
--
Joe Riel
prev parent reply other threads:[~2015-08-18 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 15:32 comint-previous-input mangles current line Joe Riel
2015-08-18 16:30 ` Joe Riel [this message]
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=20150818093044.0f3c8438@gauss \
--to=joer@san.rr.com \
--cc=help-gnu-emacs@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.
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).