emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Diego Zamboni <diego@zzamboni.org>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Asynchronous org-agenda-redo
Date: Thu, 12 Dec 2019 13:51:34 +0100	[thread overview]
Message-ID: <CAGY83EfU6OfJQDTKCRJxGCXW1N0WJ9GDR45qjN6=8UTjZVBAmw@mail.gmail.com> (raw)
In-Reply-To: <87k172ot2m.fsf@yantar92-laptop.i-did-not-set--mail-host-address--so-tickle-me>

[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]

Hi Ihor,

I cannot answer your question, but I am curious about using async together
with tangling, since for some of my buffers, tangling takes some time and
freezes Emacs in the process. Do you have some examples of this that you
could share?


On Thu, Dec 12, 2019 at 9:21 AM Ihor Radchenko <yantar92@gmail.com> wrote:

> I am thinking if it is possible to implement org-agenda-redo
> asynchronously.
> Rebuilding agenda should normally not affect any buffer except agenda
> buffer. So, it should be sufficient to block any agenda modifying
> commands in the agenda buffer, redo the agenda buffer in separate
> thread, and replace the old agenda with the calculated one.
> Then, emacs should remain responsive while updating agenda (except for
> modifying the agenda buffer).
> For example, this naive code kind of works (forgetting that buffer-local
> variables will not be passed to the thread):
> (define-advice org-agenda-redo (:around (oldfun &optional all) make-async)
>   (make-thread oldfun "org-agenda-redo"))
> The problem is that emacs does not become responsive...
> Another approach would be using async.el package, which allows calling
> arbitrary function in subordinate emacs process. Then, the main emacs
> instance should not be "frozen" (I use same approach for tangling and it
> works fine).
> However, the question is how to pass the .org and agenda buffers to this
> subordinate process. Opening the .org files there is not a good option
> since it would give too much overhead to this asynchronous agenda.
> Any suggestions? Alternative ideas?
> Best,
> Ihor

[-- Attachment #2: Type: text/html, Size: 2109 bytes --]

  parent reply	other threads:[~2019-12-12 12:51 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-12  8:18 Asynchronous org-agenda-redo Ihor Radchenko
2019-12-12 12:17 ` Adam Porter
2019-12-12 15:46   ` Ihor Radchenko
2019-12-13  6:49     ` Adam Porter
2019-12-13  8:35       ` Ihor Radchenko
2019-12-13  9:39         ` Ihor Radchenko
2019-12-14  4:59           ` Adam Porter
2019-12-22  6:54             ` Ihor Radchenko
2019-12-24  0:36               ` Adam Porter
2019-12-14  4:50         ` Adam Porter
2019-12-16  7:23           ` Ihor Radchenko
2019-12-16 10:32             ` Adam Porter
2019-12-12 12:51 ` Diego Zamboni [this message]
2019-12-12 14:58   ` Ihor Radchenko
2019-12-15 11:56     ` Asynchronous org-babel-tangle (was Re: Asynchronous org-agenda-redo) Diego Zamboni
2019-12-15 13:40       ` Ihor Radchenko
2019-12-15 13:41       ` Ihor Radchenko

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='CAGY83EfU6OfJQDTKCRJxGCXW1N0WJ9GDR45qjN6=8UTjZVBAmw@mail.gmail.com' \
    --to=diego@zzamboni.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \


* 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).