Re: [org-save-all-org-buffers] Saving is not reliable?

[Mikhail Skorzhisnkii]

I found the bug. The bug was mostly my own creation. There was a 
small (but very destructive) bug in doom emacs distribution. Fixed 
that bug and sent them a pull requested: 
https://github.com/hlissner/doom-emacs/pull/4424

Basically I made a small snippet for agenda that makes side window 
of agenda staticly sized, really small and includes only very 
small portion of context related to agenda entry. And to correctly 
possition it in frame, I've used wonderful doom emacs popup 
syntax:

 (set-popup-rule! "^*org-agenda-side\*"
   :side 'top
   :size 0.15
   :autosave t
   :quit t)

Turns out :autosave ignores indirect buffers and sets 
buffer-modified-p state to nil. Hope this is the end of my quest, 
My previous solution was also very clunky.

Mikhail Skorzhinskii


Samuel Wales <samologist@gmail.com> writes:

> an undo-boundary bug can make something unexpected get undone as 
> part
> of a batch or make an org operation require two undos.  the 
> agenda is
> one place where these bugs have existed.
>
>
> On 12/9/20, Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
> > On Wednesday,  9 Dec 2020 at 11:16, Mikhail Skorzhisnkii wrote:
> > > It's kind of reproduction scenario. Basically I need to
> > > modify buffer from search-type agenda.
> >
> > In the past, anecdotally I have seen something similar: adjust 
> > the
> > scheduled date for an entry via the agenda view and ask to save 
> > all org
> > buffers.  The change to the scheduled date is sometimes 
> > forgotten.  I
> > haven't tried with emacs -Q so it could, as in Mikhail's case, 
> > be
> > configuration dependent and it's also not entirely reproducible 
> > (i.e. it
> > sometimes happens, sometimes doesn't).
> >
> > But I've not seen this happen recently so maybe it was a bug 
> > along the
> > way.  Sorry for vagueness but I thought I'd chime in just in 
> > case it
> > helps.
> > --
> > : Eric S Fraga via Emacs 28.0.50, Org release_9.4-160-g7c8dce


--
---
Mikhail Skorzhinskii