unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: function keys in macro
Date: Mon, 25 Nov 2013 21:34:41 +0100	[thread overview]
Message-ID: <87r4a4kyo5.fsf@nl106-137-194.student.uu.se> (raw)
In-Reply-To: mailman.7060.1385383126.10748.help-gnu-emacs@gnu.org

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Have you bound M-f2 to any command?

Well, I use Emacs in a Linux VT (tty1 to be precise)
and M-F2 (or Alt-F2) will switch to tty2. In
/etc/console-setup/remap.inc, with

# J - Emacs to the left...
alt keycode 36       = Decr_Console
ctrll alt keycode 36 = Decr_Console
# L - ... Linux VTs with tmux to the right
alt keycode 38       = Incr_Console
ctrll alt keycode 38 = Incr_Console

I have bound those functions to Alt-J and Alt-K
instead, but I haven't unset those old "short"cuts
because I'd never use them for anything else.

That's why, in Emacs (in tty1), I can't hit M-F2 and
have Emacs process it, because the tty1 will intercept
it and jump to tty2.

But, I just tried Emacs in X and no: M-F2 is unbound.

So, for everything to fall into place like the blocks
of Tetris, if I put those keys in a macro, could I jump
between the ttys programmatically with Elisp?

I have tried the following shell/X tools to accomplish
the same task:

* chvt (doesn't work from Emacs, tmux, or X, but from
  an "empty" Linux VT, it works to everywhere including
  X)
* xdotool (works from everywhere, but you cannot get
  from the "VT world" to X)
* xmacroplay (works just like xdotool, which makes sense)

So the best solution I found so far, which is 99%
satisfactory, is remap from the VT world, and xdotool
from X.

In fact, I just got a new idea writing this, remap to
some unused shortcut (or even Unicode char, if those
could be put in macros), and then have a macro "type"
that... stay tuned!

-- 
Emanuel Berg, programmer-for-rent. CV, projects, etc at uXu
underground experts united:  http://user.it.uu.se/~embe8573


  parent reply	other threads:[~2013-11-25 20:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23 15:10 function keys in macro Emanuel Berg
2013-11-25 12:38 ` Michael Heerdegen
2013-11-25 12:44 ` Jambunathan K
2013-11-25 12:50 ` Jambunathan K
     [not found] ` <mailman.7060.1385383126.10748.help-gnu-emacs@gnu.org>
2013-11-25 20:34   ` Emanuel Berg [this message]
2013-11-25 21:40     ` Emanuel Berg
2013-11-26  7:35       ` Michael Heerdegen
2014-01-14  1:47     ` Emanuel Berg
     [not found] ` <mailman.7064.1385384049.10748.help-gnu-emacs@gnu.org>
2013-11-25 20:40   ` Emanuel Berg
2013-11-25 20:42     ` Emanuel Berg
2013-11-27 12:38       ` Tassilo Horn
     [not found]       ` <mailman.7252.1385555936.10748.help-gnu-emacs@gnu.org>
2013-11-27 20:10         ` Emanuel Berg
2013-11-28 10:06           ` Jambunathan K
     [not found]           ` <mailman.7323.1385633250.10748.help-gnu-emacs@gnu.org>
2013-11-28 15:25             ` Emanuel Berg

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=87r4a4kyo5.fsf@nl106-137-194.student.uu.se \
    --to=embe8573@student.uu.se \
    --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).