From: Dan Jacobson <jidanni@dman.ddts.net>
Subject: *shell* sometimes eats first char of command
Date: Thu, 17 Apr 2003 07:50:01 +0800 [thread overview]
Message-ID: <87of36vw7q.fsf@jidanni.org> (raw)
Sometimes in *shell*, apparently emacs loses track of where the prompt
ends and command begins.
t r u e <return> C-c C-p C-c C-c <return>
bash: rue: command not found
that was with PS1='$ '. Here is some other scenes from real life. I
didn't keep track of my previous strokes though:
07:26 ~$ shar /tmp/f|mail -s bug bugs@gnus.org
07:29 1 ~$ bash: har: command not found
Null message body; hope that's ok
Yes, if I just typed the commands in without using any C-c stuff, it
probably wouldn't have occurred.
reply other threads:[~2003-04-16 23:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87of36vw7q.fsf@jidanni.org \
--to=jidanni@dman.ddts.net \
/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).