public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Emacs-w32 28.1-2 (marked as test) fails with: "Doing vfork: Resource temporarily unavailable"
Date: Sun, 17 Jul 2022 10:35:11 -0600	[thread overview]
Message-ID: <8bbc40d4-a355-33c9-0065-5d8cfa5b7267@SystematicSw.ab.ca> (raw)
In-Reply-To: <2b58f263-cb3f-98a2-9a45-7ee5ccc76ef1@cornell.edu>

On 2022-07-17 08:15, Ken Brown wrote:
> On 7/17/2022 7:08 AM, Oleksandr Gavenko wrote:
>> I saw a new version of emacs-w32 28.1-2 (has 28.1-1) and gave it a try.
>> If has a problem with forking processes:
>> Doing vfork: Resource temporarily unavailable

> Please see the release announcement:
>    https://cygwin.com/pipermail/cygwin-announce/2022-April/010529.html

Could you not perhaps at emacs (initial) startup add the rebase userpath 
eln-cache entry, and create a shell script to rebase the eln-cache 
entries which could be e.g. ~/.emacs.d/cygwin-rebase-eln-cache or 
elsewhere, and perhaps that script could also initially add the rebase 
userpath eln-cache entry, to make life easier for users.

You could document the manual instructions and any commands or scripts 
provided in /usr/share/doc/cygwin/emacs.README for reference in every 
release notice, as well as in issues here, rather than documenting it in 
and referring to release notices.

I suggest this as GNU units comes with a python script 
(/usr/bin/units_cur) to update currency exchange rates (requiring 
internet availability to access a few free data sources) if you want to 
use units for such operations, and instructions for various automated 
modes of operation documented in /usr/share/doc/cygwin/units.README, the 
approach decided on after discussions on the apps list.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2022-07-17 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17 11:08 Oleksandr Gavenko
2022-07-17 14:15 ` Ken Brown
2022-07-17 16:35   ` Brian Inglis [this message]
2022-07-17 21:20     ` Ken Brown

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=8bbc40d4-a355-33c9-0065-5d8cfa5b7267@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).