From: Max Nikulin <manikulin@gmail.com>
To: emacs@vergauwen.me, Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [PATCH]: ox-latex: omit empty date
Date: Mon, 1 Aug 2022 23:47:54 +0700 [thread overview]
Message-ID: <80b3058f-7397-6e56-97fa-82b398d11d43@gmail.com> (raw)
In-Reply-To: <N8O1xep--3-2@vergauwen.me>
On 01/08/2022 17:55, emacs--- via General discussions about Org-mode. wrote:
> *later in this mail)*
> ;; Date.
> (let ((date (and (plist-get info :with-date) (org-export-get-date
> info))))
> (if (string-match-p "^\{.*\}$" (org-export-data date info))
> (format "\\date%s\n" (org-export-data date info))
> (format "\\date{%s}\n" (org-export-data date info))))
I am against such code.
> _Why mostly:_
> At the moment the code escapes the provided brackets and the current
> behaviour is
> #+date: {my}{fancy}{date} -> \date\{my\}\{fancy\}\{date\}
#+date: @@latex:{my}{fancy}{date}@@
Anyway such date is not suitable for other backends.
I think, custom command name and "#+latex_header:" with such command is
proper solution.
It is possible to choose some combination of existing options like
#+options: date:t
#+date:
as instruction to not add the \date command, but I think it would be
confusing for users and anyway a breaking change for some of them.
I suppose, reverting the patch was the proper step.
next prev parent reply other threads:[~2022-08-01 17:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 12:49 [PATCH]: ox-latex: omit empty date emacs--- via General discussions about Org-mode.
2022-07-29 13:31 ` Ihor Radchenko
[not found] ` <87sfmkkptc.fsf@localhost-N898uXC--3-2>
2022-07-29 18:49 ` emacs--- via General discussions about Org-mode.
2022-07-30 5:49 ` Ihor Radchenko
2022-07-30 16:13 ` Max Nikulin
2022-07-31 0:53 ` Ihor Radchenko
2022-07-31 2:27 ` Max Nikulin
2022-07-31 2:38 ` Ihor Radchenko
2022-07-31 7:14 ` Max Nikulin
[not found] ` <eed45238-7cad-1752-9e98-688bd0ead08a@gmail.com-N8I60z3----2>
2022-08-01 10:09 ` emacs--- via General discussions about Org-mode.
2022-08-01 10:28 ` Daniel Fleischer
2022-08-01 10:55 ` emacs--- via General discussions about Org-mode.
2022-08-01 16:47 ` Max Nikulin [this message]
2022-07-31 15:25 ` Daniel Fleischer
2022-07-31 15:40 ` Daniel Fleischer
2022-08-01 1:07 ` Ihor Radchenko
2022-08-05 12:42 ` Ihor Radchenko
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=80b3058f-7397-6e56-97fa-82b398d11d43@gmail.com \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=emacs@vergauwen.me \
/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).