From: "Doherty, Daniel" <ded@ddoherty.net>
To: Rasmus <rasmus@gmx.us>, Org-mode List <emacs-orgmode@gnu.org>
Subject: Re: Title/Author missing in Markdown export?
Date: Mon, 16 May 2016 16:12:03 -0500 [thread overview]
Message-ID: <CAJ5HwTyXHMOW-o8UBv+2V+XdpHYyMNx6iHMVo=H=bxFfQFQEyg@mail.gmail.com> (raw)
In-Reply-To: <87a8k2awyf.fsf@saiph.selenimh>
[-- Attachment #1: Type: text/plain, Size: 2244 bytes --]
Thanks for pointing out that my manual was out of date. Looks to me like I
needed to delete the stock org manual before the package-based one would
show up in info.
====================================================
Daniel E. Doherty
Law Offices of Daniel E. Doherty
7300 W. 110th Street, Suite 930
Overland Park, KS 66210
913.338.7182 (Phone)
913.338.7164 (FAX)
ded-law@ddoherty.net
On Sat, May 7, 2016 at 7:12 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
wrote:
> Hello,
>
> "Daniel E. Doherty" <ded@ddoherty.net> writes:
>
> > On Tue, 28 Apr 2015 09:08:45 -0500,
> > Rasmus <rasmus@gmx.us> wrote:
> >>
> >> Andreas Hilboll <lists@hilboll.de> writes:
> >>
> >> > Using the current git master, any exported Markdown doesn't include
> >> > title, author, and date information. Is this desired behaviour, or is
> >> > it a bug?
> >>
> >> AFAIK it's a "feature".
> >>
> >> --
> >> ⠠⠵
> >>
> >>
> > Rasmus,
> >
> > Not sure whether you were being ironic on this,
>
> Rasmus is correct. Vanilla Mardown doesn't provide any way to specify
> a title or an author in a document.
>
> Of course, if there's some standard way to do this, we can extend
> "ox-md.el" accordingly. The same goes for table of contents, generated
> as HTML for the time being.
>
> > but I've noticed that exports in LaTeX, odt, and HTML, not longer seem
> > to pick up the buffer name as the title as formerly and as the manual
> > claims.
> >
> > `TITLE'
> > The title to be shown (otherwise derived from buffer's name). You
> > can use several such keywords for long titles.
> >
> > Same is true of author:
> >
> > `AUTHOR'
> > The document author (`user-full-name').
> >
> > I rather liked having this be the default with the option to change it.
> So,
> > is this the intended behavior, or is the manual wrong?
>
> You are looking at an outdated manual. This change was introduced
> 2 years ago (commit 604b93892caa8a646ced1ac7089461614bb9bffa). You may
> want to search ML archives for the discussion about it.
>
> You can probably use something like
>
> #+TITLE: {{{input-file}}}
>
> to get the old behaviour back.
>
> Regards,
>
> --
> Nicolas Goaziou
>
>
[-- Attachment #2: Type: text/html, Size: 3847 bytes --]
prev parent reply other threads:[~2016-05-16 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 14:05 Title/Author missing in Markdown export? Andreas Hilboll
2015-04-28 14:08 ` Rasmus
2016-05-07 9:55 ` Daniel E. Doherty
2016-05-07 12:12 ` Nicolas Goaziou
2016-05-16 21:12 ` Doherty, Daniel [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='CAJ5HwTyXHMOW-o8UBv+2V+XdpHYyMNx6iHMVo=H=bxFfQFQEyg@mail.gmail.com' \
--to=ded@ddoherty.net \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).