Emacs Problem

Emacs Problem

[Scott Purcell]

Hello,
I got ambitious during lunch and installed emacs. At the cmd line I type in emacs and all works great.

I got one problem though, it will not quit.

I run a standalone emacs on my box and when I quit I hit the keys [ ctrl x c ] and it quits the app.
But in the one that runs in cygwin, it does not.

How do I get cygwin to quit emacs and return to a cmd prompt?

Thanks,
Scott

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Emacs Problem

[Frank Schmitt]

"Scott Purcell" <spurcell@vertisinc.com> writes:

> I run a standalone emacs on my box and when I quit I hit the keys [
> ctrl x c ] and it quits the app.  But in the one that runs in cygwin,
> it does not.

It's "control+c control+x" in Emacs language "C-x C-c". If this doesn't
work try "Meta+x save-buffers-kill-emacs RETURN" (Meta is usually the
Alt key under Cygwin, in Emacs terminology "M-x save-buffers-kill-emacs
RET").

If the C-x C-c doesn't work, this keys are probably bound in some way by
your terminal, over here using rxvt as terminal and tcsh as shell it
works as expected.

-- 
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Emacs Problem

[Randall R Schulz]

Frank, Scott,

This is more likely a Cygwin options problem than it is non-standard key 
bindings in Emacs.

This is reaching the proportions of a FAQ: You need to include "tty" in 
your CYGWIN environment variable, lest the Cygwin tty driver commandeer the 
CTRL-C and send a SIGINT when it's typed.

Randall Schulz


At 13:25 2003-01-15, Frank Schmitt wrote:
>"Scott Purcell" <spurcell@vertisinc.com> writes:
>
> > I run a standalone emacs on my box and when I quit I hit the keys [
> > ctrl x c ] and it quits the app.  But in the one that runs in cygwin,
> > it does not.
>
>It's "control+c control+x" in Emacs language "C-x C-c". If this doesn't
>work try "Meta+x save-buffers-kill-emacs RETURN" (Meta is usually the
>Alt key under Cygwin, in Emacs terminology "M-x save-buffers-kill-emacs
>RET").
>
>If the C-x C-c doesn't work, this keys are probably bound in some way by
>your terminal, over here using rxvt as terminal and tcsh as shell it
>works as expected.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Emacs Problem

[David Starks-Browning]

Scott,

You don't say anything about:

 - whether you mean emacs to an X display or "emacs -nw" aka "emacs-nox"
 - assuming the latter, whether in the standard Cygwin command window,
   or rxvt.

I don't think you'll have this problem in rxvt (I don't).  If a
standard command window, does Randall's advice fix the problem?  If so
I'll add something to the FAQ.

Thanks,
David
(Cygwin FAQ maintainer)

On Wednesday 15 Jan 03, Randall R Schulz writes:
> 
> This is reaching the proportions of a FAQ: You need to include "tty" in 
> your CYGWIN environment variable, lest the Cygwin tty driver commandeer the 
> CTRL-C and send a SIGINT when it's typed.
> 
> Randall Schulz


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

emacs problem

[J. David Boyd]

I'm starting to see this error quite a bit in the terminal window I started
emacs from:

0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in
forked process - failed to create new win32 semaphore, Win32 error 87


It seems to take an indeterminate amount of time before it starts happening,
and it _might_ be related to running Gnus, but once it starts, it seems that
almost everything I do in emacs outputs another line like above to the
terminal window.

Any idea how to debug this?

I'm using emacs version "GNU Emacs 24.3.1 (i686-pc-cygwin, GTK+ Version 3.6.4)
 of 2013-03-11 on fiona"


TIA,

Dave


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[Ken Brown]

On 7/10/2013 2:07 PM, J. David Boyd wrote:
>
> I'm starting to see this error quite a bit in the terminal window I started
> emacs from:
>
> 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in
> forked process - failed to create new win32 semaphore, Win32 error 87

Have you tried rebaseall 
(http://cygwin.com/faq.html#faq.using.fixing-fork-failures)?  This isn't 
the typical error message you see from rebase problems, but it can't 
hurt to try.  If that doesn't help, maybe you could test the build I 
mentioned at

   http://cygwin.com/ml/cygwin/2013-07/msg00062.html

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[J. David Boyd]

Ken Brown <kbrown@cornell.edu> writes:

> On 7/10/2013 2:07 PM, J. David Boyd wrote:
>>
>> I'm starting to see this error quite a bit in the terminal window I started
>> emacs from:
>>
>> 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in
>> forked process - failed to create new win32 semaphore, Win32 error 87
>
> Have you tried rebaseall
> (http://cygwin.com/faq.html#faq.using.fixing-fork-failures)?  This
> isn't the typical error message you see from rebase problems, but it
> can't hurt to try.  If that doesn't help, maybe you could test the
> build I mentioned at
>
>   http://cygwin.com/ml/cygwin/2013-07/msg00062.html
>
> Ken

Yes, the first thing I tried was rebaseall, but that also gives (in my
history) the message about not being able to fork a new process.

I'll get your rebuilt verison, and see what happens.  It's worth a shot.

Thanks,

Dave


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[Ken Brown]

On 7/10/2013 3:07 PM, J. David Boyd wrote:
> Ken Brown <kbrown@cornell.edu> writes:
>
>> On 7/10/2013 2:07 PM, J. David Boyd wrote:
>>>
>>> I'm starting to see this error quite a bit in the terminal window I started
>>> emacs from:
>>>
>>> 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in
>>> forked process - failed to create new win32 semaphore, Win32 error 87
>>
>> Have you tried rebaseall
>> (http://cygwin.com/faq.html#faq.using.fixing-fork-failures)?  This
>> isn't the typical error message you see from rebase problems, but it
>> can't hurt to try.  If that doesn't help, maybe you could test the
>> build I mentioned at
>>
>>    http://cygwin.com/ml/cygwin/2013-07/msg00062.html
>>
>> Ken
>
> Yes, the first thing I tried was rebaseall, but that also gives (in my
> history) the message about not being able to fork a new process.

Are you saying you get a fork error when you run rebaseall?  If so, I 
think you need to fix that before you can hope to avoid fork errors in 
emacs.  Have you looked for BLODA?  Other than that, I don't know what 
to suggest (except that you should send cygcheck output when you write 
again).

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[J. David Boyd]

Ken Brown <kbrown@cornell.edu> writes:

> On 7/10/2013 3:07 PM, J. David Boyd wrote:
>> Ken Brown <kbrown@cornell.edu> writes:
>>
>>> On 7/10/2013 2:07 PM, J. David Boyd wrote:
>>>>
>>>> I'm starting to see this error quite a bit in the terminal window I started
>>>> emacs from:
>>>>
>>>> 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in
>>>> forked process - failed to create new win32 semaphore, Win32 error 87
>>>
>>> Have you tried rebaseall
>>> (http://cygwin.com/faq.html#faq.using.fixing-fork-failures)?  This
>>> isn't the typical error message you see from rebase problems, but it
>>> can't hurt to try.  If that doesn't help, maybe you could test the
>>> build I mentioned at
>>>
>>>    http://cygwin.com/ml/cygwin/2013-07/msg00062.html
>>>
>>> Ken
>>
>> Yes, the first thing I tried was rebaseall, but that also gives (in my
>> history) the message about not being able to fork a new process.
>
> Are you saying you get a fork error when you run rebaseall?  If so, I
> think you need to fix that before you can hope to avoid fork errors in
> emacs.  Have you looked for BLODA?  Other than that, I don't know what
> to suggest (except that you should send cygcheck output when you write
> again).
>
> Ken

Wow, sorry, I said that entirely wrong.  I meant that in my recollection, when
I need to rebase, I get messages about "can't create fork".  But that's not
what I said at all.

So this is an entirely different error, but I still rebased, first thing, just
as a SWAG.

I got the emacs from your site, thanks, and I'll keep an eye on it and see how
it goes.

I'll keep you posted.

Dave


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[Christopher Faylor]

On Wed, Jul 10, 2013 at 02:54:59PM -0400, Ken Brown wrote:
>On 7/10/2013 2:07 PM, J. David Boyd wrote:
>>
>> I'm starting to see this error quite a bit in the terminal window I started
>> emacs from:
>>
>> 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in
>> forked process - failed to create new win32 semaphore, Win32 error 87
>
>Have you tried rebaseall 
>(http://cygwin.com/faq.html#faq.using.fixing-fork-failures)?  This isn't 
>the typical error message you see from rebase problems, but it can't 
>hurt to try.  If that doesn't help, maybe you could test the build I 
>mentioned at

That doesn't look like the standard fork problem, Ken.  The error comes
from semaphore::_fixup_after_fork:

  void
  semaphore::_fixup_after_fork ()
  {
    if (shared == PTHREAD_PROCESS_PRIVATE)
      {
	pthread_printf ("sem %p", this);
	/* FIXME: duplicate code here and in the constructor. */
	win32_obj_id = ::CreateSemaphore (&sec_none_nih, currentvalue,
						INT32_MAX, NULL);
	if (!win32_obj_id)
	  api_fatal ("failed to create new win32 semaphore, %E");
      }
  }

Error code 87 is ERROR_INVALID_PARAMETER.  The only two things that I
can see which would cause that problem are "sec_non_nih" and
currentvalue.

I'll change the error to report on currentvalue.  I assume that
currentvalue must be zero for some reason here and that is what is
causing the problem but it would be nice to know for sure.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[Christopher Faylor]

On Wed, Jul 10, 2013 at 04:55:38PM -0400, Christopher Faylor wrote:
>On Wed, Jul 10, 2013 at 02:54:59PM -0400, Ken Brown wrote:
>>On 7/10/2013 2:07 PM, J. David Boyd wrote:
>>>
>>> I'm starting to see this error quite a bit in the terminal window I started
>>> emacs from:
>>>
>>> 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in
>>> forked process - failed to create new win32 semaphore, Win32 error 87
>>
>>Have you tried rebaseall 
>>(http://cygwin.com/faq.html#faq.using.fixing-fork-failures)?  This isn't 
>>the typical error message you see from rebase problems, but it can't 
>>hurt to try.  If that doesn't help, maybe you could test the build I 
>>mentioned at
>
>That doesn't look like the standard fork problem, Ken.  The error comes
>from semaphore::_fixup_after_fork:
>...
>Error code 87 is ERROR_INVALID_PARAMETER.  The only two things that I
>can see which would cause that problem are "sec_non_nih" and
>currentvalue.
>
>I'll change the error to report on currentvalue.  I assume that
>currentvalue must be zero for some reason here and that is what is
>causing the problem but it would be nice to know for sure.

The current snapshot has this change and a shot-in-the-dark attempt to
fix the reported problem as well.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[Ken Brown]

On 7/10/2013 5:10 PM, Christopher Faylor wrote:
> On Wed, Jul 10, 2013 at 04:55:38PM -0400, Christopher Faylor wrote:
>> On Wed, Jul 10, 2013 at 02:54:59PM -0400, Ken Brown wrote:
>>> On 7/10/2013 2:07 PM, J. David Boyd wrote:
>>>>
>>>> I'm starting to see this error quite a bit in the terminal window I started
>>>> emacs from:
>>>>
>>>> 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in
>>>> forked process - failed to create new win32 semaphore, Win32 error 87
>>>
>>> Have you tried rebaseall
>>> (http://cygwin.com/faq.html#faq.using.fixing-fork-failures)?  This isn't
>>> the typical error message you see from rebase problems, but it can't
>>> hurt to try.  If that doesn't help, maybe you could test the build I
>>> mentioned at
>>
>> That doesn't look like the standard fork problem, Ken.  The error comes
>>from semaphore::_fixup_after_fork:
>> ...
>> Error code 87 is ERROR_INVALID_PARAMETER.  The only two things that I
>> can see which would cause that problem are "sec_non_nih" and
>> currentvalue.
>>
>> I'll change the error to report on currentvalue.  I assume that
>> currentvalue must be zero for some reason here and that is what is
>> causing the problem but it would be nice to know for sure.
>
> The current snapshot has this change and a shot-in-the-dark attempt to
> fix the reported problem as well.

Thanks.  It's also possible that this isn't a Cygwin problem.  There are 
known race conditions between emacs-24.3 and glib, which have been fixed 
in the newer version of emacs that I asked Dave to test.

Dave, instead of trying the new emacs right away, would you be willing 
to install the cygwin snapshot and see if that fixes the problem?  If 
not, could you report the error message and then try the new emacs?

Thanks.

Ken

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[Christopher Faylor]

On Wed, Jul 10, 2013 at 05:54:55PM -0400, Ken Brown wrote:
>On 7/10/2013 5:10 PM, Christopher Faylor wrote:
>> On Wed, Jul 10, 2013 at 04:55:38PM -0400, Christopher Faylor wrote:
>>> On Wed, Jul 10, 2013 at 02:54:59PM -0400, Ken Brown wrote:
>>>> On 7/10/2013 2:07 PM, J. David Boyd wrote:
>>>>>
>>>>> I'm starting to see this error quite a bit in the terminal window I started
>>>>> emacs from:
>>>>>
>>>>> 0 [main] emacs-X11 19400 C:\tools\cygwin\bin\emacs-X11.exe: *** fatal error in
>>>>> forked process - failed to create new win32 semaphore, Win32 error 87
>>>>
>>>> Have you tried rebaseall
>>>> (http://cygwin.com/faq.html#faq.using.fixing-fork-failures)?  This isn't
>>>> the typical error message you see from rebase problems, but it can't
>>>> hurt to try.  If that doesn't help, maybe you could test the build I
>>>> mentioned at
>>>
>>> That doesn't look like the standard fork problem, Ken.  The error comes
>>>from semaphore::_fixup_after_fork:
>>> ...
>>> Error code 87 is ERROR_INVALID_PARAMETER.  The only two things that I
>>> can see which would cause that problem are "sec_non_nih" and
>>> currentvalue.
>>>
>>> I'll change the error to report on currentvalue.  I assume that
>>> currentvalue must be zero for some reason here and that is what is
>>> causing the problem but it would be nice to know for sure.
>>
>> The current snapshot has this change and a shot-in-the-dark attempt to
>> fix the reported problem as well.
>
>Thanks.  It's also possible that this isn't a Cygwin problem.  There are 
>known race conditions between emacs-24.3 and glib, which have been fixed 
>in the newer version of emacs that I asked Dave to test.

Given the point at which the problem occurs, I don't see how it could be
anything but a Cygwin problem.  It's in the fork code before anything
user-based should be kicked off.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[J. David Boyd]

Ken Brown <kbrown@cornell.edu> writes:

> On 7/10/2013 5:10 PM, Christopher Faylor wrote:
>
> Thanks.  It's also possible that this isn't a Cygwin problem.  There
> are known race conditions between emacs-24.3 and glib, which have been
> fixed in the newer version of emacs that I asked Dave to test.
>
> Dave, instead of trying the new emacs right away, would you be willing
> to install the cygwin snapshot and see if that fixes the problem?  If
> not, could you report the error message and then try the new emacs?
>
> Thanks.
>
> Ken

THanks, sure, no problem.  Where do I get the latest snapshot from?  Setup and
all updates, or the EXP setting?

Dave


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[Corinna Vinschen]

On Jul 11 09:34, J. David Boyd wrote:
> Ken Brown <kbrown@cornell.edu> writes:
> 
> > On 7/10/2013 5:10 PM, Christopher Faylor wrote:
> >
> > Thanks.  It's also possible that this isn't a Cygwin problem.  There
> > are known race conditions between emacs-24.3 and glib, which have been
> > fixed in the newer version of emacs that I asked Dave to test.
> >
> > Dave, instead of trying the new emacs right away, would you be willing
> > to install the cygwin snapshot and see if that fixes the problem?  If
> > not, could you report the error message and then try the new emacs?
> >
> > Thanks.
> >
> > Ken
> 
> THanks, sure, no problem.  Where do I get the latest snapshot from?  Setup and
> all updates, or the EXP setting?

http://cygwin.com/snapshots/


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[Ken Brown]

On 7/11/2013 10:11 AM, Corinna Vinschen wrote:
> On Jul 11 09:34, J. David Boyd wrote:
>> Ken Brown <kbrown@cornell.edu> writes:
>>
>>> On 7/10/2013 5:10 PM, Christopher Faylor wrote:
>>>
>>> Thanks.  It's also possible that this isn't a Cygwin problem.  There
>>> are known race conditions between emacs-24.3 and glib, which have been
>>> fixed in the newer version of emacs that I asked Dave to test.
>>>
>>> Dave, instead of trying the new emacs right away, would you be willing
>>> to install the cygwin snapshot and see if that fixes the problem?  If
>>> not, could you report the error message and then try the new emacs?
>>>
>>> Thanks.
>>>
>>> Ken
>>
>> THanks, sure, no problem.  Where do I get the latest snapshot from?  Setup and
>> all updates, or the EXP setting?
>
> http://cygwin.com/snapshots/

Dave,

This should be fixed now in the latest snapshot (2013-07-23).  See

   http://cygwin.com/ml/cygwin/2013-07/msg00481.html

Ken


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[J. David Boyd]

Ken Brown <kbrown@cornell.edu> writes:

> On 7/11/2013 10:11 AM, Corinna Vinschen wrote:
>> On Jul 11 09:34, J. David Boyd wrote:
>>> Ken Brown <kbrown@cornell.edu> writes:
>>>
>>>> On 7/10/2013 5:10 PM, Christopher Faylor wrote:
>>>>
>>>> Thanks.  It's also possible that this isn't a Cygwin problem.  There
>>>> are known race conditions between emacs-24.3 and glib, which have been
>>>> fixed in the newer version of emacs that I asked Dave to test.
>>>>
>>>> Dave, instead of trying the new emacs right away, would you be willing
>>>> to install the cygwin snapshot and see if that fixes the problem?  If
>>>> not, could you report the error message and then try the new emacs?
>>>>
>>>> Thanks.
>>>>
>>>> Ken
>>>
>>> THanks, sure, no problem.  Where do I get the latest snapshot from?  Setup and
>>> all updates, or the EXP setting?
>>
>> http://cygwin.com/snapshots/
>
> Dave,
>
> This should be fixed now in the latest snapshot (2013-07-23).  See
>
>   http://cygwin.com/ml/cygwin/2013-07/msg00481.html
>
> Ken

Great, thanks.  I'll get it right away and try it out for a day or so, then
report back here.

Dave


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[J. David Boyd]

david@adboyd.com (J. David Boyd) writes:

> Ken Brown <kbrown@cornell.edu> writes:
>
>>> http://cygwin.com/snapshots/
>>
>> Dave,
>>
>> This should be fixed now in the latest snapshot (2013-07-23).  See
>>
>>   http://cygwin.com/ml/cygwin/2013-07/msg00481.html
>>
>> Ken
>
> Great, thanks.  I'll get it right away and try it out for a day or so, then
> report back here.
>
> Dave

I'm running it now, so far so good.  I'll try everything I can think of, which
is mostly just using org mode to track my work, and gnus for checking
newsgroups.  Usually takes no more than 1 hour or so for it to break.

Thanks,

Dave


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: emacs problem

[Corinna Vinschen]

On Jul 23 15:44, J. David Boyd wrote:
> david@adboyd.com (J. David Boyd) writes:
> 
> > Ken Brown <kbrown@cornell.edu> writes:
> >
> >>> http://cygwin.com/snapshots/
> >>
> >> Dave,
> >>
> >> This should be fixed now in the latest snapshot (2013-07-23).  See
> >>
> >>   http://cygwin.com/ml/cygwin/2013-07/msg00481.html
> >>
> >> Ken
> >
> > Great, thanks.  I'll get it right away and try it out for a day or so, then
> > report back here.
> >
> > Dave
> 
> I'm running it now, so far so good.  I'll try everything I can think of, which
> is mostly just using org mode to track my work, and gnus for checking
> newsgroups.  Usually takes no more than 1 hour or so for it to break.

Thanks for your feedback.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

RE: Emacs Problem

[Dieter Meinert]

-----BEGIN PGP SIGNED MESSAGE-----

Will this go into the FAQ ?

For me the hint solved the problem (cygwin window running
tcsh: setenv CYGWIN tty; emacs [C-X C-C];)

Regards, Dieter 


************************************************************
***********
 * Dr. Dieter Meinert                                      
           *
 * c/o H. Rosen Engineering GmbH    Phone +49-591-9136-493 
           *
 * Am Seitenkanal 8                 Fax +49-591-9136-121   
           *
 * D-49811 Lingen (Ems)             Email
dmeinert@roseninspection.net *
 * Germany                                                 
           *

************************************************************
***********


|=> -----Original Message-----
|=> From: Randall R Schulz [mailto:rrschulz@cris.com]
|=> Sent: Wednesday, January 15, 2003 11:14 PM
|=> To: cygwin@cygwin.com
|=> Subject: Re: Emacs Problem
|=> 
|=> 
|=> Frank, Scott,
|=> 
|=> This is more likely a Cygwin options problem than it is
| => non-standard key 
|=> bindings in Emacs.
|=> 
|=> This is reaching the proportions of a FAQ: You need to 
|=> include "tty" in 
|=> your CYGWIN environment variable, lest the Cygwin tty 
|=> driver commandeer the 
|=> CTRL-C and send a SIGINT when it's typed.
|=> 
|=> Randall Schulz
|=> 
|=> 
|=> At 13:25 2003-01-15, Frank Schmitt wrote:
|=> >"Scott Purcell" <spurcell@vertisinc.com> writes:
|=> >
|=> > > I run a standalone emacs on my box and when I quit
|I  => hit the keys [
|=> > > ctrl x c ] and it quits the app.  But in the one
|that  => runs in cygwin,
|=> > > it does not.
|=> >
|=> >It's "control+c control+x" in Emacs language "C-x
|C-c". If  => this doesn't
|=> >work try "Meta+x save-buffers-kill-emacs RETURN" (Meta
|is  => usually the
|=> >Alt key under Cygwin, in Emacs terminology "M-x 
|=> save-buffers-kill-emacs
|=> >RET").
|=> >
|=> >If the C-x C-c doesn't work, this keys are probably
|bound  => in some way by
|=> >your terminal, over here using rxvt as terminal and
|tcsh  => as shell it
|=> >works as expected.
|=> 
|=> 
|=> --
|=> Unsubscribe info:     
|http://cygwin.com/ml/#unsubscribe-simple => Bug reporting:
|        http://cygwin.com/bugs.html
|=> Documentation:         http://cygwin.com/docs.html
|=> FAQ:                   http://cygwin.com/faq/
|=> 
|=> 

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.3 for non-commercial use <http://www.pgp.com>

iQEVAwUBPiZcRLYBkYAdGmPFAQEhlAf+JPp9vu60t5ZL0UgspybVtVQ2lQJNnvxK
6Tqqbj34UIuKgjoQt1ixMXl5lCrbD2tj+p6sREiVD6zWkRYuqc1qgPmd9lgtJA6S
/0siOBKOx6+5bdoTi2Cbhmp/IlyCXnWq3+z9JGtvcTwjPyS4F3mLBl7/Cisz7mSc
oZIBfJCG0GXbj7Bqf0kn7BaIA+HIfrRYkOTlkTacc0rt3O11Fogmg1Mw6iN09QBu
MmPznctOpDXsPlC8xxNWGe2p9AMj0rsret445M7tddohXrrU/igcjeRk+v8eE5/s
5gy3dsElK4P8Mskt0ZpUc7YtnIKK/Hqtl+nJdpOqCISPgDykJhhs8g==
=jmVC
-----END PGP SIGNATURE-----


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Emacs Problem

[Larry Hall (RFK Partners, Inc)]

At 03:39 PM 1/15/2003, Scott Purcell wrote:
>Hello,
>I got ambitious during lunch and installed emacs. At the cmd line I type in emacs and all works great.
>
>I got one problem though, it will not quit.


Yeah, so?  What's the problem?  Emacs is the end-all of software, right?  It's
supposed to do everything except make your coffee in the morning, no?  So
*why* would you *ever* want to quit from it? ;-) ;-) ;-)

No flames or editor-wars, please! :-)


>I run a standalone emacs on my box and when I quit I hit the keys [ ctrl x c ] and it quits the app.
>But in the one that runs in cygwin, it does not.
>
>How do I get cygwin to quit emacs and return to a cmd prompt?



You're best off re-posting this after reading www.cygwin.com/bugs.html.  The
obvious question that comes to mind for me is - are you running the Cygwin
or Win32 version of Emacs?  I can't tell (and neither can anyone else) from
the information you've sent so far.  That's why we have a recommended 
procedure for posting problem reports.  Take a look at 'em.





Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: Emacs Problem

[Igor Pechtchanski]

On Wed, 15 Jan 2003, Larry Hall (RFK Partners, Inc) wrote:

> At 03:39 PM 1/15/2003, Scott Purcell wrote:
> >Hello,
> >I got ambitious during lunch and installed emacs. At the cmd line I type in emacs and all works great.
> >I got one problem though, it will not quit.
>
> Yeah, so?  What's the problem?  Emacs is the end-all of software, right?  It's
> supposed to do everything except make your coffee in the morning, no?  So
> *why* would you *ever* want to quit from it? ;-) ;-) ;-)
>
> No flames or editor-wars, please! :-)

As one of my friends would say:
- It doesn't make my coffee in the morning? :-o Oh, no!  What have I been
  drinking all these years?
And, as my other friend would say:
- I wish I could just boot emacs as an operating system...
	Igor
P.S. Personally, I use vim :q  No disrespect for Emacs intended.

> [snip]

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Oh, boy, virtual memory! Now I'm gonna make myself a really *big* RAMdisk!
  -- /usr/games/fortune


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

emacs problem..

[Vincent Yau]

Hi I just installed the latest Cygwin today
and I am running it on a Windows 2000 Service Pack 2 box.
I wanted to fire up emacs but it spits out this error message:

   emacs.exe -- Entry point not found
   The procedure entry point TIFFClientOpen could not be
   located in the dynamic link library cygtiff3.dll.

Wonder if I am doing anything wrong?  I have tried reinstalling
and still does not work.  Any tip/pointer much appreciated.

thanks

--Vincent


_____________________________________________________________
Calling all cartoon fans! 

Garfield keeps millions of newspaper readers laughing over their morning corn flakes...now he's waddling into cyberspace to spread his mirth (and girth)!

You can now get the full-color Garfield comic strip e-mailed to you every day of the week -- absolutely FREE! Just go to http://www.garfield.com/signup/ to register!

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: emacs problem..

[Joe Buehler]

Vincent Yau wrote:

> Hi I just installed the latest Cygwin today
> and I am running it on a Windows 2000 Service Pack 2 box.
> I wanted to fire up emacs but it spits out this error message:
> 
>    emacs.exe -- Entry point not found
>    The procedure entry point TIFFClientOpen could not be
>    located in the dynamic link library cygtiff3.dll.
> 
> Wonder if I am doing anything wrong?  I have tried reinstalling
> and still does not work.  Any tip/pointer much appreciated.

Sounds like a version problem.  Which version of cygtiff3.dll do
you have installed?  Look in the /etc/setup/installed.db file
for the tiff package.

It was built against tiff-3.5.7-1.

Joe Buehler




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/