Since jrsyangl hasn't written back on this one, I have to take the bait
and ask "why CRLF and the lowercase 'e'?".
Thanks in advance,
Paul
Christopher Faylor wrote:
On Mon, Jul 14, 2008 at 04:21:16PM -0400, jrsyangl wrote:
Whenever I try to enter the letter "e", and only for "e" (other le
You could try to remove the /e mount point for testing. It's possible
that the problem I patched yesterday is the cause of the problem.
No, that didn't help. I didn't reboot but I did restart Cygwin which I think
is enough.
For completeness I'm attaching my fstab. Would it help if I change "
On Jul 15 17:35, kalle ko wrote:
> Latest updated cygwin (just updated to make sure), Windows Vista SP1.
>
> This will hang cygwin 1.5.25-cr-0x5f1:
> 1. Create a connected socket
> 2. Send a big enough buffer (> 0x4238 bytes)
> 3. Close the socket
>
> It will hang in the close() function. Only wa
On Jul 15 16:47, Henk van Lingen wrote:
>
> Hi,
>
> I'm a cygwin rookie and can't get I clear clue (after googling) as to why
> after installing cygwin on WinXP I have these permissions:
>
> $ ls -al /cygdrive/c/cygwin/
> total 9
> drwxrwx---+ 11 administrator Users 0 Jul 4 13:52 .
> drwxr
On Jul 15 10:49, Lee Maschmeyer wrote:
> From: "Corinna Vinschen"
> To:
> Sent: Monday, July 14, 2008 16:37
> Subject: Re: A path that's invalid on 1.7 but presumably valid on 1.5
>
>
>> On Jul 14 16:21, Lee Maschmeyer wrote:
>>> The invalid path in question: //?/e:cygwin/usr/share/tcl8.4/init.tcl
Latest updated cygwin (just updated to make sure), Windows Vista SP1.
This will hang cygwin 1.5.25-cr-0x5f1:
1. Create a connected socket
2. Send a big enough buffer (> 0x4238 bytes)
3. Close the socket
It will hang in the close() function. Only way is to kill it with
taskmanager or close the cyg
From: "Corinna Vinschen"
To:
Sent: Monday, July 14, 2008 16:37
Subject: Re: A path that's invalid on 1.7 but presumably valid on 1.5
On Jul 14 16:21, Lee Maschmeyer wrote:
The invalid path in question: //?/e:cygwin/usr/share/tcl8.4/init.tcl.
This
is the path as supplied by tcl. To make it wo
Hi,
I'm a cygwin rookie and can't get I clear clue (after googling) as to why
after installing cygwin on WinXP I have these permissions:
$ ls -al /cygdrive/c/cygwin/
total 9
drwxrwx---+ 11 administrator Users 0 Jul 4 13:52 .
drwxrwxr-x+ 11 Administrators SYSTEM0 Jul 15 11:10 ..
-rwxr-x
Quoting Christopher Faylor <[EMAIL PROTECTED]>:
Why are you responding to this email 5+ months after it was sent?
Distraction by incoming mails has been recognized as the main reason
for low output by programmers. The cure is to switch to batch mode in
email processing, like once in 5 mon
> From: Christopher Faylor
>> I wrote:
>> Reference: http://sourceware.org/ml/cygwin/2008-02/msg00181.html
>> ...
>>
>> "SHELL The full pathname to the shell is kept in this environment variable."
>>
>> It may also be read from:
>>http://www.gnu.org/software/bash/manual/bashref.html
>
> Why are y
On Tue, Jul 15, 2008 at 01:27:18AM -0700, Pedro Izecksohn wrote:
>Reference: http://sourceware.org/ml/cygwin/2008-02/msg00181.html
>
>"Are you sure SHELL was exported to the environment, and not just in the bash
>shell variable namespace?"
>
>It is a documentation problem, from man bash:
>
>"SHELL
Will writes
> I don't know if there's one specifically for NTEmacs, but gnu.emacs.help
> answers NTEmacs questions.
Thx for the pointer. Haven't thought about it.
--
Rolf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
D
Andy writes
[snip]
> I do run NTemacs with cygwin. I do so becuase for a long time the cyugwin
> emaxs was broken and/or horribly slow compared to the NTemacs port, and
> requires an X11 server to have a GUI.
>
> Try running "python -i" to force interactive behaviour - this works for me.
Yes,
On Mon, 14 Jul 2008 20:18:12 GMT, rolf wrote:
> René Berber writes:
>
>
> [snip]
>> Just for reference, with XEmacs opening a shell:
>>
>> sh-3.2$ echo $TERM
>> dumb
>> sh-3.2$ echo $TERMCAP
>> emacs:co#79:tc=unknown:
>> sh-3.2$ python
>> Python 2.5.1 (r251:54863, May 18 2007, 16:56:43)
>> [GCC
Reference: http://sourceware.org/ml/cygwin/2008-02/msg00181.html
"Are you sure SHELL was exported to the environment, and not just in the bash
shell variable namespace?"
It is a documentation problem, from man bash:
"SHELL The full pathname to the shell is kept in this environment variable."
I
15 matches
Mail list logo
