Re: emacs problem

On Jul 23 15:44, J. David Boyd wrote: > da...@adboyd.com (J. David Boyd) writes: > > > Ken Brown 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.htm

Re: emacs problem

da...@adboyd.com (J. David Boyd) writes: > Ken Brown 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 t

Re: emacs problem

Ken Brown writes: > On 7/11/2013 10:11 AM, Corinna Vinschen wrote: >> On Jul 11 09:34, J. David Boyd wrote: >>> Ken Brown 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

Re: emacs problem

On 7/11/2013 10:11 AM, Corinna Vinschen wrote: On Jul 11 09:34, J. David Boyd wrote: Ken Brown 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 f

Re: emacs problem

On Jul 11 09:34, J. David Boyd wrote: > Ken Brown 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

Re: emacs problem

Ken Brown 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

Re: emacs problem

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: > >>>

Re: emacs problem

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

Re: emacs problem

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

Re: emacs problem

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

Re: emacs problem

Ken Brown writes: > On 7/10/2013 3:07 PM, J. David Boyd wrote: >> Ken Brown 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\emac

Re: emacs problem

On 7/10/2013 3:07 PM, J. David Boyd wrote: Ken Brown 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 - fai

Re: emacs problem

Ken Brown 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 s

Re: emacs problem

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 trie

Re: emacs problem starting with 20121123 snapshot

On Sun, Dec 23, 2012 at 07:16:32AM -0500, Ken Brown wrote: >On 12/19/2012 9:46 AM, Ken Brown wrote: >> Starting with the 20121123 snapshot, emacs won't run under X11. > >This is fixed in the snapshot of 2012-12-22 19:41:44. Thanks cgf. Thanks for the confirmation. I was going to send out a notic

Re: emacs problem starting with 20121123 snapshot

On 12/19/2012 9:46 AM, Ken Brown wrote: Starting with the 20121123 snapshot, emacs won't run under X11. This is fixed in the snapshot of 2012-12-22 19:41:44. Thanks cgf. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation

Re: Emacs problem with Cygwin 1.5.17-1 (rebasing)

I want to complete the story which has some point of interest. Obviously, you are not obliged to replay, not to take care of problems. As you can see from this mailing list, after installing the cygwin package 1.5.17-1 (26-27 May) I had a problem with Emacs: it took all CPU (100%) and its window

Re: Emacs problem with Cygwin 1.5.17-1

Thanks for the "rapid communications" I have resolve downgrading to 1.5.16-1. angelo. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin

Re: Emacs problem with Cygwin 1.5.17-1

On Fri, Jun 03, 2005 at 10:02:09PM +0200, Angelo Graziosi wrote: >"No one is obligated" but when one one is asked for something: > > > >and one answers > > > >it is natural to wait for

Re: Emacs problem with Cygwin 1.5.17-1

"No one is obligated" but when one one is asked for something: and one answers it is natural to wait for a response, a simple response as "Ok received!" or sometghing else only t

Re: Emacs problem with Cygwin 1.5.17-1

At 01:37 PM 6/2/2005, you wrote: >On Wed, 1 Jun 2005 19:09:35 -0400 , Christopher Faylor wrote: > >>Please stop doing this. I do read email. I will read your email >>when I have time. Pinging me is not going to help. > >You should at least answer "OK. the problem is under investigation" or >so

Re: Emacs problem with Cygwin 1.5.17-1

On Wed, 1 Jun 2005 19:09:35 -0400 , Christopher Faylor wrote: >Please stop doing this. I do read email. I will read your email >when I have time. Pinging me is not going to help. You should at least answer "OK. the problem is under investigation" or something else. angelo. -- Unsubscribe

Re: Emacs problem with Cygwin 1.5.17-1 (CGF, a little comment)

On Wed, Jun 01, 2005 at 11:51:34PM +0200, Angelo Graziosi wrote: > Please stop doing this. I do read email. I will read your email when I have time. Pinging me is not going to help. cgf -- Unsubscribe info: http://cygwin.com/ml/#un

Re: Emacs problem with Cygwin 1.5.17-1 (CGF, a little comment)

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

Re: Emacs problem with Cygwin 1.5.17-1

I remember you, that reinstalling Cygwin 1.5-16-1 (and keeping coreutils 5.3.0-6) Emacs works fine. I would keep 1.5.17-1 because it allow me to build CERNLIB-2005 with a limited number of patches (with 1.5.16-1 there is something more to patch) I have also tried XEmacs 21.4.17-1. It starts and

Re: Emacs problem with Cygwin 1.5.17-1 (CGF please comment) (fwd)

-- Forwarded message -- Date: Mon, 30 May 2005 19:07:56 +0200 (MET DST) From: Angelo Graziosi <[EMAIL PROTECTED]> To: cygwin-xfree@cygwin.com Subject: Re: Emacs problem with Cygwin 1.5.17-1 (CGF please comment) I pointed out a problem between Emacs (21.2-13, i.e. curr

Re: emacs problem results from bad $HOME value

Sarah wrote: > Solved the problem with emacs flaking out. The default values for $HOME > and $home set up in the default .login file were wrong. Hi Sarah, What .login file? (what shell come to that?) > Commented out > the lines that set them and hardcoded the correct location. Pretty You mig

RE: Emacs Problem

* *** |=> -Original Message- |=> From: Randall R Schulz [mailto:[EMAIL PROTECTED]] |=> Sent: Wednesday, January 15, 2003 11:14 PM |=> To: [EMAIL PROTECTED] |=> Subject: Re: Emacs Problem |=&g

Re: Emacs Problem

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

Re: Emacs Problem

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 pr

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

Re: Emacs Problem

"Scott Purcell" <[EMAIL PROTECTED]> 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-bu

Re: Emacs Problem

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 d

Re: emacs problem..

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 >