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
>
Kyle Meyer 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
Hi Kyle,
> 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
>
Bastien writes:
> Timothy writes:
>
>> I’m trying to make a .org refcard.
>
> Is it intented to replace orgcard.tex at some point? I believe we
> should stick to using the same format for Org than for Emacs. If this
> is doable via an .org file that is easier to maintain, that's good.
Somethi
Hi Timothy,
Timothy writes:
> I’m trying to make a .org refcard.
Is it intented to replace orgcard.tex at some point? I believe we
should stick to using the same format for Org than for Emacs. If this
is doable via an .org file that is easier to maintain, that's good.
PS: FWIW, I don't thin
Hi All,
I’m trying to make a .org refcard. There are two benefits I see, first we can
evaluate
`(org-release)' during export and so move `(org-release)' out of the makefile,
secondly this enables us to have keybindings that are always up to date. Users
who have customised the keybindings (or fram
