From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: Sticky agendas not redone when using org-agenda-(set|remove)-restriction-lock Date: Sun, 18 Jan 2015 11:26:16 +0100 Message-ID: <87fvb8qt9z.fsf@nicolasgoaziou.fr> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54925) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YCn2i-0003bU-88 for emacs-orgmode@gnu.org; Sun, 18 Jan 2015 05:25:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YCn2f-0008Ct-1Q for emacs-orgmode@gnu.org; Sun, 18 Jan 2015 05:25:16 -0500 Received: from relay5-d.mail.gandi.net ([2001:4b98:c:538::197]:37978) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YCn2e-0008Co-R3 for emacs-orgmode@gnu.org; Sun, 18 Jan 2015 05:25:12 -0500 In-Reply-To: (Nikolai Weibull's message of "Sun, 18 Jan 2015 10:55:05 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Nikolai Weibull Cc: emacs-orgmode@gnu.org Hello, Nikolai Weibull writes: > I=E2=80=99m bumping this again, as this feels like a bug and I=E2=80=99m = surprised > that no one has at least responded to it. > > On Wed, Jan 7, 2015 at 6:51 PM, Nikolai Weibull wrote: >> Hi! >> >> Anyone else experiencing this? Or is my configuration wrong in some way? >> >> On Mon, Dec 22, 2014 at 7:10 PM, Nikolai Weibull wrote: >>> Hi! >>> >>> It seems that agendas created when org-agenda-sticky-mode is t aren=E2= =80=99t >>> automatically redone when calling >>> org-agenda-(set|remove)-restriction-lock. The reason is that >>> (org-agenda-maybe-redo) checks whether there=E2=80=99s a window display= ing a >>> buffer named org-agenda-buffer-name. Org-agenda-buffer-name is, for >>> some reason, not set to the (buffer-name) for these sticky agendas >>> (which get the key that was selected as a suffix, for example, =E2=80= =9C*Org >>> Agenda(p)*=E2=80=9D). >>> >>> I don=E2=80=99t know whether there=E2=80=99s a reason for this, but it = seems like it=E2=80=99s >>> a bug. Either org-agenda-buffer-name isn=E2=80=99t being set correctly= or >>> (org-agenda-maybe-redo) should be using (buffer-name) instead of >>> org-agenda-buffer-name. >>> >>> If there=E2=80=99s a reason for this, I=E2=80=99d really like to know w= hat it is, so >>> that I can begin to try to remember to press g whenever I=E2=80=99ve up= dated >>> the restriction lock. According to the manual By default, Org maintains only a single agenda buffer and rebuilds it each time you change the view, to make sure everything is always up to date. If you often switch between agenda views and the build time bothers you, you can turn on sticky agenda buffers or make this the default by customizing the variable =E2=80=98org-agenda-stick= y=E2=80=99. With sticky agendas, the agenda dispatcher will not recreate agenda views from scratch, it will only switch to the selected one, and you need to update the agenda by hand with =E2=80=98r=E2=80=99 or =E2= =80=98g=E2=80=99 when needed. You can toggle sticky agenda view any time with =E2=80=98org-toggle-sticky-agenda=E2=80=99. So the whole point of sticky agenda is that you need to update it manually. Regards, --=20 Nicolas Goaziou