[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Asynchronous org-agenda-redo
From: |
Adam Porter |
Subject: |
Re: Asynchronous org-agenda-redo |
Date: |
Mon, 23 Dec 2019 18:36:09 -0600 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) |
Ihor Radchenko <address@hidden> writes:
> If you accidentally move the point in the buffer being processed by
> agenda, the results may be unpredictable (org-agenda-get-* functions
> move across the buffer with re-search-forward).
I'm afraid that's the basic problem with threading in Emacs: shared
state. I don't know of a way to work around that. I suppose you could
modify a lot of the agenda code to, e.g. store the position of the
current search in a variable and go to it before each search. Of
course, that would also reduce performance to some extent. It's a hard
problem.
- Asynchronous org-agenda-redo, Ihor Radchenko, 2019/12/12
- Re: Asynchronous org-agenda-redo, Adam Porter, 2019/12/12
- Re: Asynchronous org-agenda-redo, Ihor Radchenko, 2019/12/12
- Re: Asynchronous org-agenda-redo, Adam Porter, 2019/12/13
- Re: Asynchronous org-agenda-redo, Ihor Radchenko, 2019/12/13
- Re: Asynchronous org-agenda-redo, Ihor Radchenko, 2019/12/13
- Re: Asynchronous org-agenda-redo, Adam Porter, 2019/12/13
- Re: Asynchronous org-agenda-redo, Ihor Radchenko, 2019/12/22
- Re: Asynchronous org-agenda-redo,
Adam Porter <=
- Re: Asynchronous org-agenda-redo, Adam Porter, 2019/12/13
- Re: Asynchronous org-agenda-redo, Ihor Radchenko, 2019/12/16
- Re: Asynchronous org-agenda-redo, Adam Porter, 2019/12/16
- Re: Asynchronous org-agenda-redo, Diego Zamboni, 2019/12/12