Skip Collins writes:
> On Wed, Apr 27, 2022 at 4:48 AM Ihor Radchenko wrote:
>> Fixed in 2d6f26c05 on main. And no, it was not that easy to fix.
>> Captured headlines may or may not need to be unfolded.
>
> Thanks. I confirm that behavior is correct for folded level 1
> headlines. But the
On Wed, Apr 27, 2022 at 4:48 AM Ihor Radchenko wrote:
> Fixed in 2d6f26c05 on main. And no, it was not that easy to fix.
> Captured headlines may or may not need to be unfolded.
Thanks. I confirm that behavior is correct for folded level 1
headlines. But the problem still exists at level 2 and
Skip Collins writes:
> I think this is a real bug. Am I wrong? Seems like it should be easy to fix.
Fixed in 2d6f26c05 on main. And no, it was not that easy to fix.
Captured headlines may or may not need to be unfolded.
Best,
Ihor
I think this is a real bug. Am I wrong? Seems like it should be easy to fix.
On Mon, Apr 4, 2022 at 11:25 AM Skip wrote:
> On Fri, Apr 1, 2022 at 3:46 PM Skip wrote:
> > Another manifestation of the problem shows up when using
> > auto-revert-mode. Starting with the single headline in a folded
On Fri, Apr 1, 2022 at 3:46 PM Skip wrote:
> Another manifestation of the problem shows up when using
> auto-revert-mode. Starting with the single headline in a folded state
> as above, when I execute the following command in a shell,
> echo "* TODO bar :action:" >>capture.org
> then the
I think there is a bug in updating an org buffer window after capture
appends an entry. When the previously final entry, terminated with a
newline, is folded, the newly captured entry that is appended does not
show correctly in the buffer. Here is an example capture template:
("a" "Actions" entry
