emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Ruijie Yu <ruijie@netyu.xyz>
Cc: Gustavo Barros <gusbrs.2016@gmail.com>,
	emacs-orgmode@gnu.org, Bastien Guerry <bzg@gnu.org>
Subject: Re: [BUG] org-latex-packages-alist type specification [9.6.3 (release_9.6.3-2-gf2949d @ /usr/local/share/emacs/29.0.90/lisp/org/)]
Date: Thu, 20 Apr 2023 08:53:53 +0000	[thread overview]
Message-ID: <87fs8vx7by.fsf@localhost> (raw)
In-Reply-To: <A0F0BE34-70CB-4AF1-8917-518D6E380DC5@netyu.xyz>

Ruijie Yu <ruijie@netyu.xyz> writes:

>> Compiler list may also be nil.
>
> This should be covered by the repeat case?  Unless you want to be explicit about this, in which case you can wrap it in a choice, whose first choice being (const :tag “description” nil), and the second choice being the repeat case. 

Yes, explicit tag will be better.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  parent reply	other threads:[~2023-04-20  8:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 19:40 [BUG] org-latex-packages-alist type specification [9.6.3 (release_9.6.3-2-gf2949d @ /usr/local/share/emacs/29.0.90/lisp/org/)] Gustavo Barros
2023-04-13  5:12 ` Ruijie Yu via General discussions about Org-mode.
2023-04-13 11:26   ` Ihor Radchenko
2023-04-13 11:30     ` Ruijie Yu via General discussions about Org-mode.
2023-04-19  9:48       ` Bastien Guerry
2023-04-22 13:29         ` Ihor Radchenko
2023-04-20  8:53       ` Ihor Radchenko [this message]
2023-04-20  9:28         ` Ruijie Yu via General discussions about Org-mode.
2023-04-22 13:30           ` Ihor Radchenko
2023-04-22 13:35             ` Gustavo Barros

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=87fs8vx7by.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=gusbrs.2016@gmail.com \
    --cc=ruijie@netyu.xyz \
    /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).