unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: 15247@debbugs.gnu.org, yamaoka@jpl.org
Subject: bug#15247: 24.3.50; Emacs Cygwin crashes when replying to a mail
Date: Mon, 02 Sep 2013 14:29:51 +0200	[thread overview]
Message-ID: <522484BF.9040206@gmx.at> (raw)
In-Reply-To: <b4mk3izlewy.fsf@jpl.org>

 > I realized that this is caused by `make-frame-invisible' that runs
 > when there is only one Emacs frame.  At least for Cygwin, you should
 > be able to reproduce it in this way:
 >
 > emacs -Q --eval '(make-frame-invisible (selected-frame) t)'
 >
 > I also guess that it was harmless until about a week ago.

Should be harmless again with revision 114106.

 > Why such an odd thing was run is because I was using this advice
 > to make `raise-frame' work on Cygwin.
 >
 > (defadvice raise-frame (before make-it-work (&optional frame) activate)
 >   "Make it work on Cygwin."
 >   (make-frame-invisible frame t))
 >
 > As I wrote in <http://thread.gmane.org/gmane.emacs.devel/150533>,
 > `raise-frame' doesn't raise iconified, invisible, or hidden frame.
 > Now I changed it into:
 >
 > (defadvice raise-frame (before make-it-work (&optional frame) activate)
 >   "Make it work on Cygwin."
 >   (or (eq frame (selected-frame))
 >       (make-frame-invisible frame)))

I don't understand fully: Above you say that "`raise-frame' doesn't
raise iconified, invisible, or hidden frame" and in the before-advice
or `raise-frame' you make the frame invisible?	

 > Even if Emacs should not crash for any Lisp code,

It should not, indeed.

 > it's a trivial
 > one among many(?) issues concerning Cygwin.  So, I'm closing this
 > bug.  Sorry for the noise.

martin





  reply	other threads:[~2013-09-02 12:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-02  6:02 bug#15247: 24.3.50; Emacs Cygwin crashes when replying to a mail Katsumi Yamaoka
2013-09-02 10:02 ` Katsumi Yamaoka
2013-09-02 12:29   ` martin rudalics [this message]
2013-09-02 23:27     ` Katsumi Yamaoka

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=522484BF.9040206@gmx.at \
    --to=rudalics@gmx.at \
    --cc=15247@debbugs.gnu.org \
    --cc=yamaoka@jpl.org \
    /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).