Colin Baxter writes:
> I have now discovered what is causing the org-persist warnings. It is
> because my org-agenda files have local variables present. If I remove
> the local variables, the warnings disappear.
Do you mean file-local? Can you provide a minimal Org file example?
I also have
>
> Do you still keep this line in your init:
>
> (advice-add 'org-latex--org-table :override #'my/org-latex--org-table) ?
You were right. My bad.
I confirm, the new function works and is a significant improvement.
Vikas
> > \begin{longtblr}[options 1 options 2 options 3 options 4]{align}
>
> PS: I think the options should be separated by commas. In this
> case, it's necessary to replace the line:
>
> (mapconcat (lambda (x) (mapconcat 'identity x "")) options-list " ")))
>
> by this line:
>
> (mapconcat (lambda
> Do you still keep this line in your init:
>
> (advice-add 'org-latex--org-table :override #'my/org-latex--org-table) ?
>
> If so, rename the function from my previous email as
> `my/org-latex-org-table' and re-evaluate it. And comment the old
> `my/org-latex-org-table'.
>
You were right. My
Juan Manuel Macías writes:
> \begin{longtblr}[options 1 options 2 options 3 options 4]{align}
PS: I think the options should be separated by commas. In this
case, it's necessary to replace the line:
(mapconcat (lambda (x) (mapconcat 'identity x "")) options-list " ")))
by this line:
Vikas Rawal writes:
> This still seems to exporting the second "options" value only.
Do you still keep this line in your init:
(advice-add 'org-latex--org-table :override #'my/org-latex--org-table) ?
If so, rename the function from my previous email as
`my/org-latex-org-table' and re-evaluate
I have now discovered what is causing the org-persist warnings. It is
because my org-agenda files have local variables present. If I remove
the local variables, the warnings disappear.
Best wishes,
Colin.
Greetings, fellow Emacsians!
On behalf of the EmacsConf 2021 organizers team, I'm very excited to
announce the program for EmacsConf 2021 (Nov 27 and 28), available at:
https://emacsconf.org/2021/schedule
We'll continue working on scheduling the talks in a way that works
>
> First, you need to convert a plist to an alist (source:
> https://caiorss.github.io/Emacs-Elisp-Programming/Elisp_Programming.html#sec-1-8-4):
>
>
> And this would be the modified function:
>
This still seems to exporting the second "options" value only.
Vikas
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> Thanks for quick patch, I'm on the latest main. and I pulled your patch. Now
>> it's not infinite
>> looping, but still takes about 3.5 seconds. So I take another profiler
>> profiling again.
>
> Fixed (hopefully) on main via
Hi all,
* lisp/org-src.el (org-src-font-lock-fontify-block): Reset the
modification flag of the temporary fontification buffer after
fontifying.
Without this some modes cause Emacs to prompt about unsaved buffers
when exiting: `Save buffer *org-src-fontification:...-mode*?'
(I'm seeing this
"Christopher M. Miles" writes:
> Thanks for quick patch, I'm on the latest main. and I pulled your patch. Now
> it's not infinite
> looping, but still takes about 3.5 seconds. So I take another profiler
> profiling again.
Fixed (hopefully) on main via 1b2d06880. Please, restart emacs after
Max Nikulin writes:
> P.S. Earlier added "yes" entry were successfully removed by my previous
> message to this thread with "X-Woof-Bug: canceled" header. Hope, correct
> header will be set by "X-Woof-Bug: Bug: font-lock error with - in
> code-mode (reopened)"
Thanks! I can see the correct
This is a message to track the issue on https://updates.orgmode.org
On 01/10/2021 16:56, Ihor Radchenko wrote:
"Dr. Arne Babenhauserheide" writes:
When parsing the following code:
Am richtigen Ort zur richtigen Zeit (=+=; 1x pro Abenteuer im richtigen
Moment auftauchen), Computeraffinität
Ihor Radchenko writes:
> "Christopher M. Miles" writes:
>
>> Here is the profiler report:
>>
>> CPU:
>>
>> #+begin_example
>> 4003 66% - command-execute
>> 4003 66% - call-interactively
>> 3913 65% - funcall-interactively
>> 3320 55%- kill-buffer
>>
"Christopher M. Miles" writes:
> Here is the profiler report:
>
> CPU:
>
> #+begin_example
> 4003 66% - command-execute
> 4003 66% - call-interactively
> 3913 65% - funcall-interactively
> 3320 55%- kill-buffer
> 3318 55% -
Here is the profiler report:
CPU:
#+begin_example
4003 66% - command-execute
4003 66% - call-interactively
3913 65% - funcall-interactively
3320 55%- kill-buffer
3318 55% - org-persist-write-all-buffer
3318 55% -
> Ihor Radchenko writes:
> Colin Baxter writes:
>> Ok, I now applied your patch and remade org-mode. Unfortunately,
>> I don't see any change. I still get the warning on all the
>> archive commands: org-agenda-archive-default, org-agenda-archive
>> and
18 matches
Mail list logo