From: Wynfield Henman <wynfield@gmail.com>
To: cygwin@cygwin.com
Subject: Re: multiwindow X11 and Emacs
Date: Sat, 15 Sep 2012 06:09:00 -0000 [thread overview]
Message-ID: <CAM-A7MBgVneqLUWjCKAYNKKKcTcnsJkreChHQNdighsY7CnvAw@mail.gmail.com> (raw)
In-Reply-To: <505311EE.7080008@cornell.edu>
Sorry about that. I was more making the point that it's not a cygwin
port of emac's fault.
I also have this problem using emacs built locally from the original
gnu emacs source code. And also from the cygwin port.
C-z puts emacs off the screen, but when its re-displayed the focus
doesn't come back into the editting buffer. I have to first click on
any ol option on the top menu, and it re-activiates something that
enable editting back in the buffer.
environment: putty (also built from original source code)
This problem / hanging does not occur when emacs has been moved off
the screen by clicking on the [-] tab in the upper right side of the
emacs frame.
Can you duplicate this on your system?
C-Z # then [SHIFT][TAB] back to emacs to get it back up on the
screen. It should be frozen then. Workaround, click on [File] or
something and then escape from it and you can work in the normal
buffer.
On Fri, Sep 14, 2012 at 4:15 AM, Ken Brown <kbrown@cornell.edu> wrote:
> On 9/14/2012 1:56 AM, Wynfield Henman wrote:
>>
>> emacs hangs for me when invoking it from putty which has been
>> initiated by cygwin X11 which I start with startx.
>> But, I usually always have emacs up all the time and its not a big
>> pain. I would be nice for it not to freeze when being re-activated.
>
>
> I'm sorry, but you didn't give enough details for me to know whether you're
> reporting the same problem that Achim reported. If not, please start a new
> thread. In either case, please give a precise recipe for producing the
> problem. Do you have to use a non-Cygwin program (putty) in order to
> produce the problem?
>
> 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
>
--
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:[~2012-09-14 22:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 10:52 Achim Gratz
2012-09-12 13:50 ` Ken Brown
2012-09-12 14:24 ` Achim Gratz
2012-09-12 14:46 ` Ken Brown
2012-09-12 15:09 ` Achim Gratz
2012-09-14 11:03 ` Wynfield Henman
2012-09-14 13:15 ` Ken Brown
2012-09-15 6:09 ` Wynfield Henman [this message]
2012-09-15 11:57 ` Ken Brown
2012-09-15 14:58 ` 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=CAM-A7MBgVneqLUWjCKAYNKKKcTcnsJkreChHQNdighsY7CnvAw@mail.gmail.com \
--to=wynfield@gmail.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).