emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Timothy <orgmode@tec.tecosaur.net>
To: emacs-orgmode@gnu.org
Cc: Kyle Meyer <kyle@kyleam.com>, Timothy <orgmode@tec.tecosaur.net>,
Subject: Re: Attempting to create orgcard.org
Date: Wed, 28 Sep 2022 15:10:25 +0800	[thread overview]
Message-ID: <878rm42cir.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <87pmfg587d.fsf@gnu.org>

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

Hi Bastien,

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

Sure, though the idea here is that this would provide a way we could move
`(org-release)' out of the makefile and fully into elisp.

I’ve done a little test, and defining `org-release' like so in `org-macs.el' seems
to work quite nicely.

│ (defalias 'org-release
│   (eval-when-compile
│     (require 'lisp-mnt)
│     (eval
│      `(function
│        (lambda ()
│          "The release version of Org"
│          ,(lm-version "org.el"))))))

As I understand it, `orgcard.tex' is currently the main blocker on us moving
`org-release' out of the makefile like so?

Removing the need to manually ensure that keybindings are up to date and
accurate is a nice bonus.

All the best,

      reply	other threads:[~2022-09-28  8:52 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
2022-09-28  7:10       ` Timothy [this message]

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


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