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-subtree to just
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
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
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 refe
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 from a prev
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
>
> 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
