Thank you very much.
signature.asc
Description: PGP signature
Ah, my bad, I was a bit distracted.
Ihor Radchenko writes:
> Sébastien Gendre writes:
>
>> I also created a file "./common-setup.inc" to share some settings between
>> my Org files. Like the bibliography file definition. This setup is
>> referenced like this in my 2 Org files:
>>
>> #+SETU
Ihor Radchenko writes:
"Thomas S. Dye" writes:
I'm seeing this message often:
Invalid function: org-fold-core-suppress-folding-fix [91
times]
Do I have a problem? Is there a fix?
You have a problem with installation.
Most likely, some parts of Org mode were compiled/loaded from
b
they seem random, but once they start in a file, they sometimes occur
more often.
e.g. open a heading, open a child, and the first heading closes.
On Sat, Aug 9, 2025 at 5:53 AM Ihor Radchenko wrote:
>
> Samuel Wales writes:
>
> > i am not getting that error yet, but i am getting folding glitch
Hello,
I apologize for the delay in re-submitting this. I have created a
number of tests to test the current implementation. Then I have
reimplemented `org-clock-sum' using the org-element api (ensuring all
tests still pass). Then I added a new feature that will issue a warning
if the timestamp
Hey Ihor,
I think we might be talking about different levels on both points.
On 2025-08-09 11:27, Ihor Radchenko wrote:
> Not really. Org export uses specialized internal export backends in
> some scenarios. For example, see `org-export-toc-entry-backend'.
On 2025-07-13 09:57, Ihor Radchenko wro
* Sharon Kimble [2025-08-04 10:53]:
>
> Is it possible to have a link in file B to file A, which when double-clicked,
> or C-c'ed, or some other form of automating it, causes file A to activate
> please?
>
> The backstory is that I'm copying my blog posts (written in org-mode of
> course) i
"Mark A. Hershberger" writes:
> I ran into a problem with an org-src-font-lock-fontify-block and, before
> I thought to check the parent org-mode repo, I made a fix to the master
> branch of emacs.
>
> My fix:
> https://cgit.git.savannah.gnu.org/cgit/emacs.git/commit/?id=c4af4b39018923fdfc22b515a
I ran into a problem with an org-src-font-lock-fontify-block and, before
I thought to check the parent org-mode repo, I made a fix to the master
branch of emacs.
My fix:
https://cgit.git.savannah.gnu.org/cgit/emacs.git/commit/?id=c4af4b39018923fdfc22b515acc1f6ba3f2b024d
The fix in org-mode:
htt
>>> "IR" == Ihor Radchenko writes:
> Uwe Brauer writes:
>> I have a org file containing the lines
>>
>> #+begin_src
>> %%% Local Variables:
>> %%% mode: LaTeX
>> %%% TeX-master: t
>> %%% End:
>> #+end_src
>>
>> When I close and reopen the file the buffer is now in LaTeX mode, so the
>> src bl
Thank you!
I was going to say I didn't think of the outline path as missing so much as
provided but empty, so I'm quite happy to hear you fixed that.
--
Omar
Lars Frantzen writes:
>> AFAIK, the best you can do is setting isearch-invisible to t.
>> Otherwise, I do not think that isearch supports searching inside
>> overlays with 'display property.
>
> For "isearch-invisible" it says "Not documented as a variable." I tried
> "isearch-toggle-invisible" b
Max Nikulin writes:
>>> I do not think that general case of nested links should be supported.
>>
>> Could you elaborate why?
>
> Effect of nested link is confusing. Users may be in doubts what link
> should be activated, borders between links may be hidden. Nested links
> are not allowed in HT
Uwe Brauer writes:
> I have a org file containing the lines
>
> #+begin_src
> %%% Local Variables:
> %%% mode: LaTeX
> %%% TeX-master: t
> %%% End:
> #+end_src
>
> When I close and reopen the file the buffer is now in LaTeX mode, so the
> src block was not recognised as src block? Is this a bug
"Jacob S. Gordon" writes:
>> IMHO, providing an export backend sounds much cleaner (and more
>> flexible).
>
> No argument there. My concern is that a separate export path is a
> surprise to the user. IOW, I could adjust `org-html-with-latex' to get
> MathJax or images for math, but I’d have to c
Jacek Generowicz writes:
> Here is an org document setting out my question. It should export cleanly
> to HTML, without any dependencies other than Jujutsu.
> ...
> #+begin_src sh :noweb yes :exports code :dir /tmp/time-travel-wtf/branching
> echo A <>
> jj new <>
> echo A <>
> #+end_src
> So far
On 09/08/2025 15:37, Ihor Radchenko wrote:
that had issues with exporting links like
[[info:emacs#Echo%20Area][info:emacs#Echo Area]]
However, we are getting way too many special cases all over the code by
now. Maybe, after all, it is a better idea to bring back the nested
links, and remove the
Christian Moe writes:
> Nesting =#+begin_summary= inside a =#+begin_details= block creates a
> newline, though, and in Firefox, the newline separates the collapse/expand
> arrow
> from the summary text, which is a bad look.
Yeah. Looks like can only contain "inline" HTML markup, while
Org puts
"Peter Becich (pbecich)" via "General discussions about Org-mode."
writes:
> Thanks. Here is the patch, if we decide the change this default now. Please
> run `make test`; I do not have all the dependencies. `make compile` succeeds.
Thanks for the patch, but we do not make breaking changes on b
Ihor Radchenko writes:
>
> Yue Yi writes:
>
> > Here is the improved patch.
> > From 7db5f6fa55f6d082e911b8e852fe5ecd47878ebd Mon Sep 17 00:00:00 2001
> > From: Yue Yi
> > Date: Sat, 9 Aug 2025 12:31:41 +0800
> > Subject: [PATCH] ox-html: Fix TOC generation for non-toplevel headlines
>
> Applie
Alyssa Ross writes:
>> We will support such format in future, but not yet.
>> Currently, this will produce undefined behavior.
>> See
>> https://list.orgmode.org/orgmode/canvbq5mau9fk-43sms4x5kvz-jtsszfmrgzrh7eusptnrzh...@mail.gmail.com/
>
> I see. So is it a documentation bug that the example
Yue Yi writes:
> Here is the improved patch.
> From 7db5f6fa55f6d082e911b8e852fe5ecd47878ebd Mon Sep 17 00:00:00 2001
> From: Yue Yi
> Date: Sat, 9 Aug 2025 12:31:41 +0800
> Subject: [PATCH] ox-html: Fix TOC generation for non-toplevel headlines
Applied, onto main.
https://git.savannah.gnu.org/
Greetings again.
Ihor Radchenko writes:
>>> Should be 9.8. We do not make breaking changes in bugfix releases.
>>> See https://orgmode.org/worg/org-maintenance.html#branches
>>
>> Changed it to 9.8, although I think we will have no breaking changes
>> after all your latest improvement ideas hav
Vincent Koppelmans writes:
> Here is the complete minimal example, as the HTML exported version of the
> email did not include org markup:
>
> Tangling a source block that contains a variable from another source block
> results in an additional incorrect new line at the end of the variable valu
Ihor Radchenko writes:
> Alyssa Ross writes:
>
>> I get the same error as Omar, but to reproduce it in emacs -Q I have to
>> (require 'org-capture) first. Is that helpful?
>
> Yup.
> That's because of
>
>>> ("j" "Journal entry" plain
>>>(file+olp+datetree "Journal.org"))
>
> which
Konstantin Borisov writes:
>> Using line numbers is not exactly reliable. What if the source org file
>> changes? The line numbers will not be correct then.
>
> From the theoretical perspective of view you are right. But from the
> practical I think line numbers should work well enough.
I doubt
Ihor Radchenko writes:
> I have a few comments about the commit message.
> [...]
> We generally put changelog entries at the beginning, optionally
> following by explanation, not wise versa. We also `quote' Elisp symbols
> and leave two spaces between sentences. See
> https://orgmode.org/worg/o
"Thomas S. Dye" writes:
>Debugger entered--Lisp error: (void-variable graphviz-dot)
> ...
> graphviz-dot-mode()
> org-src-font-lock-fontify-block(#("dot" 0 3
You have some problem with your graphviz-dot-mode installation.
> I use dot code blocks fairly frequently and don't rememb
Alyssa Ross writes:
> I get the same error as Omar, but to reproduce it in emacs -Q I have to
> (require 'org-capture) first. Is that helpful?
Yup.
That's because of
>>("j" "Journal entry" plain
>> (file+olp+datetree "Journal.org"))
which is missing the outline path.
We will
Samuel Wales writes:
> i am not getting that error yet, but i am getting folding glitches
> upon folding/unfolding of headings and upon moving of list items.
>
> perhaps not related? might be in the past few git snapshots.
No idea, because I need more details on what "glitches" you are talking
"Thomas S. Dye" writes:
> I'm seeing this message often:
>
> Invalid function: org-fold-core-suppress-folding-fix [91 times]
>
> Do I have a problem? Is there a fix?
You have a problem with installation.
Most likely, some parts of Org mode were compiled/loaded from built-in
version, and some
Yue Yi writes:
> Yue Yi writes:
>
>> > > In other words, when scope is non-nil, we can always obtain an Org
>> > > element with a logical hierarchical structure. However, when scope is
>> > > nil, we may not be able to do so, as explained in my previous
>> > > email. This is why I introduced the
Ihor Radchenko writes:
> Thanks for the patch, but I am confused *why* you need this.
> `user-error' will stop macro just fine. Macros will not loop forever
> already.
Oh! I have just (re-)tried it, and you are right. It must had been the
NS port freezing on me, which is quite common, unfortun
Max Nikulin writes:
>> Originally, the link nesting was disallowed to handle the following bug
>> report:
>> https://list.orgmode.org/orgmode/87twa23k74@nicolasgoaziou.fr/
>> that had issues with exporting links like
>> [[info:emacs#Echo%20Area][info:emacs#Echo Area]]
>>
>> However, we are
Max Nikulin writes:
> I think, it is better to ask Timothy as the author of the blog post. I
> expect that either preview for http: images never worked or some third
> party package is involved. ...
They kind of did not work. (I just checked with Org 9.5)
But this is not an excuse for us - we
Karthik Chikmagalur writes:
>>> [[https://github.com/larsmagne/meme/raw/master/images/Grandma-Finds-The-Internet.jpg]]
>>>
>>> I expect that it may be related to TRAMP file paths like
>>> /https:/host/file.png (by default http is disabled in gvfs backend
>>> though), but not for regular URLs.
>
36 matches
Mail list logo
