emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Subhan Michael Tindall <SubhanT@familycareinc.org>
To: "'emacs-orgmode@gnu.org'" <emacs-orgmode@gnu.org>
Subject: Possible bug
Date: Tue, 10 Mar 2015 16:24:54 +0000	[thread overview]
Message-ID: <931fda3be08d4908bfbced55e9a9c170@fcmailsvr2.familycareinc.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]

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*")
*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.

I've poked around a bit in the code, but my elisp-fu is quite weak. I couldn't find an easy way to pass a buffer name in to org-agenda to be used, nor was it entirely clear to me how to modify org-agenda to grab & respect the buffer name when rebuilding a 'sticky' one.





This message is intended for the sole use of the individual and entity to which it is addressed and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the intended addressee, nor authorized to receive for the intended addressee, you are hereby notified that you may not use, copy, disclose or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete the message.  Thank you.

[-- Attachment #2: Type: text/html, Size: 3802 bytes --]

next             reply	other threads:[~2015-03-10 16:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 16:24 Subhan Michael Tindall [this message]
2015-03-10 20:32 ` Possible bug Nicolas Goaziou
  -- 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=931fda3be08d4908bfbced55e9a9c170@fcmailsvr2.familycareinc.org \
    --to=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

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).