From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nikolai Weibull <now@disu.se>
Subject: Sticky agendas not redone when using
 org-agenda-(set|remove)-restriction-lock
Date: Mon, 22 Dec 2014 19:10:08 +0100
Message-ID: <CADdV=MsyaTLnKSkF7mKfbxmdxX5f8ewLZLvFCGCCSFjHezOb=A@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:37533)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nikolai.weibull@gmail.com>) id 1Y37Qr-00029K-Ht
	for emacs-orgmode@gnu.org; Mon, 22 Dec 2014 13:10:14 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <nikolai.weibull@gmail.com>) id 1Y37Qo-0006r0-EN
	for emacs-orgmode@gnu.org; Mon, 22 Dec 2014 13:10:13 -0500
Received: from mail-wg0-x22a.google.com ([2a00:1450:400c:c00::22a]:46312)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <nikolai.weibull@gmail.com>) id 1Y37Qo-0006qm-8Y
	for emacs-orgmode@gnu.org; Mon, 22 Dec 2014 13:10:10 -0500
Received: by mail-wg0-f42.google.com with SMTP id k14so7354169wgh.29
	for <emacs-orgmode@gnu.org>; Mon, 22 Dec 2014 10:10:09 -0800 (PST)
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: emacs-orgmode@gnu.org

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 displaying =
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*Or=
g
Agenda(p)*=E2=80=9D).

I don=E2=80=99t know whether there=E2=80=99s a reason for this, but it seem=
s 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 what =
it is, so
that I can begin to try to remember to press g whenever I=E2=80=99ve update=
d
the restriction lock.

Thanks!