emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Timothy <orgmode@tec.tecosaur.net>,  emacs-orgmode@gnu.org
Subject: Re: Attempting to create orgcard.org
Date: Wed, 28 Sep 2022 08:22:46 +0200	[thread overview]
Message-ID: <87pmfg587d.fsf@gnu.org> (raw)
In-Reply-To: <87pmfgmju0.fsf@kyleam.com> (Kyle Meyer's message of "Tue, 27 Sep 2022 20:19:35 -0400")

Kyle Meyer <kyle@kyleam.com> writes:

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

Fully agreed.  And I don't want to be in the same situation than for
the manual, where someone puts a lot of energy into something that we
accept as a temporary experiment, and which becomes something like a
burden for some Emacs maintainers.

Timothy, I believe your efforts are worthwhile as a way to provide
Emacs third-party package maintainers a way to produce a refcard-like
PDF document for their libraries.  But not for Org, where the refcard
is really good enough as it is, especially the Emacs sync constraints
we have right now.

Is that okay with you?


  parent reply	other threads:[~2022-09-28  6:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 14:36 Attempting to create orgcard.org Timothy
2022-09-27 20:45 ` Bastien
2022-09-28  0:19   ` Kyle Meyer
2022-09-28  1:22     ` Timothy
2022-09-28  6:22     ` Bastien [this message]
2022-09-28  7:10       ` Timothy

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=87pmfg587d.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=orgmode@tec.tecosaur.net \


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