From: Bastien <bzg@gnu.org>
To: Timothy <orgmode@tec.tecosaur.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: changing orgcard.tex
Date: Wed, 28 Sep 2022 08:16:28 +0200 [thread overview]
Message-ID: <87h70s9g77.fsf@gnu.org> (raw)
In-Reply-To: <87r0zyvijo.fsf@tec.tecosaur.net> (Timothy's message of "Mon, 26 Sep 2022 12:55:37 +0800")
Hi Timothy,
Timothy <orgmode@tec.tecosaur.net> writes:
>> If we are to make changes against orgcard.tex we should be careful to
>> stick to GNU conventions regarding creating refcards.
>
> Might you have a link to those conventions on hand?
I meant sticking to the .tex commands used for Emacs refcard and its
visual output.
--
Bastien
prev parent reply other threads:[~2022-09-28 6:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 15:30 Dynamic keybindings in the manual Timothy
2022-09-25 17:52 ` Juan Manuel Macías
2022-09-26 4:52 ` Bastien
2022-09-26 4:55 ` changing orgcard.tex (was: Dynamic keybindings in the manual) Timothy
2022-09-28 6:16 ` Bastien [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=87h70s9g77.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).