Hi,
Our (Org mode) CI is now failing to run ob-scheme tests because Geiser
fails to run REPL:
https://builds.sr.ht/~bzg/job/1035753
Test test-ob-scheme/tables backtrace:
(obsolete max-specpdl-size)()
geiser-syntax--read-from-string("#")
geiser-guile-update-warning-level()
geiser-guile--s
Roshan Shariff writes:
> Thanks for the feedback! I'm attaching a new version of the patch that
> improves the commit message and avoids the use of file-name-concat.
Thanks!
Applied, onto main, with minor amendments.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=4ea9a98f8
I ad
Bastien Guerry writes:
>> So, there is still a problem with ESS installation.
>> We may need to update the build manifest yet more.
>> Probably "elpa-ess" is installed into some weird place, out of
>> load-path.
>
> I added the load-path for ess, this seems to work.
May it be enough to drop --qu
On 2023-08-05, at 11:49, Ihor Radchenko wrote:
> Marcin Borkowski writes:
>
>> Thanks a lot, that works! (Apart from the issue with lines beginning
>> with a star, possibly preceded by whitespace, which are "escaped" with
>> a comma - but that is a known thing in Org, and I can easily circumv
Ihor Radchenko writes:
> Should we try to make a call for maintenance at least for some of these
> libraries?
Definitely. We should probably prioritize files in this list, then
ask on this list *and* on the web.
Let's make sure we propose this as something fun to do, not a chore.
How do you w
Akira Kyle writes:
> It's been five years since I initially wrote this patch and two years
> since I started my assignment processes
More precisely: I'll double-check with the FSF legal team that having
your name in the FSF copyright registers means that you can contribute
to Emacs and Org-mode
Hi Akira,
Akira Kyle writes:
> I have been informed that this document my university has
> provided is queued with the FSF legal team for eventual review.
Thanks for your answer.
I suggest we take this off-list and try to sort it out with the FSF
legal team directly.
--
Bastien Guerry
Minor change below.
Ihor Radchenko writes:
> David Masterson writes:
>
>> I think begin.html is a good starting point. Mentioning 'texdoc latex'
>> is also simple (and more LaTeX specific) and most likely to work. You
>> could include a parenthetical note that, if it doesn't work, try the
>>
Max Nikulin writes:
> On 05/08/2023 05:57, Rudolf Adamkovič wrote:
>> +*** Make ~ob-sqlite~ use in-database by default
>
> "use in-memory database"
Oops! Fixed.
>> +SQLite source blocks with no ~:db~ argument now execute against a
>> +transient in-memory database by default.
>
> I am unsure, b
Hello
> #+begin_src lang :tangle yes foo no bar baz "foo bar"
> should yield
> '("yes" "foo" "no" "bar" "baz" #("foo bar" 0 7 (org-babel-quote t)))
> We will allow using quotes to include whitespace.
> In such scenarios, we still capture this unknown value.
> This is useful for some third-party b
Hi
Could it be possible, in org-capture, to capitalize the text entered
from a previous prompt?
Example:
I have this part of an org-capture template:
* %^{CLIENT} _%^{Project}_ /%^{Description}/
:PROPERTIES:
:DIR: z:/! 2023/%\\1-%\\2-%\\3
:END:
I would like to know if it is possible to “
On Sat, Aug 05, 2023 at 07:29 PM, Bastien Guerry
wrote:
Ihor Radchenko writes:
Akira, may I know if you managed to clear the FSF paperwork?
I've just checked and Akira's is a registered FSF contributor
since
last may.
Unfortunately I was informed that I am only allowed to make
"sm
Ihor Radchenko writes:
> So, there is still a problem with ESS installation.
> We may need to update the build manifest yet more.
> Probably "elpa-ess" is installed into some weird place, out of
> load-path.
I added the load-path for ess, this seems to work.
I also added the gnuplot dependency
Ihor Radchenko writes:
> Akira, may I know if you managed to clear the FSF paperwork?
I've just checked and Akira's is a registered FSF contributor since
last may.
--
Bastien Guerry
Understood, I'm currently trying it out. Maybe I'll post later in that thread.
> On Aug 5, 2023, at 22:26, Ihor Radchenko wrote:
>
> yc wang writes:
>
>> ... Just wondering, will these LaTeX preview changes also be integrated into
>> HTML publishing? There are many common SVG-related function
Hi Ihor,
On Sat, 5 Aug 2023 at 04:23, Ihor Radchenko wrote:
> First, minor one: please put two spaces between sentences in the commit
> message. It is our convention.
> `file-name-concat' is only available since Emacs 28.
> Please use `org-file-name-concat'.
Thanks for the feedback! I'm attachin
yc wang writes:
> ... Just wondering, will these LaTeX preview changes also be integrated into
> HTML publishing? There are many common SVG-related functionalities like
> automatic alignment and scaling, equation labeling and positioning, etc.
By default, HTML export uses MathJax to render LaT
Thank you for the information.
It's really impressive. Just wondering, will these LaTeX preview changes also
be integrated into HTML publishing? There are many common SVG-related
functionalities like automatic alignment and scaling, equation labeling and
positioning, etc.
Sincerely,
ywangmy
>
Juan Manuel Macías writes:
>> And it looks like at least on of the test conditions is not trivial to
>> fix without knowing French. May you or somebody familiar with French
>> punctuation take a look?
>
> I'm afraid I'm not very familiar with the syntax and usage of tests, so
> I have to study th
yc wang writes:
> ... When I enable the dvisvgm option for exporting TeX snippets, I noticed
> that the displayed math environment enclosed in \[…\] is not recognized as
> "equations," similar to other math environments like
> \begin{align*}...\end{align*}, which are placed in a “equation-cont
Max Nikulin writes:
> I was trying to modify publish.sh to collect errors up to a reasonable
> number, a draft is attached. It can be improved further to save list of
> failures to some file, so final step of .build.yml may be to check
> whether this file is empty and to send a notification ot
On 31/07/2023 23:41, Ihor Radchenko wrote:
Max Nikulin writes:
I hope, there is a better way to address the issue with failure
notifications.
That sounds too complex.
I think we can simply add an extra "check" task to
https://git.sr.ht/~bzg/worg/tree/master/item/.build.yml
It will run after "
Christian Barthel writes:
> while upgrading from emacs 28.1 to 29.1, my org-agenda stopped working.
> The message in the echo area was:
>
> --8<---cut here---start->8---
> Search failed: "\\]+\\)>"
> --8<---cut here---end
Bastien Guerry writes:
>> What about the other approach I proposed?
>> (where we export skipping errors first, upload, and then re-export,
>> catching all errors this time just to trigger an email to notify about
>> the failure).
>
> Yes, let's do this.
Ok. I added a new --debug command line arg
On 2023-08-02 08:45, Ihor Radchenko wrote:
> `rx' would be great.
> But even adding comments like in your example would be an improvement.
Since the future of this code snippet seems to be uncertain I went for
comments only.
And I thought I was pretty much done when I noticed at least one majo
Hi, Ihor,
Ihor Radchenko writes:
> Welcome back :)
thanks! :-)
>> In the meantime, I'm submitting this patch with a fix for second-level
>> French `smart quotes': the correct quotes should be “” (without spaces,
>> as in Spanish or Greek) (please, some francophone correct me, if I'm
>> wrong...
Dear Community,
I hope this letter finds you well. My name is ywangmy, and I am an avid user of
org-export for exporting TeX snippets to HTML. First and foremost, I want to
extend my appreciation for the hard work and dedication put forth by the
developers to create such a valuable tool.
I am
Roshan Shariff writes:
> * org-macs.el (org-compile-file, org-compile-file-commands): Avoid
> converting the source path to be relative to the default-directory,
> which breaks for absolute source paths when the current directory is a
> symlink.
>
> Commit 5a8a1d4ff [1] changed org-compile-file t
Marcin Borkowski writes:
> Thanks a lot, that works! (Apart from the issue with lines beginning
> with a star, possibly preceded by whitespace, which are "escaped" with
> a comma - but that is a known thing in Org, and I can easily circumvent
> it.)
May you elaborate why you consider this a bug
Ihor Radchenko writes:
> Should we try to make a call for maintenance at least for some of these
> libraries?
Ping!
Bastien Guerry writes:
>>> The last message I received from them was over a month ago and my
>>> last follow up email to them was ten days ago.
>>
>> Bastien, may you follow up with Craig about the status?
>
> I don't see the FSF copyright assignment status for
> ak...@akirakyle.com - please CC
Ihor Radchenko writes:
> We thus need volunteers to help maintaining Org LaTeX export library -
> lisp/ox-latex.el
This is a very late followup...
Leo Butler, Eric Fraga, and Pedro Andres Aranda Gutierrez previously
expressed an interest in maintaining lisp/ox-latex.el.
If you are still into i
"David O'Toole" writes:
> Ok, I will get started on this :)
Hi,
It has been a while since the last email in this thread.
May I know if you are still interested in taking over the maintenance of
org-info-js?
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at
"Dr. Arne Babenhauserheide" writes:
> I depend on ox-html for my personal website. I would be glad to help.
Arne, sorry for the very late reply.
If you are still willing to help with the maintenance, may you please
submit a patch adding yourself to ;; Maintainer: line in
lisp/ox-html.el?
Bastie
On 2023-08-04, at 22:20, Marcin Borkowski wrote:
> On 2023-08-04, at 10:03, Ihor Radchenko wrote:
>
>> Marcin Borkowski writes:
>>
>>> I have an Elisp form in an Org source block, returning a (multi-line)
>>> string. I'd like to put that string into the same Org buffer. I tried
>>> `:result
Rudolf Adamkovič writes:
> P.S. #1: This is my first contribution to the
> WORG, and I am not sure if the patch is OK.
> I do ever not plan to contribute to the WORG,
> as I am not a fan of the idea and think that
> all built-in backends (and more!) should be
> documented in the Org manual.
See
Hi Ihor,
Ihor Radchenko writes:
> I am not sure.
> We now got exactly the concern Max raised: New commits do not update
> WORG as long as even a single WORG page is broken:
> https://builds.sr.ht/~bzg/job/1035051
Mh, yes, I reverted this change.
> What about the other approach I proposed?
> (w
Mehmet Tekman writes:
> * Under vanilla `org-babel-merge-params', any number of :tangle header
> values are permitted and concatenated together.
>
> e.g 4:
> __
> ´
> (should ;; 4.
> override-document-and-parent-header-with-local-tfile-and-action
> (equal '(:tangle "rand
Hi,
while upgrading from emacs 28.1 to 29.1, my org-agenda stopped working.
The message in the echo area was:
--8<---cut here---start->8---
Search failed: "\\]+\\)>"
--8<---cut here---end--->8---
The search seemed to fai
Bastien Guerry writes:
> Ihor Radchenko writes:
>
>> I am attaching tentative patch that will revert demoting errors to
>> messages. However, I do not fully understand the purpose of the original
>> `condition-case' code in the publish.sh. Bastien?
>
> Applied. I'm aware it only fixes part of t
Juan Manuel Macías writes:
> These last months I have been disconnected from the list for family
> reasons. Now, trying to catch up with the news on the list and pending
> things that I left here :-).
Welcome back :)
> In the meantime, I'm submitting this patch with a fix for second-level
> Fre
41 matches
Mail list logo