all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: emacs-devel@gnu.org, Timothy <orgmode@tec.tecosaur.net>
Subject: refcard sources in Org
Date: Wed, 14 Dec 2022 12:36:33 +0000	[thread overview]
Message-ID: <871qp2uppq.fsf@localhost> (raw)

Hi,

In Org ML, we recently had a suggestion to switch orgcard.tex source
from tex to Org. https://orgmode.org/list/87mtakvq0d.fsf@tec.tecosaur.net

The main argument in favour of this approach is that we can automate key
binding calculation using Org macros, making it less painful to maintain
the card in case if the default bindings change in future.

However, the current Emacs card generation is tailored to tex.
Kyle pointed out that:

> Something to consider: orgcard.tex is included in the Emacs repo and
>   fits into their refcard machinery.  If the source changes from .tex to
>   .org, the .org file must be included in the Emacs repo, as is done with
>   the .org of the manual now (bug#45143, bug#46837).  Doing so would
>   involve extra setup and handling on the Emacs side.  Even if someone on
>   the Org side volunteers to do that work, another case of special
>   handling probably wouldn't be received warmly.

However, Kyle's statement is anyway just what he thinks. So, I am just
going ahead and asking what Emacs devs think about this idea. Would it
increase maintenance load on you?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



             reply	other threads:[~2022-12-14 12:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 12:36 Ihor Radchenko [this message]
2022-12-14 13:15 ` refcard sources in Org Eli Zaretskii
2022-12-14 13:42   ` Ihor Radchenko

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

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

  git send-email \
    --in-reply-to=871qp2uppq.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-devel@gnu.org \
    --cc=orgmode@tec.tecosaur.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.