unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: Doc of keyboard macros
Date: Mon, 24 Sep 2018 22:35:40 +0300	[thread overview]
Message-ID: <83k1naadtf.fsf@gnu.org> (raw)
In-Reply-To: <8736ty4s4o.fsf@mail.linkov.net> (message from Juri Linkov on Mon, 24 Sep 2018 22:23:03 +0300)

> From: Juri Linkov <juri@linkov.net>
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,  emacs-devel@gnu.org
> Date: Mon, 24 Sep 2018 22:23:03 +0300
> 
> There is a current tendency towards deprecating F1-F10 function keys
> by hardware manufacturers.  These keys are already hard to press by default
> on PC: a special additional key <Fn> needs to be pressed in combination of
> <Fn>-<F3>, and a Chromebook has no row of function keys at all: in order
> to get <F4>, you have to press <Search>-4.

Those are still faster than "C-x (", since they are a single key
combination, whereas "C-x (" is 2 key combinations.



  reply	other threads:[~2018-09-24 19:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24 14:47 Doc of keyboard macros Stefan Monnier
2018-09-24 15:21 ` Eli Zaretskii
2018-09-24 15:51   ` Eli Zaretskii
2018-09-24 16:36     ` Stefan Monnier
2018-09-24 16:50       ` Andreas Schwab
2018-09-24 17:07       ` Eli Zaretskii
2018-09-24 19:00         ` Stefan Monnier
2018-09-24 19:23         ` Juri Linkov
2018-09-24 19:35           ` Eli Zaretskii [this message]
2018-09-24 20:03             ` Alan Mackenzie
2018-09-24 20:17             ` Joost Kremers
2018-10-10 20:25               ` Mathias Dahl
2018-10-14  8:28                 ` Marcin Borkowski
2018-10-14 14:33                   ` Yuri Khan
2018-10-15 20:22                     ` Juri Linkov
2018-10-16  1:05                       ` Van L
2018-09-24 20:06           ` Drew Adams
2018-09-24 20:22         ` Filipp Gunbin

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=83k1naadtf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=monnier@iro.umontreal.ca \
    /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).