emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Daniel Fleischer <danflscr@gmail.com>
To: emacs--- via "General discussions about Org-mode."
	<emacs-orgmode@gnu.org>
Cc: Max Nikulin <manikulin@gmail.com>,  emacs@vergauwen.me
Subject: Re: [PATCH]: ox-latex: omit empty date
Date: Mon, 01 Aug 2022 13:28:23 +0300	[thread overview]
Message-ID: <m2o7x41cmw.fsf@gmail.com> (raw)
In-Reply-To: <N8NsXYQ--3-2@vergauwen.me> (emacs's message of "Mon, 1 Aug 2022 12:09:53 +0200 (CEST)")

emacs--- via "General discussions about Org-mode."
<emacs-orgmode@gnu.org> writes:

> My use case is very niche and be solved by changing my custom latex date 
> command by renaming it as for example \mydate.
>
> Adding extra options like with_date:nil seems overkill for this small issue. 

I agree; I think we shouldn't change basic behavior for more advanced
usages unless it's something many people are interested in and we keep a
backward compatibility.

> A second option would be is to analyze the data format in the org file.
> If for example the date is specified as 
> #+date: {day}{something}

The thing is \date is a macro with one parameter, a string. That's way
\date{} doesn't do anything and \date{\today} prints today's date where
\today return today's date as a string. Starting to introduce new kinds
of inputs - e.g. {y}{m}{d} - to the \date macro would just confuse
people, I think.

Daniel


  reply	other threads:[~2022-08-01 10:29 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 [this message]
2022-08-01 10:55               ` emacs--- via General discussions about Org-mode.
2022-08-01 16:47                 ` Max Nikulin
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=m2o7x41cmw.fsf@gmail.com \
    --to=danflscr@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=emacs@vergauwen.me \
    --cc=manikulin@gmail.com \
    /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).