unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mario Becroft <mb@becroft.co.nz>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: 19175@debbugs.gnu.org
Subject: bug#19175: 24.4; make-frame-on-display fails if emacs started with -nw
Date: Sun, 29 Mar 2015 21:52:03 +1300	[thread overview]
Message-ID: <87y4mg424s.fsf@ak2.becroft.co.nz> (raw)
In-Reply-To: <9800C187-E0D5-4431-865C-7CD57D019D6B@swipnet.se> (Jan D.'s message of "Sun, 29 Mar 2015 10:45:16 +0200")

"Jan D." <jan.h.d@swipnet.se> writes:

> Hi.
>
>> 29 mar 2015 kl. 05:42 skrev Mario Becroft <mb@becroft.co.nz>:
>> 
>> Perhaps it depends on the configuration, such as which toolkit is used
>> etc. I compile mine with X, but without external toolkits. In this case,
>> my configure command was as follows:
>> 
>> ./configure --without-toolkit-scroll-bars --with-x
>> --with-x-toolkit=lucid --without-xft
>
> No, it is a signal race.  Apparently XOpenDisplay does not retry when
> interrupted by a signal, SIGIO in this case.
> Blocking SIGIO at the appropriate locations fixes it.
>
> Is the fix too late for the 24-branch?

I wasn't implying knowledge about the cause of the problem, which I have
not investigated myself, only additional information in case it is
relevant. It would be fantastic to see a fix.

Then there are other X-related bugs I have reported, but if the
connection to the server can at least be made, this would be a step
forward.

-- 
Mario Becroft <mb@becroft.co.nz>       t: @MarioBecroft
p: +64-9-974-9244  m: +64-21-038-5178  w: http://www.becroft.co.nz/





  reply	other threads:[~2015-03-29  8:52 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-25  4:28 bug#19175: 24.4; make-frame-on-display fails if emacs started with -nw Mario Becroft
2014-11-25  4:34 ` bug#19175: Further information Mario Becroft
2015-03-23  6:12 ` bug#19175: 24.4; make-frame-on-display fails if emacs started with -nw Jan D.
2015-03-23  6:32   ` Mario Becroft
2015-03-23 17:34     ` Glenn Morris
2015-03-23 20:26       ` Mario Becroft
2015-03-24  1:44   ` Glenn Morris
2015-03-29  3:42     ` Mario Becroft
2015-03-29  8:45       ` Jan D.
2015-03-29  8:52         ` Mario Becroft [this message]
2015-03-29 15:01         ` Eli Zaretskii
2015-03-29 17:09           ` Jan Djärv
2015-03-29 17:20             ` Eli Zaretskii
2015-03-29 19:18               ` Jan D.
2015-03-29 21:17         ` Stefan Monnier
2015-03-30  6:32           ` Jan D.
2015-03-30 13:58             ` Stefan Monnier
2015-03-30 14:36               ` Eli Zaretskii
2015-03-30 20:51                 ` Stefan Monnier
2015-03-31  2:34                   ` Eli Zaretskii
2015-03-31 13:26                     ` Stefan Monnier
2015-03-31 14:03                       ` Eli Zaretskii
2015-03-31 21:07                         ` Stefan Monnier
2015-04-01  2:38                           ` Eli Zaretskii
2015-04-01  3:55                             ` Stefan Monnier
2015-03-30 14:47               ` Eli Zaretskii
2015-03-31 14:14                 ` Nicolas Petton
2015-03-31 21:08                   ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y4mg424s.fsf@ak2.becroft.co.nz \
    --to=mb@becroft.co.nz \
    --cc=19175@debbugs.gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).