David Masterson writes:
>> Do you have specific section of the manual in mind?
>
> I thought about it and, I think, a simple statement at the end of 13.10
> (Latex Export) provides a start to help a newbie. Something like:
>
>
>
> If you have the LaTeX system installed, the 'kpsewhich' Linu
Ihor Radchenko writes:
> I'd prefer to put some more generic reference. Some info manual or
> good stable URL link that has explanations about kpsewhich and other
> LaTeX basics.
What about
http://mirrors.ctan.org/info/latex-doc-ptr/latex-doc-ptr.pdf
No direct references to kpsewhich, but I
Ihor Radchenko writes:
> I generally feel that it should be reasonable to go ahead with this
> breaking change, possibly disabling variable resolution for ox-org only.
Done, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=f409cb4e5
--
Ihor Radchenko // yantar92,
Org mo
Stefan Nobis writes:
> Ihor Radchenko writes:
>
>> I'd prefer to put some more generic reference. Some info manual or
>> good stable URL link that has explanations about kpsewhich and other
>> LaTeX basics.
>
> What about
>
>http://mirrors.ctan.org/info/latex-doc-ptr/latex-doc-ptr.pdf
Looks
Ihor Radchenko writes:
> Bastien Guerry writes:
>
>>> are there reasons not to punt the orphanage issue to this emacs
>>> orphanage (and, point to it from the org wiki)? on the one hand, "less
>>> control". on the other, "less work" (even "globally", if things scale).
>>
>> Indeed, perhaps htt
On 29 Jul 2023, Ihor Radchenko wrote:
Jonathan Gregory writes:
The basic-mode term is not very helpful. Perhaps
[inline/cropped/embedded]-mode would have been more descriptive
in terms of what it does.
Sounds reasonable. I like "inline-mode", although no strong
opinion.
I like it too.
Jonathan Gregory writes:
>> For example, python2/3 or MathJax4,4- were breaking and some
>> people were relying on legacy code. So, we had to provide some
>> extra versions checks and toggles on Org side as well.
>
> We're talking about different things here. Lilypond needs the
> \version to u
Hi All,
When setting Org to track TODO state changes, calling `org-todo' on an
active region comprising multiple headings, the state changes only
logged for the last heading.
To reproduce with `emacs -Q', visit the file:
#+begin_src org
,#+todo: TODO(t) | DONE(d!)
,* TODO Task 1
,* TODO Task 2
Gustavo Barros writes:
> When setting Org to track TODO state changes, calling `org-todo' on an
> active region comprising multiple headings, the state changes only
> logged for the last heading.
Confirmed.
The logging works using `post-command-hook', which is only called once.
--
Ihor Radche
On 31 Jul 2023, Ihor Radchenko wrote:
May it be possible to mix multiple \version commands? So that we
declare \version for \paper and user can declare other \version
for the code block body.
Probably not. Wouldn't that confuse the compiler? In any case, the
\version number is relative to
Hello
Ihor Radchenko writes:
>
> > Mehmet Tekman writes:
> > Question: What is the order of submission of patches?
> >
> >Do I submit a testing patch first which works strictly with
> >vanilla Org first, and then a new merge-params function, and
> >then yet another testing patch that
On 30/07/2023 16:16, Ihor Radchenko wrote:
The problem with dependencies is only there for local builds and that's
probably the motivation of the `condition-case' I proposed to change in
my patch.
Worg is a set of independent documents, so fail on first error in CI is
reasonable mostly only if
Mehmet Tekman writes:
> I've adapted this to write a git patch which currently passes with
> upstream/main, and contains a few `should-not` statements which are
> planned to be `should` statements after the merge function has been
> patched for the `:tangle' multi-parameter property.
I do not li
Max Nikulin writes:
> On 30/07/2023 16:16, Ihor Radchenko wrote:
>> The problem with dependencies is only there for local builds and that's
>> probably the motivation of the `condition-case' I proposed to change in
>> my patch.
>
> Worg is a set of independent documents, so fail on first error in
Hi! I wrote a package that provides interactive day view for orgmode
tasks. With this package you can visually understand your day schedule
and quickly reschedule your tasks and events. Essentially, this is what
modern calendars provide, although my package currently only provides
day view.
The
Ihor Radchenko writes:
> Is there any specific reason why you want to merge these tests now and
> not later, when you submit the full patch?
Convenience on my part, and closure of the many many patch branches
that I have open.
But I think you're right, and tomorrow evening I will just bite the
Ihor Radchenko writes:
> Stefan Nobis writes:
>
>> Ihor Radchenko writes:
>>
>>> I'd prefer to put some more generic reference. Some info manual or
>>> good stable URL link that has explanations about kpsewhich and other
>>> LaTeX basics.
>>
>> What about
>>
>>http://mirrors.ctan.org/info/l
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>>> Unlike `org-latex-preview', here we need to (1) respect active region;
>>> (2) keep the backward compatibility for INCLUDE-LINKED.
>>>
>>> For (1), for example, it would make sense to respect region when prefix
>>> argument is C-u an
18 matches
Mail list logo
