From: Andrey Lisin <andrey.lisin@gmail.com>
To: Javier <nospam@nospam.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: How get escape sequence generated by keyboard shortcut in Emacs?
Date: Sun, 01 Mar 2015 00:05:37 +0600 [thread overview]
Message-ID: <m2d24toqry.fsf@gmail.com> (raw)
In-Reply-To: <mcsv7v$nai$1@speranza.aioe.org> (Javier's message of "Sat, 28 Feb 2015 17:51:59 +0000 (UTC)")
Nice! Thanks for help everyone!
next prev parent reply other threads:[~2015-02-28 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1011.1425137633.31049.help-gnu-emacs@gnu.org>
2015-02-28 17:25 ` How get escape sequence generated by keyboard shortcut in Emacs? Dan Espen
2015-02-28 17:45 ` Robert Thorpe
2015-02-28 17:51 ` Javier
2015-02-28 18:05 ` Andrey Lisin [this message]
2015-02-28 15:33 Andrey Lisin
[not found] ` <87ioemuirj.fsf@gmail.com>
[not found] ` <EC3D20A4-BC2D-4616-B59F-41CDB641FC2A@gmail.com>
2015-02-28 16:28 ` Tory S. Anderson
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=m2d24toqry.fsf@gmail.com \
--to=andrey.lisin@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=nospam@nospam.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).