From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Antero Mejr <mail@antr.me>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Latex exporter should consider export settings [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.3/lisp/org/)]
Date: Wed, 29 Jan 2025 07:04:55 +0100 [thread overview]
Message-ID: <E7D0ED89-2AD2-494C-B4FC-938A697BAA5A@gmail.com> (raw)
In-Reply-To: <87plk6rbjo.fsf@antr.me>
Hi,
Thanks a lot. I would like a couple of days to look at the creator part specifically and adding this in to ox-Beamer. Or maybe even factoring out.
FTMB, let’s wait for Ihor’s reaction to this and discuss the pdfcreator part.
The semantics behind is different. I happens to be the program that created the PDF.
Could you please expand on why you want to block that too?
Best, /PA
Enviado desde mi iPad
> El 28 ene 2025, a las 20:20, Antero Mejr <mail@antr.me> escribió:
>
> Pedro Andres Aranda Gutierrez <paaguti@gmail.com> writes:
>
>> attached is a fix for the reported BUG, including a couple of test cases
>
> That seems to work, thanks. I attached a patch that handles
> org-export-with-creator too.
>
> It would be good if these fixes were also ported over to org-beamer,
> since the same problem happens there.
>
> <0001-lisp-ox-latex.el-Obey-with-creator-when-exporting.patch>
next prev parent reply other threads:[~2025-01-29 6:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-28 7:31 [BUG] Latex exporter should consider export settings [9.6.15 (release_9.6.15 @ /usr/share/emacs/29.3/lisp/org/)] Pedro Andres Aranda Gutierrez
2025-01-28 8:02 ` Pedro Andres Aranda Gutierrez
2025-01-28 12:59 ` Pedro Andres Aranda Gutierrez
2025-01-28 19:19 ` Antero Mejr
2025-01-29 6:04 ` Pedro Andres Aranda Gutierrez [this message]
2025-01-29 21:06 ` Antero Mejr
2025-01-30 5:43 ` Pedro Andres Aranda Gutierrez
2025-01-30 6:56 ` Pedro Andres Aranda Gutierrez
2025-01-30 8:31 ` Pedro Andres Aranda Gutierrez
-- strict thread matches above, loose matches on Subject: below --
2025-01-28 1:38 Antero Mejr
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=E7D0ED89-2AD2-494C-B4FC-938A697BAA5A@gmail.com \
--to=paaguti@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mail@antr.me \
/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 public 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).