From: "Dauer, Michael" <michael.dauer@smartpm.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: built-in macros not working anymore [9.3.6 (9.3.6-23-g01ee25-elpaplus @ c:/Users/mda/.emacs.d/elpa/org-plus-contrib-20200309/)]
Date: Tue, 19 May 2020 16:23:24 +0200 [thread overview]
Message-ID: <CAA3mUeYS1VMEtAKH0=TC+aow_hzoXr9fryT8Ukww4DXOG3L6Ow@mail.gmail.com> (raw)
In-Reply-To: <87blmkggl6.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 904 bytes --]
mist.org>>>
* test
foo {{{author}}} bar {{{keyword(AUTHOR)}}}
{{{title}}}
{{{date}}}
{{{time}}}
{{{input-file}}}
{{{n}}}
<<<
ascii output buffer>>>
Michael Dauer
Table of Contents
_________________
1. test
1 test
======
foo bar
mist.org
1
<<<
Am Di., 19. Mai 2020 um 16:11 Uhr schrieb Nicolas Goaziou <
mail@nicolasgoaziou.fr>:
> Hello,
>
> "Dauer, Michael" <michael.dauer@smartpm.com> writes:
>
> > Yes, the behavior changed. Now the author macro expands to blank despite
> > the variable user-full-name is set.
> > Note I use #OPTIONS: author:nil, which is necessary to prevent that the
> export
> > is concluded by an author line.
> >
> > The expected behavior is to expand to the value of user-full-name.
>
> You lost me. Would you mind writing an ECM demonstrating the currently
> observed defect in {{{author}}} macro from master branch?
>
> Regards,
>
> --
> Nicolas Goaziou
>
[-- Attachment #2: Type: text/html, Size: 1582 bytes --]
next prev parent reply other threads:[~2020-05-19 14:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 9:57 Bug: built-in macros not working anymore [9.3.6 (9.3.6-23-g01ee25-elpaplus @ c:/Users/mda/.emacs.d/elpa/org-plus-contrib-20200309/)] Dauer, Michael
2020-03-11 13:00 ` Eric S Fraga
2020-03-11 15:23 ` Nicolas Goaziou
2020-05-18 15:18 ` Dauer, Michael
2020-05-18 16:01 ` Nicolas Goaziou
2020-05-19 9:44 ` Dauer, Michael
2020-05-19 14:11 ` Nicolas Goaziou
2020-05-19 14:23 ` Dauer, Michael [this message]
2020-05-19 22:53 ` Nicolas Goaziou
2020-05-20 8:30 ` Dauer, Michael
2020-05-20 19:51 ` Nicolas Goaziou
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='CAA3mUeYS1VMEtAKH0=TC+aow_hzoXr9fryT8Ukww4DXOG3L6Ow@mail.gmail.com' \
--to=michael.dauer@smartpm.com \
--cc=emacs-orgmode@gnu.org \
/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).