Dear Ihor and Max,
thanks for the feedback and apologies for responding that late.
On Wed, 15 May 2024 at 13:48, Max Nikulin wrote:
> Is it possible to keep title formatting from .bib files till it becomes
> known that specific style requires sentence case for particular entry
> type? I had a h
> Ihor Radchenko writes:
> Eli Zaretskii writes:
>>> Can we instead store them in memory? Yes, but (1) it will make
>>> Emacs RAM consumption grow constantly and more and more previews
>>> are generated; (2) it will require significant changes in the
>>> Org mode codebase
Colin Baxter writes:
> > 1. not reasonable in a sense that it has downsides compared to
> > what we do now - save latex previews on disk 2. impossible in a
> > sense that we do not have an existing toggle to store cached
> > previews in memory. Such functionality would have to be
Hello. I'm giving a presentation about information management for large
distributed teams during a crisis, using org mode and git. It has been
decades since I have NOT had LaTeX on my machine, and it preceded emacs
for me, so I can't recall whether org mode needs LaTeX to export or not.
In other
I've attempted to disable the element cache using `(setq org-element-use-cache
nil)`.
However, it seems that cache is still in use, because I'm regularly getting
org-element--cache errors like:
⛔ Warning (org-element): org-element--cache: Org parser error in
todo-routine.org::55572. Resetting
> From: Ihor Radchenko
> Cc: Eli Zaretskii , n142...@gmail.com, emacs-orgmode@gnu.org
> Date: Wed, 19 Jun 2024 10:35:39 +
>
> If you do not use latex-preview or other features that cache their
> results, org-persist should not create any files or directories.
> (It currently does create gc-lo
Eli Zaretskii writes:
> Let me clarify. In the scenario in which I found out about Org
> caching, I didn't use latex-preview, not at all
Sure. Org uses multiple caches.
You encountered the one created by parser. The parser cache in
particular can be disabled. But not the latex preview cache
Al Haji-Ali writes:
> On 18/06/2024, Ihor Radchenko wrote:
>> Hmm. Thanks, but the patch does not apply on my side.
>> May you instead create a patch as a separate file, add the commit
>> message, and attach that patch file in the email reply?
>
> See attached.
Thanks. Although this is a differe
Platon Pronko writes:
> I've attempted to disable the element cache using `(setq
> org-element-use-cache nil)`.
>
> However, it seems that cache is still in use, because I'm regularly getting
> org-element--cache errors like:
>
> ⛔ Warning (org-element): org-element--cache: Org parser error in
András Simonyi writes:
> I added a few words about this now both in the docstring and in the
> ORG-NEWS entry -- I've attached
> the updated patch.
Thanks! I have no further comments.
Feel free to install the patch.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode
"Cook, Malcolm" writes:
> Since my (bash) shell prompt is a (more or less) constant string (e.g.
> "myname@myhost> ").
>
> So, my workaround is to:
>
> (setq comint-prompt-regexp "myname@myhost> ")
>
> Then the filtering works perfectly.
>
> Of course if I change my name, this will fail. Or
Ihor Radchenko writes:
> Ping ;)
So I gave up on this specific patch because I wrote a patch to just
rewrite the entire `org-clock-sum' function using org-element API.
Attached is the `org-clock-sum' rewrite patch which I've been using for
a while with no issues. I have half finished patches lo
* doc/org-manual.org: Add missing '~'.
* lisp/org-element-ast.el (org-element-deferred): Fix typo in docstring.
* lisp/org-element.el (org-element-archive-tag,
org-element-drawer-re-nogroup, org-element--cache-log-message): Fix
typos in docstring.
(org-element--current-element, org-element--cache-f
Morgan Smith writes:
> * doc/org-manual.org: Add missing '~'.
> * lisp/org-element-ast.el (org-element-deferred): Fix typo in docstring.
> * lisp/org-element.el (org-element-archive-tag,
> org-element-drawer-re-nogroup, org-element--cache-log-message): Fix
> typos in docstring.
> (org-element--cu
Morgan Smith writes:
> So I gave up on this specific patch because I wrote a patch to just
> rewrite the entire `org-clock-sum' function using org-element API.
> Attached is the `org-clock-sum' rewrite patch which I've been using for
> a while with no issues. I have half finished patches locally
I guess in a way the other thread (Sub: orgalist send bug) is done and
orgalist in the new version is usable enough for me that I can live
with the warning.
But I was troubled with the possibility of lots of load path shadows
so I spent some time cleaning up. [In any case since emacs had got
upgra
> Ihor Radchenko writes:
> Eli Zaretskii writes:
>> Let me clarify. In the scenario in which I found out about Org
>> caching, I didn't use latex-preview, not at all
> Sure. Org uses multiple caches. You encountered the one created
> by parser. The parser cache in
Colin Baxter writes:
> This what I cannot understand. If the user never uses latex preview why
> cannot the latex preview cache be disabled? I don't want to go on and on
> and become a bore - I've said my piece and I will be silent from now
> on.
I believe that we have some kind of misunderstand
Rustom Mody writes:
> I figured its these 5 lines at the start of org-element-at-point
>
> (unless (derived-mode-p 'org-mode)
> (display-warning
> '(org-element org-element-parser)
> (format-message
>"`org-element-at-point' cannot be used in non-Org buffer
Ihor Radchenko writes:
>> Ideally the fix in that commit should be ported to the org-element API.
>> Notably, the malformed clock from the email thread from that commit is
>> parsed a little strangely by org-element. I'm not sure what effect this
>> has on my rewrite patch but regardless, we sho
On Wednesday, June 19th, 2024 at 08:55, Christopher W. Ryan
wrote:
> In other words, if a complete novice, knowing nothing about LaTeX and
> not having it on their machine ever, installed emacs and created an org
> mode file, could they export via latex to PDF? Could they export to html?
To HTM
Dear All,
On Wed, 19 Jun 2024 at 16:35, Ihor Radchenko wrote:
> Thanks! I have no further comments.
> Feel free to install the patch.
Thanks, I'have applied the patch to main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=782f6c33beed8d7baac9549b94a6a08040eba838
best wishes,
22 matches
Mail list logo
