On Fri, Jan 09, 2004 at 01:01:17PM -0500, Christopher Faylor <[EMAIL PROTECTED]> wrote:
> Now, if only I could get Windows to tell me exactly where the bug is
> occurring that would be wonderful.
Have you tried using SAPI? You would have to find the bug first, of course,
but then having windows t
At 01:01 PM 1/9/2004, Christopher Faylor you wrote:
>On Fri, Jan 09, 2004 at 11:50:03AM -0500, Larry Hall wrote:
>>So when you write some code that will cause a "bug", please do so in
>>such a way that it will always segv.
>
>As it turns out, the problems that people are having with Windows ME in
>
On Fri, Jan 09, 2004 at 11:50:03AM -0500, Larry Hall wrote:
>So when you write some code that will cause a "bug", please do so in
>such a way that it will always segv.
As it turns out, the problems that people are having with Windows ME in
recent cygwin snapshots are really SEGV problems, so I've
At 12:33 AM 1/9/2004, Christopher Faylor you wrote:
>On Thu, Jan 08, 2004 at 05:33:23PM -0800, Brian Dessent wrote:
>>"H. James de St. Germain" wrote:
>>>at the time... Its curious that it works in either place and even more
>>>curious that placing it after cygwin starts causes programs like rxvt
On Thu, Jan 08, 2004 at 05:33:23PM -0800, Brian Dessent wrote:
>"H. James de St. Germain" wrote:
>>at the time... Its curious that it works in either place and even more
>>curious that placing it after cygwin starts causes programs like rxvt
>>to core dump.
>
>Why should that be curious? As Chris
"H. James de St. Germain" wrote:
> at the time... Its curious that it works in either place and even more
> curious that placing it after cygwin starts causes programs like rxvt
> to core dump.
Why should that be curious? As Chris pointed out it has to be set
before cygwin1.dll initializes. If
On Thu, Jan 08, 2004 at 03:35:08PM -0700, H. James de St. Germain wrote:
>several people have responded that the CYGWIN environment variable
>should be set in the cygwin.bat file, but for whatever reason, I put it
>in the shell resource file and that fixed the problems i was having at
>the time...
several people have responded that the CYGWIN environment variable
should be set in the cygwin.bat file, but for whatever reason, I put
it in the shell resource file and that fixed the problems i was having
at the time... Its curious that it works in either place and even more
curious that placing
On Thu, 8 Jan 2004, Larry Hall wrote:
> At 05:03 PM 1/8/2004, H. James de St. Germain you wrote:
> >(But doesn't everyone just work in emacs anyway?)
>
> No, if I'm one of "everyone".
Hey, I personally use vi(m). But I do know people who'd like to boot up
emacs as their OS. :-)
> >Then when you
At 05:03 PM 1/8/2004, H. James de St. Germain you wrote:
>(But doesn't everyone just work in emacs anyway?)
No, if I'm one of "everyone".
>Then when you start cygwin, it pops up an rxvt terminal for you.
>
>NOTE: in the past I have had
>
> setenv CYGWIN "tty"
>
>in my resource file (.tcshrc)
To follow up on using rxvt:
I have changed by cygwin.bat to have
rxvt -e tcsh -l
as the final line. (Yes I (currently) like some of the old tcsh
properties over bash (though I've used both over time)) (But
doesn't everyone just work in emacs anyway?)
Then when you start cygwin, it pops u
On Thu, Jan 08, 2004 at 04:44:56PM -0500, Igor Pechtchanski wrote:
>>i don't have a winsup directory (didn't compile cygwin from src) so
>>fixing fhandler_console.cc might be more than i want to attempt.
>>strange though, you would think that if it were that easy the
>>developers would have already
Jim,
Please make sure your mailer respects the Reply-To: header.
Also, if advice given by someone on the Cygwin list helped you, it's
usually a good idea to post a followup to the list stating this, just to
bring things to a closure, so that others searching the archives will see
what worked and w
On Thu, 8 Jan 2004, H. James de St. Germain wrote:
> Control spacebar doesn't work in the standard cygwin terminal. This is
> a problem for those of us who love emacs...
>
> From the cryptic posts I've found on the web, it seems that this results
> because the "C
Control spacebar doesn't work in the standard cygwin terminal. This
is a problem for those of us who love emacs...
>From the cryptic posts I've found on the web, it seems that this
results because the "C-spacebar" is not a recognized ASCII value and
thus is not being &q
15 matches
Mail list logo
