emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Mikhail Skorzhisnkii <mskorzhinskiy@eml.cc>
To: emacs-orgmode@gnu.org
Subject: Re: [org-save-all-org-buffers] Saving is not reliable?
Date: Sun, 13 Dec 2020 16:08:55 +0100	[thread overview]
Message-ID: <871rft920o.fsf@eml.cc> (raw)
In-Reply-To: <CAJcAo8teBOS0f2nohz7X-JSUhZq6t-zdiEzicjPXbGmvesbXhQ@mail.gmail.com>

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: 

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 

  (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

      reply	other threads:[~2020-12-13 15:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 16:22 [org-save-all-org-buffers] Saving is not reliable? Mikhail Skorzhisnkii
2020-12-09  6:16 ` Kyle Meyer
2020-12-09 10:16   ` Mikhail Skorzhisnkii
2020-12-09 10:30     ` Eric S Fraga
2020-12-12 23:50       ` Samuel Wales
2020-12-13 15:08         ` Mikhail Skorzhisnkii [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871rft920o.fsf@eml.cc \
    --to=mskorzhinskiy@eml.cc \
    --cc=emacs-orgmode@gnu.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).