From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kyle Meyer Subject: Re: Org Agenda Mode Line Date: Fri, 30 Jan 2015 12:33:02 -0500 Message-ID: <87vbjocgxd.fsf@kyleam.com> References: <87egqcqv8u.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34983) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHFRO-0008Co-RN for emacs-orgmode@gnu.org; Fri, 30 Jan 2015 12:33:11 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YHFRJ-0000u0-T0 for emacs-orgmode@gnu.org; Fri, 30 Jan 2015 12:33:10 -0500 Received: from mail-qc0-f180.google.com ([209.85.216.180]:37327) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YHFRJ-0000ts-Q1 for emacs-orgmode@gnu.org; Fri, 30 Jan 2015 12:33:05 -0500 Received: by mail-qc0-f180.google.com with SMTP id r5so21475522qcx.11 for ; Fri, 30 Jan 2015 09:33:05 -0800 (PST) In-Reply-To: <87egqcqv8u.fsf@gmail.com> (Tory S. Anderson's message of "Fri, 30 Jan 2015 08:00:01 -0500") 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: "Tory S. Anderson" Cc: orgmode list torys.anderson@gmail.com (Tory S. Anderson) wrote: > Suddenly I see my org agenda mode line has, as the buffer name, > *Org Agenda(a:2015-01-24) > > I've tried closing and restarting agenda but it persists. What does > this mean? That looks like a buffer name generated when org-agenda-sticky is non-nil. The text in parentheses tells you how the command was invoked. For example, "*Org Agenda(s:term)*" means that after calling org-agenda, you pressed 's' and searched for 'term'. In your case, you used the 'a' key, but I'm uncertain of how the '2015-01-24' was generated. How are you trying to close the buffer? With a sticky agenda, 'q' will just bury the buffer. You need to press 'Q' or call kill-buffer directly to actually kill it. -- Kyle