From: Nikolai Weibull <now@disu.se>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Sticky agendas not redone when using org-agenda-(set|remove)-restriction-lock
Date: Thu, 20 Aug 2015 20:31:53 +0200 [thread overview]
Message-ID: <CADdV=Ms0oABCuJut23zKaVjAYNo7bAd0TEQ659H_8Fq-pwoq9w@mail.gmail.com> (raw)
In-Reply-To: <874mjtri37.fsf@free.fr>
I am so disappointed with everything that has to do with e-mail right
now. For some reason the e-mail isn’t being delivered. I assume it’s
not being accepted by the mailing list, but I can’t see why. I’m not
getting any error message.
Anyway, here’s the relevant part (and let’s see if this e-mail gets through):
* org-agenda.el (org-agenda-maybe-redo): Test for
org-agenda-this-buffer-name as well.
The Agenda buffer will have a different name if it’s in sticky mode,
but some commands that alter the agenda should still redo it, for
example, org-agenda-remove-restriction-lock, just like
org-agenda-filter-by-category does.
---
lisp/org-agenda.el | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/lisp/org-agenda.el b/lisp/org-agenda.el
index 07b77ac..5fd1cd4 100644
--- a/lisp/org-agenda.el
+++ b/lisp/org-agenda.el
@@ -7169,7 +7169,9 @@ in the file. Otherwise, restriction will be to
the current subtree."
(defun org-agenda-maybe-redo ()
"If there is any window showing the agenda view, update it."
- (let ((w (get-buffer-window org-agenda-buffer-name t))
+ (let ((w (get-buffer-window (or org-agenda-this-buffer-name
+ org-agenda-buffer-name)
+ t))
(w0 (selected-window)))
(when w
(select-window w)
--
2.5.0
On Thu, Aug 20, 2015 at 7:21 PM, Bastien <bzg@gnu.org> wrote:
> Hi Nikolai,
>
>> Here’s the patch again, as I don’t think the one I sent yesterday got
>> through. My FSF papers are signed, by the way.
>
> It looks like you forgot to attach the patch...
>
> --
> Bastien
next prev parent reply other threads:[~2015-08-20 18:31 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
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 [this message]
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=Ms0oABCuJut23zKaVjAYNo7bAd0TEQ659H_8Fq-pwoq9w@mail.gmail.com' \
--to=now@disu.se \
--cc=bzg@gnu.org \
--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).