public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: multiwindow X11 and Emacs
Date: Wed, 12 Sep 2012 14:46:00 -0000	[thread overview]
Message-ID: <50509B05.1000005@cornell.edu> (raw)
In-Reply-To: <loom.20120912T153808-270@post.gmane.org>

On 9/12/2012 9:50 AM, Achim Gratz wrote:
> Ken Brown <kbrown <at> cornell.edu> writes:
>
>> I can't reproduce this on my system.  I'm running 64-bit Windows 7,
>> emacs-24.2-1, the latest Cygwin snapshot (2012-08-27), and the test
>> version of the X server (1.13.0-1).  Here's what I tried:
>
> Same setup as mine except 32-bit Win7/Enterprise.
>
>> 1. Start mintty from the "Cygwin Terminal" shortcut.
>>
>> 2. $ startxwin
>>
>> 3. [still in the mintty window] $ DISPLAY=:0 emacs -Q&
>
> I've tested this both with bash and tcsh, BTW since tcsh's signal handling is
> apparently different from bash.
>
>> 4. In the resulting emacs window, C-z.
>>
>> 5. Left click on the emacs icon to de-iconify emacs.
>>
>> The cursor blinks and emacs responds to keyboard input.
>
> This is what doesn't work here.  That is when I start the X server from another
> mintty than the one that the X server is started from or when the shell is tcsh.
>   So if I extend your case with:
>
> 6. Start another mintty
>
> 7. DISPLAY=:0 emacs -Q&
>
> 8. In the resulting emacs window, C-z.
>
> 9. Left click on the emacs icon to de-iconify emacs.
>
> The cursor doesn't blink and emacs doesn't respond to keyboard input.
>
> What do you get?

Still no problem.  I'm using only bash, not tcsh.  But I gather that 
you're having problems with both.

I wonder why your results are so different from mine.  Do you have 
something in your .startxwinrc that could be interfering?  I moved my 
.startxwinrc out of the way before testing.

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:[~2012-09-12 14:24 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 [this message]
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
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=50509B05.1000005@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).