From: Timothy <tecosaur@gmail.com> To: Nicolas Goaziou <mail@nicolasgoaziou.fr> Cc: org-mode-email <emacs-orgmode@gnu.org> Subject: Re: [PATCH] Wrap LaTeX snippets in $$ with markdown export Date: Tue, 04 May 2021 02:03:00 +0800 [thread overview] Message-ID: <87h7jjitkb.fsf@gmail.com> (raw) In-Reply-To: <87lf8v7q2z.fsf@nicolasgoaziou.fr> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes: > This sounds reasonable. I'm glad to hear that! >> +(defun org-md-latex-environment [...] > Nitpick: I would use `format', also the final newline character is > useless, since it will be removed later during the export process. Actually, since writing this patch I'm not sure that $$-surrounding \begin{}...\end{} environments is also a good idea. I'm inclined to leave this out of the patch. >> +;;;; Latex Fragment >> + >> +(defun org-md-latex-fragment (latex-fragment contents info) >> + "Transcode a LATEX-FRAGMENT object from Org to Markdown. >> +CONTENTS is nil. INFO is a plist holding contextual information." >> + (when (plist-get info :with-latex) >> + (let ((frag (org-html-latex-fragment contents info))) >> + (cond >> + ((string-match-p "^\\\\(" frag) >> + (concat "$" (substring frag 2 -2) "$")) >> + ((string-match-p "^\\\\\\[" frag) >> + (concat "$$" (substring frag 2 -2) "$$")) >> + (t (message "unrecognised fragment: %s" frag) >> + frag))))) > > Nitpick: I suggest to use `rx' macro. It really makes the code base > a better place. I do rather like the `rx' macro, however I'm not sure that (rx bol "\\(") is really an improvement over "^\\\\(" in this particular case. > You are missing some cases. The fragment could be $...$ or $$...$$ > already, so you can return it as-is without sending the message. Ah yep, after getting your thoughts on this message I'll send a revised patch with fixes this (along with any other changes). > Otherwise, it is a macro. We can assume it lives outside math mode. So > maybe the "Unrecognized fragment: %S" is in order in that situation. We > could also let HTML export back-end deal with it. I don't know what is > better. I'm not sure what to do here either. Perhaps nothing/HTML backend? Finally, I think if this case (lone macro) is handled, there aren't any possible "Unrecognized fragment"s that could be passed, and so that condition would no longer be necessary? -- Timothy.
next prev parent reply other threads:[~2021-05-03 18:07 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 16:41 Timothy 2021-03-31 20:59 ` Berry, Charles via General discussions about Org-mode. 2021-05-02 20:20 ` Timothy 2021-05-02 20:23 ` Timothy 2021-05-03 16:13 ` Nicolas Goaziou 2021-05-03 18:03 ` Timothy [this message] 2021-05-03 22:54 ` Nicolas Goaziou 2021-05-04 3:35 ` Timothy 2021-05-04 13:03 ` Nicolas Goaziou 2021-05-04 13:31 ` Timothy 2021-05-06 21:56 ` Nicolas Goaziou 2021-05-09 20:12 ` Timothy 2021-05-10 20:54 ` 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=87h7jjitkb.fsf@gmail.com \ --to=tecosaur@gmail.com \ --cc=emacs-orgmode@gnu.org \ --cc=mail@nicolasgoaziou.fr \ --subject='Re: [PATCH] Wrap LaTeX snippets in $$ with markdown export' \ /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
Code repositories for project(s) associated with this 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).