From: Vin Shelton <ethersoft@gmail.com>
To: zsh-workers@sunsite.dk
Subject: dropped first character
Date: Mon, 21 Mar 2005 09:51:05 -0500 [thread overview]
Message-ID: <20a80721050321065141ce9df1@mail.gmail.com> (raw)
In-Reply-To: <422906C2006D5427@n056.sc0.cp.net>
Hello -
In the latest CVS sources, I've seen the first character on the line
dropped, although I cannot yet reproduce this behavior consistently in
a fresh shell. Here's what I've seen a couple of times (cut and
pasted from a shell window):
: build/xemacs-21.5-2005-03-19-gcc-mule Mon 21 8:58; make check >& check.out
make install >& inst.out
boise [make check >& check.out]
~/software/SunOS-5.5/build/xemacs-21.5-2005-03-19-gcc-mule 9:07AM
: build/xemacs-21.5-2005-03-19-gcc-mule Mon 21 9:07; ake install >& inst.out
boise [ake install >& inst.out]
~/software/SunOS-5.5/build/xemacs-21.5-2005-03-19-gcc-mule 9:07AM
: build/xemacs-21.5-2005-03-19-gcc-mule Mon 21 9:07; cat inst.out
zsh: command not found: ake
Notice that I typed in:
make check >& check.out
and then
make install >& inst.out
with the latter being typed while the former was running. You'll
notice that for some reason the shell thought I was typing 'ake
install'.
Both times I have seen this the literal commands have been exactly the
same: 'make check' followed by 'make install', with redirected stdout
and stderr for both commands.
This is on a SunOS-5.5 system, BTW.
Does anyone have any idea what might be causing this?
- Vin
--
In a minute there is time
For decisions and revisions which a minute will reverse. T.S. Eliot
[URL: http://www.cs.amherst.edu/~ccm/prufrock.html]
next parent reply other threads:[~2005-03-21 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <422906C2006D5427@n056.sc0.cp.net>
2005-03-21 14:51 ` Vin Shelton [this message]
2005-03-21 16:22 ` Bart Schaefer
2005-03-21 16:44 ` Vin Shelton
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=20a80721050321065141ce9df1@mail.gmail.com \
--to=ethersoft@gmail.com \
--cc=zsh-workers@sunsite.dk \
/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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).