From: Henrik Frisk <frisk.h@gmail.com>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Tim Cross <theophilusx@gmail.com>,
org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: Build agenda asynchronously
Date: Wed, 18 Aug 2021 07:41:11 +0200 [thread overview]
Message-ID: <CAO0LSb61ee4EykeXp61AK_S_TN8WUjwPoQkHhDtk0h_U+UDzbA@mail.gmail.com> (raw)
In-Reply-To: <87v944v9ys.fsf@web.de>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Den tis 17 aug. 2021 kl 08:54 skrev Dr. Arne Babenhauserheide <
arne_bab@web.de>:
>
> Tim Cross <theophilusx@gmail.com> writes:
>
> > Emacs' support for asynchronous operations is at best primitive. There
> > is built-in support for calling processes asynchonously and
> > there is some other development work to set the stage for adding threads,
> > but I think general asynchronous processing inside Emacs is a long way
> > off. A lot of how Emacs lisp works fundamentally lacks the low level
> > control structures necessary to make data structures and operations on
> > those structures thread safe. This means you have to work at a very low
> > level in order to ensure code is thread safe and that simply isn't
> > practical. Even defining the basic model for an asynchronous emacs lisp
> > is non-trivial and once you have the model, you ahve to implement it.
>
> Maybe it could be possible to fire up a second Emacs and retrieve the
> agenda-buffer?
>
> This is what I do for commands like exporting the agenda which can take a
while with the -nw flag, but that is of course unsatisfactory for most use
cases.
/Henrik
[-- Attachment #2: Type: text/html, Size: 1573 bytes --]
next prev parent reply other threads:[~2021-08-18 5:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 22:52 Build agenda asynchronously dalanicolai
2021-08-16 23:59 ` Tim Cross
2021-08-17 6:52 ` Dr. Arne Babenhauserheide
2021-08-17 7:28 ` Tim Cross
2021-08-17 18:10 ` Milan Zamazal
2021-08-18 0:13 ` Tim Cross
2021-08-18 5:47 ` Henrik Frisk
2021-08-18 5:41 ` Henrik Frisk [this message]
2021-08-18 15:28 ` 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=CAO0LSb61ee4EykeXp61AK_S_TN8WUjwPoQkHhDtk0h_U+UDzbA@mail.gmail.com \
--to=frisk.h@gmail.com \
--cc=arne_bab@web.de \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).