Answers inline,
On Fri, 18 Jul 2025 at 01:48, David Masterson <dsmaster...@icloud.com> wrote:
>
> Pedro Andres Aranda Gutierrez <paag...@gmail.com> writes:
>
> > my experience (and possibly .2 cents)
> >
> > 1. LaTeX2Org
> >
> > I needed to go that path for a couple of manuals when I started lecturing
> > and it was generally feasible with AWK/Python. I got my .org file, fixed
> > it and could continue on the Org path.
>
> Do you have a reference for that?
More than a reference, what I have is a lot of previous coding. I
started with Emacs on a Sun workstation where we captured the
schematics for some circuit boards and had to develop a script to get
the connections list and print it out in format that could be used by
the
people who were wire-wrapping the prototype boards for testing.
> > 2. #+LATEX:
> >
> > Mainly for TiKZ figures (and animations): I keep them in separate files I
> >
> > #+latex: \include{...}
>
> In this case, is there a difference between that and:
>
> #+INCLUDE ...
I'm issuing a LATEX command to include LaTeX code.
> > 3. #+LATEX_HEADER:
> >
> > I've collected all my variations on RequirePackage{fancyvrb} for my listings
> > for documents and slides in one file, which I have in my Templates directory
> > to copy to the different documentation projects.
> >
> > As a plus, I also have a dir-locals.el to use with the feature and fix the
> > appearance of my slides/lecture notes.
> >
> > With the time, collecting and reusing has made the round-trip time +/-
> > equivalent to exporting to latex, fixing there and coming back.
> > That path, however, has been extemely usefull when implementing stuff
> > on the feature branch.
>
> That looks interesting, but I still have much to learn about LaTeX...
That's what I have been doing for the last 30 years ;-) ad I'm still learning.
> --
> David Masterson
Best, /PA
--
Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Sagen's Paradeiser, write BE!
Year 1 of the New Koprocracy
