From: Matt Huszagh <email@example.com> To: "firstname.lastname@example.org" <email@example.com> Subject: Re: babel latex headers and image generation commands Date: Tue, 04 Feb 2020 15:38:28 -0800 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> I've thought about this more and the solution I presented above isn't quite sufficient for me. I need something where I get complete control over what goes in the latex source block on a block-by-block basis. In other words, I don't want a user-configurable option like org-format-latex-header plus a list of user-configurable packages in every block. I could add an option alongside the option I introduced above that tells the execute function to only compose the tex file from the body (btw, this doesn't have to be manual for the user, just define a class and use snippets), but at some point I wonder how much it makes sense to keep adding options to this function since it'll just make it harder to maintain. What do people think? If there's any interest, I'm more than happy to put in the extra time and add this functionality to latex-execute. Otherwise, I'll just advise the function for my own specific needs. I do think there's a real use-case here: namely, complete case-by-case control over the source latex and its output, including export backend dependent things like colors. But, maybe this is just me and the existing functionality is fine with people. Matt
next prev parent reply other threads:[~2020-02-04 23:38 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-04 7:39 Matt Huszagh 2020-02-04 21:19 ` Matt Huszagh 2020-02-04 23:38 ` Matt Huszagh [this message] 2020-02-10 7:21 ` Bastien [not found] ` <firstname.lastname@example.org> 2020-08-29 7:02 ` Matt Huszagh 2020-09-02 17:32 ` [PATCH] " Matt Huszagh 2020-09-02 18:53 ` Matt Huszagh 2020-09-06 6:18 ` Bastien 2020-09-09 19:43 ` Matt Huszagh 2020-10-24 12:30 ` Bastien 2020-10-24 16:39 ` Matt Huszagh 2020-12-14 8:19 ` Bastien 2020-09-06 5:59 ` Bastien
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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: babel latex headers and image generation commands' \ /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).