From: "Kevin Wright" <kevin@wright.org>
To: "Cygwin-Mailing-List" <cygwin@cygwin.com>
Subject: FW: 1.1.8: tail makes bash/tcsh freeze (?) - solved
Date: Sat, 10 Feb 2001 07:59:00 -0000 [thread overview]
Message-ID: <000201c09371$828fe5f0$7ac1c13f@holstein-mobile.ASPECTDV.COM> (raw)
FYI
-----Original Message-----
From: Satoshige Ukena [ mailto:satosi-u@is.aist-nara.ac.jp ]
Sent: Saturday, February 10, 2001 8:46 AM
To: kevin@wright.org
Cc: satosi-u@is.aist-nara.ac.jp
Subject: RE: 1.1.8: tail makes bash/tcsh freeze (?)
From: "Kevin Wright" <kevin@wright.org>
Subject: RE: 1.1.8: tail makes bash/tcsh freeze (?)
Date: Sat, 10 Feb 2001 07:18:11 -0700
> Satoshige-san,
>
> This is just a guess but what happens if you rename the script to
> something besides aux.sh? I'm thinking that files with the name
> aux get messed up Windows 98 (or any other windows os).
You are right. My procedure doesn't make any sence.
I read Japanese version Cygwin FAQ and wrongly understood
the article "When it hangs, how do I get it back?"
After your pointing out, I read English version and
correctly understood the context;
If something goes wrong and the tools hang on you for some reason
(easy to do if you try and read a file called aux.sh)
In Japanese version, the context can be interpreted as
The hanged tool can easily abort by reading a file called aux.sh
Please tolerate my former so stupid mail because I am newbie.
---
S. Ukena: satosi-u@is.aist-nara.ac.jp
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
reply other threads:[~2001-02-10 7:59 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000201c09371$828fe5f0$7ac1c13f@holstein-mobile.ASPECTDV.COM' \
--to=kevin@wright.org \
--cc=cygwin@cygwin.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.
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).