From mboxrd@z Thu Jan 1 00:00:00 1970 From: Subhan Michael Tindall Subject: Possible bug Date: Tue, 10 Mar 2015 16:24:54 +0000 Message-ID: <931fda3be08d4908bfbced55e9a9c170@fcmailsvr2.familycareinc.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="_000_931fda3be08d4908bfbced55e9a9c170fcmailsvr2familycareinc_" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34648) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YVMxq-0005aF-5I for emacs-orgmode@gnu.org; Tue, 10 Mar 2015 12:25:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YVMxm-0004qE-N3 for emacs-orgmode@gnu.org; Tue, 10 Mar 2015 12:25:02 -0400 Received: from outbound.familycareinc.org ([207.170.205.147]:60887) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YVMxm-0004pu-Ct for emacs-orgmode@gnu.org; Tue, 10 Mar 2015 12:24:58 -0400 Content-Language: en-US List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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'" --_000_931fda3be08d4908bfbced55e9a9c170fcmailsvr2familycareinc_ Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable 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 b= uffer 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 re= spect 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 could= n'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 w= hich it is addressed and may contain information that is privileged, confid= ential and exempt from disclosure under applicable law. If you are not the = intended addressee, nor authorized to receive for the intended addressee, y= ou are hereby notified that you may not use, copy, disclose or distribute t= o anyone the message or any information contained in the message. If you ha= ve received this message in error, please immediately advise the sender by = reply email and delete the message. Thank you. --_000_931fda3be08d4908bfbced55e9a9c170fcmailsvr2familycareinc_ Content-Type: text/html; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable

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*”)<= /p>

*R-Agenda*

And is then refreshed by hitting r, the agenda is pr= operly rebuilt BUT in a new buffer named *Org Agenda(R)*, resulting = in two differing agendas.

 

Is this appropriate behavior? It seems that rebuildi= ng 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 funct= ions here.

 

I’ve poked around a bit in the code, but my el= isp-fu is quite weak. I couldn’t find an easy way to pass a buffer na= me in to org-agenda to be used, nor was it entirely clear to me how to modi= fy 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, co= nfidential and exempt from disclosure under applicable law. If you are not = the intended addressee, nor authorized to receive for the intended addresse= e, you are hereby notified that you may not use, copy, disclose or distribu= te to anyone the message or any information contained in the message. If yo= u have received this message in error, please immediately advise the sender= by reply email and delete the message.  Thank you. --_000_931fda3be08d4908bfbced55e9a9c170fcmailsvr2familycareinc_--