all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: "Fraga, Eric" <e.fraga@ucl.ac.uk>, Bastien <bzg@gnu.org>,
	 "Cc: emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Re: [ANN] Looking for new maintainers for ox-latex.el (LaTeX export library)
Date: Fri, 3 Feb 2023 07:23:21 +0100	[thread overview]
Message-ID: <CAO48Bk92vbs+G3=OE7+f5hOK=3kV--n0x791QFbr12tN8TppSQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 891 bytes --]

Hi,

> I am happy to help with both ox-latex and ox-beamer with two caveats: my
> time at certain times of the year is very limited (as you know as there
> is still an outstanding item for ox-beamer that I have not been able to
> address since October or longer) and my elisp-fu is sometimes not up to
> scratch.  However, I do have useful LaTeX & beamer expertise which can
> be useful.

I'm certainly time-limited, but use ox-latex and ox-beamer profusely and in
parallel with "pure" LaTEX - whatever you might understand by "pure" ;-)
will be close enough - I could also help when my lectures permit and yes, I
also follow the list

/PA
-- 
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler

Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet

[-- Attachment #2: Type: text/html, Size: 1288 bytes --]

             reply	other threads:[~2023-02-03  6:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03  6:23 Pedro Andres Aranda Gutierrez [this message]
2023-02-03 12:21 ` Re: [ANN] Looking for new maintainers for ox-latex.el (LaTeX export library) Ihor Radchenko

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAO48Bk92vbs+G3=OE7+f5hOK=3kV--n0x791QFbr12tN8TppSQ@mail.gmail.com' \
    --to=paaguti@gmail.com \
    --cc=bzg@gnu.org \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.