emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jay Kamat <jaygkamat@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Add TITLE export to ox-md
Date: Thu, 24 Aug 2017 11:30:29 +0200	[thread overview]
Message-ID: <87a82p1fey.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87fuchzllk.fsf@gmail.com> (Jay Kamat's message of "Wed, 23 Aug 2017 23:32:55 -0400")

Hello,

Jay Kamat <jaygkamat@gmail.com> writes:

> The markdown editor should support TITLE

I'm not so sure about it. Vanilla Markdown does not support title.
Neither does "ox-md.el"

Is there any consensus about how title are handled in _vanilla_ syntax?

> -(defun org-md-template (contents _info)
> +(defun org-md-template (contents info)
>    "Return complete document string after Markdown conversion.
>  CONTENTS is the transcoded contents string.  INFO is a plist used
>  as a communication channel."
> -  contents)
> +  (concat
> +    ;; Generate title and subtitle, if possible
> +    (let ((title (and (plist-get info :with-title)
> +		   (plist-get info :title)))
> +	   (subtitle (plist-get info :subtitle))
> +	   (style (plist-get info :md-headline-style)))
> +      (when title
> +	(concat
> +	  (org-md--headline-title style
> +	    1 (org-export-data title info))
> +	  (when subtitle
> +	    (org-md--headline-title style
> +	      2 (org-export-data subtitle info))))))
> +    contents))

But then you would need to shift all headlines 1 or 2 levels down.
`setext' style becomes unusable because there is no room left for other
headlines.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2017-08-24  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24  3:32 [PATCH] Add TITLE export to ox-md Jay Kamat
2017-08-24  9:30 ` Nicolas Goaziou [this message]
2017-08-24 10:28   ` Kaushal Modi
2017-08-24 14:41     ` Jay Kamat
2017-08-26  8:11       ` Nicolas Goaziou
2017-08-28  2:43         ` Jay Kamat

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=87a82p1fey.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=jaygkamat@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).