This is the mail archive of the
mailing list for the cygwin project.
Re: vi, emacs do nothing, not even error out or not found
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
- Date: Mon, 5 Feb 2007 15:29:57 -0500
- Subject: Re: vi, emacs do nothing, not even error out or not found
- References: <004301c7494e$a5444520$04000100@DJ62W3B1> <02c601c74951$cba36450$2e08a8c0@CAM.ARTIMI.COM>
- Reply-to: cygwin-talk at cygwin dot com
- Reply-to: The Cygwin-Talk Maiming List <cygwin-talk at cygwin dot com>
On Mon, Feb 05, 2007 at 06:16:46PM -0000, Dave Korn wrote:
>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 $?
>$ grep 228 /usr/include/sys/errno.h
>#define EHIPPOHEAD /* A hippo has fallen on my head */
Once again regretting going back to being in a cubicle...
"The snort heard round the office..."