unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "André A. Gomes" <andremegafone@gmail.com>
Cc: theophilusx@gmail.com, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, john@yates-sheets.org
Subject: Re: Keybinding styles
Date: Wed, 08 Sep 2021 23:09:44 -0400	[thread overview]
Message-ID: <E1mOARc-0006Z6-Gu@fencepost.gnu.org> (raw)
In-Reply-To: <87wnnr2rgn.fsf@gmail.com> (message from André A. Gomes on Wed, 08 Sep 2021 15:15:52 +0300)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > If you wanted to do a research project, you could try developing a
  > > system for writing manuals which handled variation in key bindings.
  > > You might come up with an advance in technology.
  > >
  > > If you want to work on that research, I wish you luck, but that is
  > > outside the scope of the GNU Project.

  > Why is it outside the scope of the GNU Project?

We have an Emacs Manual that documents Emacs.
That's what we want.  Producing manuals for greatly modified
version of Emacs is not our goal.  If some people want to work on it,
they are welcome to, but I won't urge people to choose that project.

  > 1. Convert the Emacs manual from texi to org.

  > 2. Leverage `where-is' and the macro replacement facilities of org---(info
  > "(org) Macro Replacement").

  > 3. Export the org manual to texi.

Supporting this as part of Emacs is a non-goal, but
if this gives you results you like, you are welcome to do it.

Eli wrote:

  > That'd produce a manual that caters to a single, but different set of
  > key bindings, which was not the intent.  The intent is to produce a
  > manual that caters to any set, in the same manual.  That'd mean
  > changing the text dynamically when it is displayed by the Info reader,
  > whereas you propose a static change.

I think that is a much more challenging goal than the other one.  I
expect it will be difficult to reconcile this with formatting the
manual trough TeX.

Supporting this as part of Emacs is a non-goal, but if you present
a clean and unproblematical implementation, we would not reject it
a priori.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)





  parent reply	other threads:[~2021-09-09  3:09 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-03 18:00 [External] : Re: Gitlab Migration Drew Adams
2021-09-03 20:06 ` Stefan Kangas
2021-09-03 22:49 ` Stefan Monnier
2021-09-04  2:00   ` Tim Cross
2021-09-04 13:26     ` Keybinding styles (was: [External] : Re: Gitlab Migration) Stefan Monnier
2021-09-04 13:39       ` Dmitry Gutov
2021-09-04 14:25         ` Keybinding styles Stefan Monnier
2021-09-04 15:44       ` Keybinding styles (was: [External] : Re: Gitlab Migration) Yuan Fu
2021-09-04 15:50         ` Eli Zaretskii
2021-09-04 15:55           ` Drew Adams
2021-09-04 16:07           ` Yuan Fu
2021-09-04 16:19             ` Eli Zaretskii
2021-09-06  3:07             ` Richard Stallman
2021-09-06 11:28               ` Dmitry Gutov
2021-09-04 19:55           ` Keybinding styles Daniel Fleischer
2021-09-04 20:52             ` Stefan Kangas
2021-09-05  7:17               ` tomas
2021-09-04 16:09         ` Bird
2021-09-04 20:48         ` Keybinding styles (was: [External] : Re: Gitlab Migration) Tim Cross
2021-09-05 19:03       ` John Yates
2021-09-06  4:34         ` Eli Zaretskii
2021-09-07  3:16         ` Richard Stallman
2021-09-07 12:02           ` John Yates
2021-09-08  3:29             ` Richard Stallman
2021-09-08 12:15               ` Keybinding styles André A. Gomes
2021-09-08 13:18                 ` Eli Zaretskii
2021-09-08 20:37                 ` John Yates
2021-09-09  5:39                   ` Eli Zaretskii
2021-09-15 13:40                     ` André A. Gomes
2021-09-15 14:26                       ` Stefan Kangas
2021-09-15 15:36                       ` Eli Zaretskii
2021-09-15 20:15                       ` Richard Stallman
2021-09-15 21:29                         ` Alexandre Garreau
2021-09-16  5:20                           ` Eli Zaretskii
2021-09-16  5:00                         ` Eli Zaretskii
2021-09-09  3:09                 ` Richard Stallman [this message]
2021-09-04 16:05     ` [External] : Re: Gitlab Migration Stefan Kangas
2021-09-04  2:20   ` Drew Adams
2021-09-04 13:14     ` Stefan Monnier
2021-09-04 14:58       ` Drew Adams
2021-09-04 16:10         ` Stefan Monnier
2021-09-04 16:40           ` Drew Adams
2021-09-05 19:27   ` John Yates
2021-09-07  3:16     ` Richard Stallman
2021-09-07 15:31       ` Barry Fishman
2021-09-09  3:07         ` Richard Stallman
2021-09-09 14:07           ` André A. Gomes

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=E1mOARc-0006Z6-Gu@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=andremegafone@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=john@yates-sheets.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=theophilusx@gmail.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.
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).