public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Rebase, Peflags, and cygserver
Date: Sat, 28 Mar 2015 00:52:00 -0000	[thread overview]
Message-ID: <5515C3D2.7030304@cornell.edu> (raw)
In-Reply-To: <87619mw5gd.fsf@Rainer.invalid>

On 3/27/2015 4:28 PM, Achim Gratz wrote:
> J. David Boyd writes:
>> What I'm doing (with some success)is this:
>>
>> 1. get latest cygwin update
>> 2. del /etc/rebase*
>> 3. rebaseall -v
>> 4. peflagsall -v
>> 5. don't restart cygserver (This means my bash shell window starts a little
>> slower, but I can live with that.)
>
>  From the announcement of _autorebase:
>
> To perform a full rebase, execute "rebase-trigger fullrebase".  Then
> shut down Cygwin and simply run setup.exe.  The rebase will be
> performed even when the installation did not get modified in any way.
> Any subsequent runs of setup.exe will again rebase in incremental
> mode.
>
>> I usually have to do this 2 to 3 times before I can get emacs to start without
>> vfork errors.
>
> Do you use Cygwin Emacs or something else?
>
>> Also, I often run Cygwin Setup (to get something I've missed, like wget..., or
>> check for updates) while emacs is running.  Should I shut it down first?
>
> Depends, but anything that could interfere with the rebase is a
> potential problem.

I've run into the OP's problem occasionally, where a full rebase doesn't 
fix all rebase/fork problems.  What's worked for me on those occasions 
is to reboot the computer and then run a full rebase.  I once saw an 
explanation of why rebooting makes a difference, but I don't remember 
what it was.

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

  reply	other threads:[~2015-03-27 20:55 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
2015-03-27 15:48 ` Jim Reisert AD1C
2015-03-27 20:46 ` Achim Gratz
2015-03-28  0:52   ` Ken Brown [this message]
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=5515C3D2.7030304@cornell.edu \
    --to=kbrown@cornell.edu \
    --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).