This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
RE: vi, emacs do nothing, not even error out or not found
- From: "Dave Korn" <dave dot korn at artimi dot com>
- To: "'obviously doesn't realise what he's let himself in for...'" <cygwin-talk at cygwin dot com>
- Date: Mon, 5 Feb 2007 18:16:46 -0000
- Subject: RE: vi, emacs do nothing, not even error out or not found
- References: <004301c7494e$a5444520$04000100@DJ62W3B1>
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
On 05 February 2007 17:54, Arved Sandstrom wrote:
> I've used cygwin in the distant past, several times, and I don't remember
> this being a problem. What I mean by "doing nothing" is just that - I type
> "vi", "vim", "emacs" (they are all installed) and I simply return to a new
> prompt. There is no error, because the programs are evidently found; they
> are in my PATH.
Say, what does this have to do with hippos anyway?
> I can't imagine that it's an X issue - PuTTy doesn't have a problem running
> vi when I contact from Windows to Linux. After all, you are just temporarily
> swapping out the contents of the terminal window.
>
> I'd prefer an error, because that would indicate what's happening.
$ vi && echo $?
228
$ grep 228 /usr/include/sys/errno.h
#define EHIPPOHEAD /* A hippo has fallen on my head */
> I've tried with both the Windows console and rxvt. There is no difference.
Perhaps you should try with crayons and paper, or an etch-a-sketch?
> Thank you.
No, no need. No, there's *really* no need.....
cheers,
DaveK
--
Can't think of a witty .sigline today....