From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Subhan Michael Tindall <SubhanT@familycareinc.org>
Cc: "'emacs-orgmode@gnu.org'" <emacs-orgmode@gnu.org>
Subject: Re: Possible bug
Date: Tue, 10 Mar 2015 21:32:32 +0100 [thread overview]
Message-ID: <87twxs1tlr.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <931fda3be08d4908bfbced55e9a9c170@fcmailsvr2.familycareinc.org> (Subhan Michael Tindall's message of "Tue, 10 Mar 2015 16:24:54 +0000")
Hello,
Subhan Michael Tindall <SubhanT@familycareinc.org> writes:
> I'm not sure if this counts as a bug or not:
>
> If I run a custom agenda (eg. "R") with sticky agendas, it displays in an buffer with the name
> *Org Agenda (R)*
> If this buffer is then renamed to e.g.
> (rename-buffer "*R-Agenda*")
Why would you need that?
> *R-Agenda*
> And is then refreshed by hitting r, the agenda is properly rebuilt BUT in a new buffer named *Org Agenda(R)*, resulting in two differing agendas.
>
> Is this appropriate behavior? It seems that rebuilding the agenda
> should respect the current buffer name. I'm very new at programing for
> lisp, so I'm not sure I'm using the right functions here.
IIRC, sticky agenda relies on buffer names to know if agenda needs to be
updated. So, it is not a good idea to rename agenda buffers.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-03-10 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 16:24 Possible bug Subhan Michael Tindall
2015-03-10 20:32 ` Nicolas Goaziou [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-16 17:45 possible bug Pete Phillips
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=87twxs1tlr.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=SubhanT@familycareinc.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).