From: Nikolai Weibull <now@disu.se>
To: Nikolai Weibull <now@disu.se>, emacs-orgmode@gnu.org
Subject: Re: Sticky agendas not redone when using org-agenda-(set|remove)-restriction-lock
Date: Sun, 18 Jan 2015 14:27:41 +0100 [thread overview]
Message-ID: <CADdV=Mt+sKE-1aVasrjZBWS66UY23y4q0RzQMY9gnaQU7gRRLQ@mail.gmail.com> (raw)
In-Reply-To: <87fvb8qt9z.fsf@nicolasgoaziou.fr>
On Sun, Jan 18, 2015 at 11:26 AM, Nicolas Goaziou
<mail@nicolasgoaziou.fr> wrote:
> Nikolai Weibull <now@disu.se> writes:
>
>> I’m bumping this again, as this feels like a bug and I’m surprised
>> that no one has at least responded to it.
>>
>> On Wed, Jan 7, 2015 at 6:51 PM, Nikolai Weibull <now@disu.se> 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 <now@disu.se> wrote:
>>>> Hi!
>>>>
>>>> It seems that agendas created when org-agenda-sticky-mode is t aren’t
>>>> automatically redone when calling
>>>> org-agenda-(set|remove)-restriction-lock. The reason is that
>>>> (org-agenda-maybe-redo) checks whether there’s 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, “*Org
>>>> Agenda(p)*”).
>>>>
>>>> I don’t know whether there’s a reason for this, but it seems like it’s
>>>> a bug. Either org-agenda-buffer-name isn’t being set correctly or
>>>> (org-agenda-maybe-redo) should be using (buffer-name) instead of
>>>> org-agenda-buffer-name.
>>>>
>>>> If there’s a reason for this, I’d really like to know what it is, so
>>>> that I can begin to try to remember to press g whenever I’ve updated
>>>> the restriction lock.
>
> According to the manual
I realize that you have to update it manually, but wouldn’t it make
sense to have it be updated automatically when you call
org-agenda-(set|remove)-restriction-lock? At least when you do so
from the Agenda itself?
next prev parent reply other threads:[~2015-01-18 13:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 18:10 Sticky agendas not redone when using org-agenda-(set|remove)-restriction-lock Nikolai Weibull
2015-01-07 17:51 ` Nikolai Weibull
2015-01-18 9:55 ` Nikolai Weibull
2015-01-18 10:26 ` Nicolas Goaziou
2015-01-18 13:27 ` Nikolai Weibull [this message]
2015-01-18 22:39 ` Nicolas Goaziou
2015-01-19 9:33 ` Nikolai Weibull
2015-01-19 17:38 ` Nicolas Goaziou
2015-02-15 21:54 ` Nikolai Weibull
2015-02-16 9:05 ` Nicolas Goaziou
2015-08-19 23:37 ` Nikolai Weibull
2015-08-20 17:02 ` Nikolai Weibull
2015-08-20 17:02 ` [PATCH 1/2] Redo Agenda in more cases even in sticky mode Nikolai Weibull
2015-08-20 17:21 ` Sticky agendas not redone when using org-agenda-(set|remove)-restriction-lock Bastien
2015-08-20 18:31 ` Nikolai Weibull
2015-08-23 7:56 ` Nicolas Goaziou
2015-08-20 18:22 ` [PATCH 1/2] Redo Agenda in more cases even in sticky mode Nikolai Weibull
2015-08-20 18:25 ` Nikolai Weibull
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='CADdV=Mt+sKE-1aVasrjZBWS66UY23y4q0RzQMY9gnaQU7gRRLQ@mail.gmail.com' \
--to=now@disu.se \
--cc=emacs-orgmode@gnu.org \
/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).