From: Max Nikulin <manikulin@gmail.com> To: emacs-orgmode@gnu.org Subject: Re: [PATCH] New LaTeX code export option: engraved Date: Thu, 5 May 2022 23:48:29 +0700 [thread overview] Message-ID: <t50v4v$rje$1@ciao.gmane.io> (raw) In-Reply-To: <87v8ukyo94.fsf@gmail.com> On 05/05/2022 22:17, Timothy wrote: > Subject: [PATCH 1/4] ox-latex: Refactor `org-latex-src-block' When I was trying to fix an issue with caption, I was not brave enough for massive changes. I do not like the original code of the function. There are some unit tests for exporting of src blocks. Maybe the new option should be tested as well. > +(defun org-latex-src-block--verbatim > + (src-block info _lang caption caption-above-p _label > + _num-start _retain-labels _attributes float) On the one hand I have no a better suggestion, but on the other hand 10 arguments is too much for straightforward code from my point of view. Unsure that getting parameters in each function or passing a property list would not be worse however. It reminds me a case when a colleague failed in despair trying to figure out what was wrong with his 15 argument fortran function. I do not remember exactly whether it was a missed argument or an extra one. The last one was assumed to be a parameter (constant) and the identifier was not available in debugger since compiler just substituted the number without creation of a symbol and it added even more confusion. My other notes are rather loosely related to your patches. The issues may be postponed till someone will start a new thread for them. My hope is that some of them might be easily addressed so that they will not need separate testing. A problem with percent sign in captions is tracked on updates.orgmode.org. Some environments has not fixed yet: https://list.orgmode.org/YT2PR01MB45101E27DC6251D8F8B7B366F6EC9@YT2PR01MB4510.CANPRD01.PROD.OUTLOOK.COM/ That time I was puzzled why the option is named "multicolumn" while only regular "figure" is added: > + (cond ((string= "multicolumn" float) > + (format "\\begin{figure*}[%s]\n%s%s\n%s\\end{figure*}" If language is added to "#+begin_example:" than the block content is properly fontified in the Emacs buffer. It would be great to treat such example similar to source block during export. When some code is not supposed to be executed, it is natural to use example block. I am curious if new functions may be reused.
next prev parent reply other threads:[~2022-05-05 18:14 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-04 15:59 Timothy 2022-05-05 7:52 ` Daniel Fleischer 2022-05-05 16:09 ` Timothy 2022-05-06 2:35 ` Ihor Radchenko 2022-05-06 11:23 ` Timothy 2022-05-05 7:54 ` Daniel Fleischer 2022-05-05 8:48 ` Ihor Radchenko 2022-05-05 15:17 ` Timothy 2022-05-05 16:13 ` Timothy 2022-05-07 5:16 ` Ihor Radchenko 2022-05-07 6:57 ` Timothy 2022-05-07 10:40 ` Timothy 2022-05-07 11:33 ` Daniel Fleischer 2022-05-08 14:30 ` [PATCH] (v2) " Timothy 2022-05-09 6:20 ` Ihor Radchenko 2022-05-09 12:57 ` Timothy 2022-05-10 8:00 ` Max Nikulin 2022-05-11 11:06 ` Ihor Radchenko 2022-05-11 16:05 ` [PATCH] (v3) " Timothy 2022-05-12 16:40 ` Daniel Fleischer 2022-05-12 16:44 ` Timothy 2022-05-05 16:48 ` Max Nikulin [this message] 2022-05-07 4:13 ` [PATCH] " Ihor Radchenko 2022-05-09 19:19 ` Sébastien Miquel 2022-05-10 1:13 ` Timothy 2022-05-10 16:10 ` Timothy 2022-05-10 17:53 ` Sébastien Miquel
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='t50v4v$rje$1@ciao.gmane.io' \ --to=manikulin@gmail.com \ --cc=emacs-orgmode@gnu.org \ --subject='Re: [PATCH] New LaTeX code export option: engraved' \ /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).