From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Huszagh Subject: Re: babel latex headers and image generation commands Date: Tue, 04 Feb 2020 15:38:28 -0800 Message-ID: <87y2thylcb.fsf@gmail.com> References: <874kw6ztr9.fsf@gmail.com> <871rrayrsc.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:53881) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iz7m4-0006Ps-P8 for emacs-orgmode@gnu.org; Tue, 04 Feb 2020 18:38:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iz7m3-00035y-R0 for emacs-orgmode@gnu.org; Tue, 04 Feb 2020 18:38:32 -0500 Received: from mail-pg1-x52d.google.com ([2607:f8b0:4864:20::52d]:43710) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iz7m3-000337-LQ for emacs-orgmode@gnu.org; Tue, 04 Feb 2020 18:38:31 -0500 Received: by mail-pg1-x52d.google.com with SMTP id u131so10449931pgc.10 for ; Tue, 04 Feb 2020 15:38:31 -0800 (PST) Received: from ryzen3950 (c-98-210-127-71.hsd1.ca.comcast.net. [98.210.127.71]) by smtp.gmail.com with ESMTPSA id r9sm6833999pfl.136.2020.02.04.15.38.28 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Feb 2020 15:38:29 -0800 (PST) In-Reply-To: <871rrayrsc.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org Sender: "Emacs-orgmode" To: "emacs-orgmode@gnu.org" 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