Hi,
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 :-).
In the meantime, I'm submitting this patch with a fix for second-level
French `smart quotes': the correct quotes should be “”
Hi folks,
It seems there is a bad interaction between org-add-log-setup and
org-with-remote-undo, such that org-agenda-undo does not function
correctly. For example,
1. Enable logging on reschedule, by setting `org-log-reschedule' to
`time'.
2. Reschedule an already-scheduled TODO item throug
Pre-weekend update: I have a `merge-params' solution, and it's passing tests.
I will need to refactor/cherry pick my branch somehow to make the patch
less "tangle sync"-centric, but I'm sure I can make it work.
On Thu, 3 Aug 2023 at 10:46, Mehmet Tekman wrote:
>
> > You dropped mailing list from
"Aaron Zeng" writes:
> I wonder if org-add-log-setup should be removed and refactored away,
> or if org-with-remote-undo should not be creating an undo boundary
> (which sounds redundant with the automatic ones created by the command
> loop?).
`org-add-log-setup' is indeed causing a lot of probl
Hi Orgers,
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
`:results raw', but the string contains `|' characters, so Org treats
its as a table and tries to format it as such, which is not what I want.
H
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
> `:results raw', but the string contains `|' characters, so Org treats
> its as a table and tries to format it as such, which
Rudolf Adamkovič writes:
> Ihor Radchenko writes:
>
>> As Max described, it might be a potential issue.
>
> How about (1) we merge the patch, and then
> (2) we add the lint warning if/when someone
> has the [hypothesized] problem?
Maybe. After re-thinking, your change should not break any exist
Mehmet Tekman writes:
> Pre-weekend update: I have a `merge-params' solution, and it's passing tests.
Side note: I had one newly added test failing on the latest main. You
may need to rebase your branch and check if tests are still passing.
> I will need to refactor/cherry pick my branch someho
"Christopher M. Miles" writes:
>> I think that instead of changing the existing function, we can convert
>> your patch into a new function `org-toggle-inline-images-command' that
>> will be free to alter the argument order. We can then re-bind that
>> function in org-keys to make it used by defau
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 the issue at hand, but I
believe th
Hi Juan,
Juan Manuel Macías writes:
> 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...).
Applied, thanks!
--
Basti
Ihor Radchenko writes:
>
> Side note: I had one newly added test failing on the latest main. You
> may need to rebase your branch and check if tests are still passing.
>
The rebase was fine, but I'm having a problem aligning my patch branch
to work without any tangle involvement.
The first hurd
I'm on main (Org mode version 9.7-pre (release_9.6.7-594-gf03b83), and it's
not fixed. Am I missing something?
Am Do., 1. Juni 2023 um 13:33 Uhr schrieb Ihor Radchenko <
yanta...@posteo.net>:
> Michael Dauer writes:
>
> > I think I found a way to consistently reproduce the issue:
> > ...
>
> Tha
Michael Dauer writes:
> I'm on main (Org mode version 9.7-pre (release_9.6.7-594-gf03b83), and it's
> not fixed. Am I missing something?
If I try to follow the recipe described in
https://list.orgmode.org/orgmode/CAP7OBx+L11ck3Ni6rv94HGU3otdj6C4rG-rMDzkwR1LTj=b...@mail.gmail.com/
using the lates
On 4 August 2023, Michael Dauer wrote:
I'm on main (Org mode version 9.7-pre (release_9.6.7-594-gf03b83), and it's
not fixed. Am I missing something?
The fix did fix it for me, and the problem went away. It did seem to introduce
a new problem with searching in a buffer with Swiper, where the
Ignore the patches in that last email, (but please do address some of
the concerns I had about the number of `:any` outputs).
Anyway, I finally did it - I got it to work. Every single patch now
pasts tests.
Please review these patches and *not the patches in the last email*.
(Apologies for the fr
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
>> `:results raw', but the string contains `|' characters, so Org trea
Ihor Radchenko writes:
> However, I think that it will provide more freedom to users if you alter
> org-babel-default-header-args:sqlite instead of hard-coding the default.
> May you update the patch accordingly?
Please see the attached patch.
> Also, can you update the docs at
> https://orgmod
On 05/08/2023 05:57, Rudolf Adamkovič wrote:
+*** Make ~ob-sqlite~ use in-database by default
"use in-memory database"
+
+SQLite source blocks with no ~:db~ argument now execute against a
+transient in-memory database by default.
I am unsure, but perhaps it would be more clear to say that t
On 05/08/2023 05:57, Rudolf Adamkovič wrote:
P.S. #2: The Table of Contents (TOC) on the
WORG is "jumpy" on Safari. In fact, it has
always been problematic for me, in one way or
another. Why cannot TOC be included at the
beginning of the document, like in standard
Org exports? Org and Emacs ma
fwiw i agree with the non-fancy toc concept for accessibility.
On 8/4/23, Max Nikulin wrote:
> On 05/08/2023 05:57, Rudolf Adamkovič wrote:
>> P.S. #2: The Table of Contents (TOC) on the
>> WORG is "jumpy" on Safari. In fact, it has
>> always been problematic for me, in one way or
>> another. W
[i.e. agree that the manuals and standard toc at top imo do a good job
for accessibility.]
On 8/4/23, Samuel Wales wrote:
> fwiw i agree with the non-fancy toc concept for accessibility.
>
> On 8/4/23, Max Nikulin wrote:
>> On 05/08/2023 05:57, Rudolf Adamkovič wrote:
>>> P.S. #2: The Table of C
* 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 to use
`file-relative-name` for the s
23 matches
Mail list logo
