From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-devel@gnu.org, orgmode@tec.tecosaur.net
Subject: Re: refcard sources in Org
Date: Wed, 14 Dec 2022 15:15:22 +0200 [thread overview]
Message-ID: <83y1ram8id.fsf@gnu.org> (raw)
In-Reply-To: <871qp2uppq.fsf@localhost> (message from Ihor Radchenko on Wed, 14 Dec 2022 12:36:33 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Date: Wed, 14 Dec 2022 12:36:33 +0000
>
> > 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?
It would mean etc/refcards/Makefile will have to be augmented to
produce the TeX version, which probably means it will have to be a
separate target dependent on the Emacs binary that has to be built
before that.
It also means Someone(TM) will have to know enough Org to maintain the
refcard over the years.
next prev parent reply other threads:[~2022-12-14 13:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 12:36 refcard sources in Org Ihor Radchenko
2022-12-14 13:15 ` Eli Zaretskii [this message]
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=83y1ram8id.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=orgmode@tec.tecosaur.net \
--cc=yantar92@posteo.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.