HI,
Attached is a small patch to allow explicitly adding style= in the biblatex
export options, to increase consistency with
Customisation variables.
Best, /PA
0001-Allow-style-in-cite_export.patch
Description: Binary data
* What I'm experiencing:
A custom ~org-num-format-function~ causes ~org-latex-preview~ warn when it
is called.
* Exact "Warning" I'm getting.
⛔ Warning (org-element-cache): org-element--cache: Org parser error in
ask.org::648. Resetting.
The error was: (error "Invalid search bound (wrong side of
Philip Kaludercic writes:
> Sławomir Grochowski writes:
>
>> Thank you Philip for the explanation and preparing the code snippet.
>>
>> So what are the next steps?
>> Can you merge your patch?
>
> If this is everything, I can push the change. But I'll test it first.
I have pushed the changes
Edgar Lux writes:
> I got this in an Org file:
>
> #+begin_src org
> [[file:Figures/Ti19-g(w, eta={0.1,}, R=1e-3).svg]]
> [[file:Figures/Ti19-g(w, eta={0.1,}, R=1e-3).png]]
> #+end_src
>
> The files exist, and can be viewed in image-mode (tested with src_bash{emacs
> -q}).
> With =C-c C-o= src_e
Anush V writes:
>> Thanks for reporting!
>> I tried to follow your steps, but I am unable to reproduce the problem.
>> May you please attach the exact problematic Org file, so that we can
>> make sure that we do the same thing?
>
> Thanks for the prompt response.
>
> Please find the attached file
Amy Grinn writes:
>>> +(while (< (point) (point-max))
>>> + (unless (looking-at " *\"\\([^\"]+\\)\" *")
>>> +(looking-at " *\\([^ ]+\\)"))
>>
>> May you please explain the rationale behind this regexp? AFAIU, it
>> implies that you want to allow whitespace characters
Garid Zorigoo writes:
> * To Reproduce
>
> 1. Change the org-num-format-function as written above
> 2. (In org-file) Turn-on ~org-num-mode~
> 3. (In org-file) On any equation, change it.
> 4. run ~org-latex-preview~ to preview the equation image.
> 5, run ~org-latex-preview~ go back to text mode.
Protesilaos Stavrou writes:
> With regard to the disambiguation scheme, I am playing around with
> various scenaria to see how Org HTML export behaves. Using the
> following:
> ...
> This is test 2 role="doc-backlink">1
> ...
> This is test 3 role="doc-backlink">1
>
> Notice that the 10
Alexander Adolf writes:
>> In fact, CLOCKSUM property does not support custom summaries.
>
> ???
AFAIU, you cannot do %CLOCKSUM{max}.
>>> Is there any way to change the summation behaviour for either or both
>>> column types?
>>
>> It is currently hard-coded. (Although, it is not too hard add s
Pedro Andres Aranda Gutierrez writes:
> HI,
> Attached is a small patch to allow explicitly adding style= in the biblatex
> export options, to increase consistency with
> Customisation variables.
Thanks!
> (style-options
> (cond
>((null style) nil)
> +
Morgan Smith writes:
> See two attached patches. All tests pass on my computer.
>
> Every once in a while I feel obligated to go back to org-clock-sum to
> try and optimize it. I have a file with 8 clocktables in it and it
> takes forever to update. This time I decided instead of trying to
> o
> I did the following:
>
> 1. Save your file to /tmp/
> 2. rm -rf /tmp/ltximg
> 3. emacs-29 --version
> GNU Emacs 29.3
> Copyright (C) 2024 Free Software Foundation, Inc.
>
> 4. emacs-29 -Q
> 5. C-x C-f /tmp/tmp.org
> 6. C-n
> 7. C-c C-x C-l
> 8. C-c C-x C-l
> 9. I do not observe any warnings
Ihor Radchenko writes:
>> * testing/lisp/test-org-clock.el (test-org-clock/clocktable/insert):
>> Add a clock time that does not include timestamps.
>> ...
>> -
>> - (goto-line 2)
>> + (insert (org-test-clock-create-clock ". 1:00" ". 2:00")
>> + "CLOCK: => 1:00\n")
>
> This
Anush V writes:
> Thanks for outlining your steps. I’ve added an additional step
> (5). Here's the updated sequence:
> ...
> 5. M-: (setq org-startup-numerated t)
Then, it looks like a duplicate of
https://list.orgmode.org/orgmode/caedgbw4gmfmpt4-w6edrh7poapd5drarbtusfulrq7vbvtu...@mail.gmail.c
Ihor Radchenko writes:
> Alexander Adolf writes:
>
>>> In fact, CLOCKSUM property does not support custom summaries.
>>
>> ???
>
> AFAIU, you cannot do %CLOCKSUM{max}.
Ah, I see; that's what you meant.
>> [...]
>> Thus, from my point of view, having a :formatter for the columnview
>> dblock wo
Morgan Smith writes:
>>> - (goto-line 2)
>>> + (insert (org-test-clock-create-clock ". 1:00" ". 2:00")
>>> + "CLOCK: => 1:00\n")
>>
>> This is not a valid clock format. Matching such lines is a bug.
>> See https://list.orgmode.org/orgmode/87wpkkhafc.fsf@saiph.selenimh/
>
>
Alexander Adolf writes:
>> In any case, making column views more flexible is welcome.
>> [...]
>
> 😇 Lure me into contributing a patch? fair enough; I might just as well
> give that a try. I presume I'd get some support here on this list?
> And/or on IRC (e.g. libera.chat#org-mode)?
Yup. You are
Ihor Radchenko writes:
> So, in the message I linked, Nicolas (the major Org mode contributor)
> was not right. I hence need to fix the parser and update Org syntax
> page. This includes fixing `org-element-clock-line-re' to account for
> CLOCK: => 1:00 syntax.
Cool. I guess ping this thread wh
"Rohit Patnaik" writes:
> #+BEGIN_SRC elisp
> (concat bullet
> ...
> (and contents
>(org-trim (replace-regexp-in-string "^" "" contents
> #+END_SRC
>
> and I'm wondering why it's adding indentation in front of the bullet.
> Naively, I
> would expect the result of this sni
> Then, it looks like a duplicate of
> https://list.orgmode.org/orgmode/caedgbw4gmfmpt4-w6edrh7poapd5drarbtusfulrq7vbvtu...@mail.gmail.com/
>
> There is no bug on the latest development version of Org mode (main).
Sure!
Thank you for pointing it out and helping with the resolution.
--
Anush V
Ihor Radchenko writes:
> Björn Bidar writes:
>
>> The bug also seems to affect `org-attach`.
>
> Fixed, on main. Alongside with other similar places.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=78e9dd0c4
I noticed after the change that captured links are not picked up.
E.
Hi,
Maybe not... because style= is a keyword for the biblatex package, while
bibstyle or citestyle aren't.
Best, /PA
On Sat, 13 Apr 2024 at 16:32, Ihor Radchenko wrote:
> Pedro Andres Aranda Gutierrez writes:
>
> > HI,
> > Attached is a small patch to allow explicitly adding style= in the
> b
Sorry... I was not right... You are right. I'll take a look at it again.
/PA
On Sun, 14 Apr 2024 at 07:22, Pedro Andres Aranda Gutierrez <
paag...@gmail.com> wrote:
> Hi,
>
> Maybe not... because style= is a keyword for the biblatex package, while
> bibstyle or citestyle aren't.
>
> Best, /PA
>
>
Hello,
Yes, that clarifies things quite a bit. I thought that the contents of the list
item only included that specific item, when in reality it includes the item and
all sub-lists.
Thanks,
Rohit
24 matches
Mail list logo
