Tim Cross writes:
> Scott Randby writes:
>
>> On 6/2/21 8:07 AM, Bruce D'Arcus wrote:
>>> On Wed, Jun 2, 2021 at 4:28 AM Tim Cross wrote:
>>>
The more I think about it, I think the best solution would be to update
the code which sets the default and have it check for latexmk. If it
> Stefan Nobis writes:
> Colin Baxter writes:
>> I really don't understand why the changed is needed.
> The upcoming citation support needs a reliable way to run the
> required bibliography processor (e.g. biber or bibtex). Therefore
> the current default setting that
Greg Minshall writes:
> Bruce,
>
>> > I really don't understand why the changed is needed.
>>
>> I've stated it twice, I believe, but it's now a longer thread, so:
>>
>> Org is set to get native citation support.
>>
>> Once that's merged, people who use this feature will be disappointed
>>
"Dr. Arne Babenhauserheide" writes:
> [[PGP Signed Part:Undecided]]
>
> Scott Randby writes:
>
>> On 6/2/21 8:07 AM, Bruce D'Arcus wrote:
>>> On Wed, Jun 2, 2021 at 4:28 AM Tim Cross wrote:
>>>
The more I think about it, I think the best solution would be to update
the code which
Scott Randby writes:
> On 6/2/21 8:07 AM, Bruce D'Arcus wrote:
>> On Wed, Jun 2, 2021 at 4:28 AM Tim Cross wrote:
>>
>>> The more I think about it, I think the best solution would be to update
>>> the code which sets the default and have it check for latexmk. If it is
>>> found, set it as
Colin Baxter writes:
>> Bruce D'Arcus writes:
>
> > On Wed, Jun 2, 2021 at 4:28 AM Tim Cross wrote:
> >> The more I think about it, I think the best solution would be to
> >> update the code which sets the default and have it check for
> >> latexmk. If it is found, set it
Bruce,
> > I really don't understand why the changed is needed.
>
> I've stated it twice, I believe, but it's now a longer thread, so:
>
> Org is set to get native citation support.
>
> Once that's merged, people who use this feature will be disappointed
> to know that when using the natbib or
On 6/2/21 12:07 PM, Stefan Nobis wrote> I have
--8<---cut here---start->8---
(setq org-latex-pdf-process '("latexmk -f -pdf -%latex -outdir=%o %f"))
--8<---cut here---end--->8---
I could not get that setting to work. The
Colin Baxter writes:
> I really don't understand why the changed is needed.
The upcoming citation support needs a reliable way to run the required
bibliography processor (e.g. biber or bibtex). Therefore the current
default setting that only runs latex three times does not suffice.
On the
On Wed, Jun 2, 2021 at 12:30 PM Colin Baxter wrote:
>
>
> I'm beginning to think this change of the default should not
> happen. From this thread it seems to be that the chances of it breaking
> existing work flow is high.
I don't see how that follows. Can you clarify?
> I really don't
> On Wed, 02 Jun 2021 17:29:49 +0100, Colin Baxter said:
Colin> I'm beginning to think this change of the default should not
Colin> happen. From this thread it seems to be that the chances of it
breaking
Colin> existing work flow is high.
Colin> I really don't understand
I'm beginning to think this change of the default should not
happen. From this thread it seems to be that the chances of it breaking
existing work flow is high.
I really don't understand why the changed is needed.
Best wishes,
Scott Randby writes:
> On 6/2/21 8:07 AM, Bruce D'Arcus wrote:
>> On Wed, Jun 2, 2021 at 4:28 AM Tim Cross wrote:
>>
>>> The more I think about it, I think the best solution would be to update
>>> the code which sets the default and have it check for latexmk. If it is
>>> found, set it as the
Scott Randby writes:
> (1) Which one of the above suggestions should I use? I don't want
> interactions when I'm exporting. I don't want to have to mess with a
> configuration file either.
> (2) How many shell commands will org-latex-pdf-process need? Right
> now there are three. Replace those
On 6/2/21 8:07 AM, Bruce D'Arcus wrote:
On Wed, Jun 2, 2021 at 4:28 AM Tim Cross wrote:
The more I think about it, I think the best solution would be to update
the code which sets the default and have it check for latexmk. If it is
found, set it as the default and if it is not found, set the
On 6/2/21 1:33 AM, Stefan Nobis wrote:
"Bruce D'Arcus" writes:
Here's the current command for the "latexmk" option:
"latexmk -g -pdf -pdflatex=\"%latex\" -outdir=%o %f"
... and here's what you have, minus shell-escape.
"latexmk -f -pdf -%latex -interaction=nonstopmode
> Bruce D'Arcus writes:
> On Wed, Jun 2, 2021 at 4:28 AM Tim Cross wrote:
>> The more I think about it, I think the best solution would be to
>> update the code which sets the default and have it check for
>> latexmk. If it is found, set it as the default and if it is not
On Wed, Jun 2, 2021 at 4:28 AM Tim Cross wrote:
> The more I think about it, I think the best solution would be to update
> the code which sets the default and have it check for latexmk. If it is
> found, set it as the default and if it is not found, set the existing
> default. This would have
Stefan Nobis writes:
> An alternative may be to use latexmk only if citations are found (new
> feature, new dependencies). Or a wrapper that checks whether latexmk
> is available and works (e.g. trying to call "latexmk --version") and
> falls back to the old routine of manually running the engine
Stefan Nobis writes:
> Tim Cross writes:
>
>> One reason is that latexmk is not installed on some systems.
>
> Just after starting to write that this is false nowadays I realized
> you are right. :)
>
> See: https://mg.readthedocs.io/latexmk.html
>
> For macOS latexmk is distributed with the
Nick Dokos writes:
> "Bruce D'Arcus" writes:
>
>> While testing org-cite a few weeks ago, I noticed by default bibtex
>> won't run with natbib export, or biblatex with biblatex export.
>>
>> Since org has not had native citations, this is not surprising.
>>
>> But with org-cite coming soon,
Tim Cross writes:
> One reason is that latexmk is not installed on some systems.
Just after starting to write that this is false nowadays I realized
you are right. :)
See: https://mg.readthedocs.io/latexmk.html
For macOS latexmk is distributed with the default TeX installation
MacTeX for
"Bruce D'Arcus" writes:
> Here's the current command for the "latexmk" option:
> "latexmk -g -pdf -pdflatex=\"%latex\" -outdir=%o %f"
> ... and here's what you have, minus shell-escape.
> "latexmk -f -pdf -%latex -interaction=nonstopmode -output-directory=%o %f"
The option
Hello,
** Tim Cross [2021-06-02 12:56:59 +1000]:
> "Bruce D'Arcus" writes:
>> On Tue, Jun 1, 2021 at 9:09 PM Scott Randby wrote:
>>
>>> As a constant user of Org's LaTeX export capability, this change would break
>>> my ability to export to PDF, and it would be difficult for me to fix. I
>>>
"Bruce D'Arcus" writes:
> On Tue, Jun 1, 2021 at 9:09 PM Scott Randby wrote:
>
>> As a constant user of Org's LaTeX export capability, this change would break
>> my ability to export to PDF, and it would be difficult for me to fix. I don't
>> support this change.
>
> Can you explain this,
On Tue, Jun 1, 2021 at 9:09 PM Scott Randby wrote:
> As a constant user of Org's LaTeX export capability, this change would break
> my ability to export to PDF, and it would be difficult for me to fix. I don't
> support this change.
Can you explain this, Scott? Why would anything "break'?
"Bruce D'Arcus" writes:
> While testing org-cite a few weeks ago, I noticed by default bibtex
> won't run with natbib export, or biblatex with biblatex export.
>
> Since org has not had native citations, this is not surprising.
>
> But with org-cite coming soon, this will change.
>
> At the time
On 6/1/21 8:00 PM, Tim Cross wrote:
"Bruce D'Arcus" writes:
While testing org-cite a few weeks ago, I noticed by default bibtex
won't run with natbib export, or biblatex with biblatex export.
Since org has not had native citations, this is not surprising.
But with org-cite coming soon,
"Bruce D'Arcus" writes:
> While testing org-cite a few weeks ago, I noticed by default bibtex
> won't run with natbib export, or biblatex with biblatex export.
>
> Since org has not had native citations, this is not surprising.
>
> But with org-cite coming soon, this will change.
>
> At the
On Tue, Jun 1, 2021 at 1:03 PM Timothy wrote:
>
>
> Bruce D'Arcus writes:
>
> > Thanks Timothy.
> >
> > What's your view on modifying current default?
>
> I think latexmk is a pretty reasonable expectation, and your
> justification that it's more important seems sound to me.
>
> Using the value
Bruce D'Arcus writes:
> Thanks Timothy.
>
> What's your view on modifying current default?
I think latexmk is a pretty reasonable expectation, and your
justification that it's more important seems sound to me.
Using the value seen in my config, I've found that at the least my
version of
Thanks Timothy.
What's your view on modifying current default?
On Tue, Jun 1, 2021, 12:36 PM Timothy wrote:
>
> Hi Bruce,
>
> In case it's of interest, I've been quite happy with this:
> https://tecosaur.github.io/emacs-config/config.html#compiling
>
> Bruce D'Arcus writes:
>
> > While
Hi Bruce,
In case it's of interest, I've been quite happy with this:
https://tecosaur.github.io/emacs-config/config.html#compiling
Bruce D'Arcus writes:
> While testing org-cite a few weeks ago, I noticed by default bibtex
> won't run with natbib export, or biblatex with biblatex export.
>
>
Hi Bruce,
Bruce D'Arcus writes:
> So what do LaTeX users think about changing the default for
> "org-latex-pdf-process" to "latexmk"?
It sounds like a good idea to me. In fact I have `org-latex-pdf-process'
set to latexmk in my ~ /.emacs (with the option to always compile with
LuaTeX).
Best
While testing org-cite a few weeks ago, I noticed by default bibtex
won't run with natbib export, or biblatex with biblatex export.
Since org has not had native citations, this is not surprising.
But with org-cite coming soon, this will change.
At the time I suggested changing default to use
35 matches
Mail list logo
