The WebM version worked fine for me.
Yours,
Christian
Robert Love writes:
> Has anyone successfully watched this? It has very intermittent sound,
> cutting out frequently then stoping for many minutes. I don’t see the
> referenced QR code.
>
> On Feb 6, 2025, at 4:19 PM, Amy Grinn wrote:
Paul Stansell writes:
>> May you please check which Org commit you are on?
>>
>
> I'm using the following version:
> Org mode version 9.8-pre (release_9.7.18-205-g0ce4f3.dirty @
> ~/.emacs.d/org-mode-git/lisp/)
>
> The ".dirty" is because of the patch you asked me to apply.
Ok. I see.
I thought
Max Nikulin writes:
>> I do not see why we cannot change it to use emacs instead of
>> pandoc to render html.
>
> It is challenging to implement proper sandboxing for elisp. Otherwise
> risk of arbitrary code execution exploits is excessively high. My
> impression from some comments is that Git
On 09/02/2025 17:15, Ihor Radchenko wrote:
One note is that gollum is using org-ruby renderer, which is not 100%
accurate.
Org-ruby has a lot of limitations, I do not think it is suitable for Worg.
I do not see why we cannot change it to use emacs instead of
pandoc to render html.
It is cha
Paul Stansell writes:
>>
>> One weird thing in the above warning is //. Is // really what you see?
>>
>
> If you mean the "//" in the following line:
>
> Warning (emacs): Emacs reader failed to read data in
> "~/.cache/org-persist//gc-lock.eld". The error was: "End of file during
> parsing"
>
> t
> I think that the easiest way to test things would be simply trying the
> latest main branch.
>
Okay, I'll do that.
> Note that you no longer need the manually installed patch - it has been
> installed upstream already.
>
Okay, thanks
>
> > The ".dirty" is because of the patch you asked me to apply.
>
> Ok. I see.
> I thought that you are testing the latest main after my last message
> where I mentioned 3 commits I installed.
>
I thought I was testing the correct version. I thought I pulled the latest
version after you made th
I am trying to use `pp', as documented:
‘pp’: Result converted to pretty-print source code. Enclosed in a code block.
Languages supported: Emacs Lisp, Python, and Ruby. Usage example: ‘:results
value pp’.
https://orgmode.org/manual/Results-of-Evaluation.html
In `emacs -Q':
#+BEGIN_SRC e
The custom types for org-clock-rounding-minutes and
org-table-duration-custom-format suffer from excessive quoting. Patch
attached.
Emacs : GNU Emacs 31.0.50 (build 4, x86_64-pc-linux-gnu, GTK+ Version 3.24.38,
cairo version 1.16.0)
of 2025-02-04
Package: Org mode version 9.7.11 (release_9.7.1
Paul Stansell writes:
> This is the head of my git clone.
>
> Commit c2d57df0ef54e4f517bdf47f42d0c6b37fe02401 (HEAD -> main, origin/main,
> origin/HEAD)
> Author: Ihor Radchenko
> Date: 2025-01-12 11:41:38 +0100
> ...
> Was I missing essential updates?
This commit should include the updates I
Robert Pluim writes:
> The custom types for org-clock-rounding-minutes and
> org-table-duration-custom-format suffer from excessive quoting. Patch
> attached.
Thanks!
May you please rebase your changes to the latest bugfix?
I've already fixed one of the :type specifications in
https://git.savann
Malcolm Purvis writes:
>
>> There is another problem though. Consider: 1. M-x org-lint
>> 2. Switch back to the original .org buffer 3. M-g M-n 4. Observe
>> link report and .org window swapped and point moving back
>>to the lint report. It is not what usually happens with error
>>
Hi all,
I was wondering if there was anything I could do to help get this patch
reviewed and, after any required tweaks, integrated. I don't know about
best practices and expectations yet so figured I would bump to learn more.
Thanks in advance.
Best,
Jules
On Sun, Feb 2, 2025 at 11:38 AM Jules
Jules Tamagnan writes:
> I was wondering if there was anything I could do to help get this patch
> reviewed and, after any required tweaks, integrated. I don't know about
> best practices and expectations yet so figured I would bump to learn more.
> Thanks in advance.
Just wait a little. It is o
[AMD Official Use Only - AMD Internal Distribution Only]
Seen on Doom Emacs 27.2 (build 1, x86_64-mingw32) running on Windows 11.
>>
Warning (org-element-cache): org-element--cache: Org parser error in
localnotes.org::5148. Resetting.
The error was: (error "Invalid search bound (wrong side of p
Rudolf Adamkovič writes:
> #+BEGIN_SRC emacs-lisp :results value pp
> '(1 2 3 4 5 6 7 8 9 10)
> #+END_SRC
>
> #+RESULTS:
> : nil
>
> Why is '(1 2 3 4 5 6 7 8 9 10) printed as nil?
Duplicate of
https://list.orgmode.org/orgmode/87r04guyq9@gmail.com/
Fixed yesterday.
--
Ihor Radchenko // yan
>
> This commit should include the updates I mentioned.
> However, "release_9.7.18-205-g0ce4f3.dirty" says that your loaded Org
> mode is "0ce4f3" back from last year. Maybe you just forgot to do make
> autoloads. Maybe you are loading Org from a different folder, not where
> you pulled the latest
[AMD Official Use Only - AMD Internal Distribution Only]
The org version is 9.6.
From: Ihor Radchenko
Sent: Monday, February 10, 2025 11:27 AM
To: Rivoallon, Frederic
Cc: emacs-orgmode@gnu.org
Subject: Re: Warning/Error message seen on an org file...
Caution: T
Dear Jean Louis, thanks so much for this detailed response! This is
incredibly helpful, especially on using embeddings and PostgreSQL for
structured linking. Your LLM function example is also great to see in
action! I’ve never used PostgreSQL or anything similar before, but I’ll
give it a try. It s
"Rivoallon, Frederic" writes:
> Seen on Doom Emacs 27.2 (build 1, x86_64-mingw32) running on Windows 11.
>>>
>
> Warning (org-element-cache): org-element--cache: Org parser error in
> localnotes.org::5148. Resetting.
> The error was: (error "Invalid search bound (wrong side of point)")
Thanks
20 matches
Mail list logo
