From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Emacs + run.exe problem.
Date: Mon, 31 Jul 2017 12:37:00 -0000 [thread overview]
Message-ID: <2d78b1fb-4255-d240-41f8-6ae16a1e2228@cornell.edu> (raw)
In-Reply-To: <vriuy3r53c1j.fsf@gavenkoa.example.com>
On 7/30/2017 4:27 PM, Oleksandr Gavenko wrote:
> On 2017-07-30, Oleksandr Gavenko wrote:
>>
>> This time two new:
>
> I tried with 32-bit version.
>
> As 64-bit version better avoid rebase problems I tried it.
>
>> * "run emacs-w32" is broken. Some GUI windows splashed on screen and quickly
>> hid.
>>
> Stil broken.
Works for me.
> But in addition socket binding for Emacs server stopped to work:
>
> (server-start)
Also works for me.
Have you looked into BLODA?
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
next prev parent reply other threads:[~2017-07-30 20:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 3:40 Oleksandr Gavenko
2017-07-31 11:58 ` Oleksandr Gavenko
2017-07-31 12:37 ` Ken Brown [this message]
2017-07-31 13:20 ` Oleksandr Gavenko
2017-07-31 22:09 ` 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=2d78b1fb-4255-d240-41f8-6ae16a1e2228@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).