From: pinmacs <pinmacs@cas.cat>
To: emacs-orgmode@gnu.org
Subject: Re: ox-latex default template changed sentence spacing from 9.6 to 9.7 ?
Date: Wed, 4 Sep 2024 15:08:46 +0200 [thread overview]
Message-ID: <59b3443c-70d9-4adc-a59f-66fbca0b9e6b@cas.cat> (raw)
In-Reply-To: <CAO48Bk9rg8HQDaj=sp+GwaZi03T0pAN_M42PM_aYDwHQWe6JfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
Hi Pedro,
You were right!
In my success of starting to have more diverse number of latex exports
in my yearly journal, it was being polluted because the global
~#+LATEX_HEADER~ stuff [1]
it went unnoticed because it was in lowcase and I was only searching for
the uppercase, these were the affecting lines:
#+latex_header: \usepackage{setspace}
#+latex_header: \onehalfspacing
Cheers,
pinmacs
[1] see here for more details:
https://list.orgmode.org/orgmode/224ef5a7-33fc-4467-b146-0899aa61b223@cas.cat/T/#t
On 2024-09-04 07:43, Pedro Andres Aranda Gutierrez wrote:
> Hi,
>
> I have a Linux with a recent emacs 30.0.90, org-mode 9.7.10 and a
> freeBsd with an emacs 29.4, org-mode 9.6.15 and I see neither emitting
> the linespread command.
>
> Tested with #LATEX_COMPILER: lualatex and without it.
>
> It must be something you have in your headers...
> Best, /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: 2576 bytes --]
next prev parent reply other threads:[~2024-09-04 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 5:43 ox-latex default template changed sentence spacing from 9.6 to 9.7 ? Pedro Andres Aranda Gutierrez
2024-09-04 13:08 ` pinmacs [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-02 22:26 pinmacs
2024-10-12 12:26 ` 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
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=59b3443c-70d9-4adc-a59f-66fbca0b9e6b@cas.cat \
--to=pinmacs@cas.cat \
--cc=emacs-orgmode@gnu.org \
/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).