From: XeCycle <XeCycle@Gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: capture gtk kill (gnome alt-f4) (delete-event?)
Date: Sat, 26 May 2012 15:36:30 +0800 [thread overview]
Message-ID: <87aa0vpf5t.fsf@xc.laptop> (raw)
In-Reply-To: BLU0-SMTP138343D28B383E324A33747CC060@phx.gbl
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
Yagnesh Raghava Yakkala <yagnesh@live.com> writes:
[...]
> I thought it is possible since Emacs is asking for confirmation(with
> unsaved buffer exist) when I click [X] button with mouse on a Emacs frame.
>
> They are the same signals., aren't they?
If Emacs acts differently on them, they must be different.
--
Carl Lei (XeCycle)
Department of Physics, Shanghai Jiao Tong University
OpenPGP public key: 7795E591
Fingerprint: 1FB6 7F1F D45D F681 C845 27F7 8D71 8EC4 7795 E591
[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]
prev parent reply other threads:[~2012-05-26 7:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-26 5:19 capture gtk kill (gnome alt-f4) (delete-event?) Yagnesh Raghava Yakkala
2012-05-26 5:26 ` XeCycle
2012-05-26 6:28 ` Yagnesh Raghava Yakkala
2012-05-26 7:36 ` XeCycle [this message]
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=87aa0vpf5t.fsf@xc.laptop \
--to=xecycle@gmail.com \
--cc=help-gnu-emacs@gnu.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.
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).