From mboxrd@z Thu Jan  1 00:00:00 1970
From: Max Mikhanosha <max@openchat.com>
Subject: Re: Sticky Agenda buffer: Announcement and request for testing
Date: Wed, 14 Mar 2012 14:12:36 -0400
Message-ID: <87vcm7dpbf.wl%max@openchat.com>
References: <65860CF1-3D9B-497B-8EF7-AA7E87B28BEE@uva.nl>
	<4F60BF29.4060206@online.de>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([208.118.235.92]:38716)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <max@openchat.com>) id 1S7sgl-0002Hc-UG
	for emacs-orgmode@gnu.org; Wed, 14 Mar 2012 14:12:48 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <max@openchat.com>) id 1S7sgh-0007aK-3D
	for emacs-orgmode@gnu.org; Wed, 14 Mar 2012 14:12:43 -0400
Received: from openchat.com ([75.99.81.170]:39211 helo=momoland.openchat.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <max@openchat.com>) id 1S7sgg-0007Zj-W3
	for emacs-orgmode@gnu.org; Wed, 14 Mar 2012 14:12:39 -0400
In-Reply-To: <4F60BF29.4060206@online.de>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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
Cc: Rainer Stengele <rainer.stengele@online.de>

At Wed, 14 Mar 2012 16:54:17 +0100,
Rainer Stengele wrote:
> 
> I have a few functions based on the org-agenda-buffer-name, which now is no more available,
> as all the agenda buffers are named differently:
> 
> ..
>   (if (get-buffer org-agenda-buffer-name)
> ..
> will no more work.

If you don't turn sticky on, then the name of the agenda will stay the
same as before, it only generates unique names if sticky is enabled.

>
> I hope that the current agenda buffer names pattern will stay as it is.
> I will have to hardcode the changed buffer names.

The method of generating default sticky agenda buffer names by adding
keys used to invoke it will not change.

You can also override it by using `org-agenda-custom-commands', if you
specify `org-agenda-buffer-name' as one of the variables being
overridden for a specific command, that name will take precedence over
the automatic method.

Regards,
  Max