Re: [PATCH] org-list.el: Reduce scope to subtree

2023-09-26 Thread J. G.
ng 3" have their counter cookies set to [0/0] which is not the desired behavior. On Tuesday, September 26, 2023 at 02:33:52 AM PDT, Ihor Radchenko wrote: "J. G." writes: > Hi, this patch reduces the scope of the function  > org-reset-checkbox-state-

[PATCH] org-list.el: Reduce scope to subtree

2023-09-24 Thread J. G.
Hi, this patch reduces the scope of the function  org-reset-checkbox-state-subtree to just the subtree per its name and documentation.From f7b0e67935f7677fe2c238a17bf4f70ac962ab08 Mon Sep 17 00:00:00 2001 From: JG Date: Sun, 24 Sep 2023 16:17:45 -0700 Subject: [PATCH] org-list.el: Reduce scope to

org-bibtex-yank failing with error Wrong type argument: stringp, nil

2023-08-12 Thread J. G.
Hi, I'm trying to figure out why I'm getting consistent failures using org-bibtex-yank. This appears to be identical to the problem posted here: https://stackoverflow.com/questions/31174281/org-bibtex-yank-fails-with-wrong-type-argument-stringp-nil On my system I am using a fresh Ubuntu 23.04 VM

Re: org-bibtex-yank failing with error Wrong type argument: stringp, nil

2023-08-12 Thread J. G.
On Friday, August 11, 2023 at 09:34:31 AM PDT, J. G. wrote: > Hi, I'm trying to figure out why I'm getting consistent failures using > org-bibtex-yank. This appears to be identical to the problem posted here: On further investigation I have pinpointed the precise error as re

Re: [BUG] Linking SCHEDULED and DEADLINE repeating timestamps to avoid desynchronization

2023-04-27 Thread J. G.
Radchenko wrote: "J. G." writes: > * TODO My late recurring todoSCHEDULED: <2023-04-12 Wed ++1w> DEADLINE: > <2023-04-13 Thu ++1w> > Right now it is Wednesday (2023-04-26 to be precise), and as shown above, my > task had a scheduled timestamp on a Wednesday f

Linking SCHEDULED and DEADLINE repeating timestamps to avoid desynchronization

2023-04-26 Thread J. G.
Hi everyone, I just stumbled across a surprising behavior with combined SCHEDULED and DEADLINE timestamps that repeat. Here is the example org file contents: * TODO My late recurring todoSCHEDULED: <2023-04-12 Wed ++1w> DEADLINE: <2023-04-13 Thu ++1w> Right now it is Wednesday (2023-04-26 to be

Possible error in manual

2023-01-07 Thread J G
> > 2.2.3 Catching invisible edits > > Sometimes you may inadvertently edit an invisible part of the buffer and > be confused on what has been edited and how to undo the mistake. Setting > org-fold-catch-invisible-edits to non-nil helps preventing this. See the > docstring of this option on how Org