emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Timothy <orgmode@tec.tecosaur.net>
To: emacs-orgmode@gnu.org
Cc: Timothy <orgmode@tec.tecosaur.net>, emacs-orgmode@gnu.org
Subject: Re: changing orgcard.tex (was: Dynamic keybindings in the manual)
Date: Mon, 26 Sep 2022 12:55:37 +0800	[thread overview]
Message-ID: <87r0zyvijo.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <878rm6wxdq.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 531 bytes --]

Hi Bastien,

> If we are to make changes against orgcard.tex we should be careful to
> stick to GNU conventions regarding creating refcards.

Might you have a link to those conventions on hand?

> Also, maybe some improvements can be shared upstream against the Emacs
> refcard?

Possibly, while keybindings /rarely/ change, occasionally they do, and so I
personally consider it a significant improvement having them dynamically
determined. After I finish with this we could ask emacs-devel what they think.

All the best,

  reply	other threads:[~2022-09-26  4:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 15:30 Dynamic keybindings in the manual Timothy
2022-09-25 17:52 ` Juan Manuel Macías
2022-09-26  4:52 ` Bastien
2022-09-26  4:55   ` Timothy [this message]
2022-09-28  6:16     ` changing orgcard.tex Bastien

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:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87r0zyvijo.fsf@tec.tecosaur.net \
    --to=orgmode@tec.tecosaur.net \
    --cc=emacs-orgmode@gnu.org \


* 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


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).