From: "Rockefeller, Harry" <Harry.Rockefeller@flightsafety.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Rebase, Peflags, and cygserver
Date: Fri, 27 Mar 2015 15:45:00 -0000 [thread overview]
Message-ID: <0a1b83ad787f4b32b383c3c633b1c087@vsrv060ex03.ssd.fsi.com> (raw)
In-Reply-To: <gjubpp7uy0nm.fsf@W0144758.usac.mmm.com>
>-----Original Message-----
>From: cygwin-owner@cygwin.com [mailto:cygwin->owner@cygwin.com] On Behalf Of J. David Boyd
>Sent: Friday, March 27, 2015 9:29 AM
>To: cygwin@cygwin.com
>Subject: Rebase, Peflags, and cygserver
>
>
>I keep having problems with vforks. Sometime >everything is fine for days, then I start emacs, and get >vfork errors.
Me too.
When vfork finally got 'fixed' this morning somehow, I notice that when I run 'emacs -Q &' from an xterm window it now takes 4 minutes for emacs to come up. FWIW It is much faster if I have emacs start my normal way from .startxwinrc.
I also find that when I create a new frame and place it on the right border of my monitor, sometimes the width gets 'fixed'. This last time I ran 'emacs -Q &' created a new frame and selected a dired buffer. Put it next to the right side of my monitor and it cannot be shrunk in width less than 73 columns. I also see this error:
(emacs:3112): Gtk-CRITICAL **: gtk_distribute_natural_allocation: assertion 'extra_space >= 0' failed
--
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
next prev parent reply other threads:[~2015-03-27 15:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 15:17 J. David Boyd
2015-03-27 15:27 ` Marco Atzeri
2015-03-27 19:05 ` J. David Boyd
2015-03-27 20:28 ` Marco Atzeri
2015-03-27 15:45 ` Rockefeller, Harry [this message]
2015-03-27 15:48 ` Jim Reisert AD1C
2015-03-27 20:46 ` Achim Gratz
2015-03-28 0:52 ` Ken Brown
2015-03-30 18:07 ` Rockefeller, Harry
2015-03-30 20:35 ` Marco Atzeri
2015-04-06 5:03 ` Jim Reisert AD1C
2015-04-06 16:27 ` Ken Brown
2015-04-11 9:04 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0a1b83ad787f4b32b383c3c633b1c087@vsrv060ex03.ssd.fsi.com \
--to=harry.rockefeller@flightsafety.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).