From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tommy Kelly Subject: Minor gotcha with org-agenda-files Date: Sat, 22 Jan 2011 10:31:52 -0600 Message-ID: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from [140.186.70.92] (port=37983 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1PggNn-00034c-8b for emacs-orgmode@gnu.org; Sat, 22 Jan 2011 11:32:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1PggNi-0007o8-8Y for emacs-orgmode@gnu.org; Sat, 22 Jan 2011 11:32:11 -0500 Received: from lo.gmane.org ([80.91.229.12]:55405) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1PggNh-0007ns-T3 for emacs-orgmode@gnu.org; Sat, 22 Jan 2011 11:32:06 -0500 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1PggNg-0007KY-CW for emacs-orgmode@gnu.org; Sat, 22 Jan 2011 17:32:04 +0100 Received: from cpe-70-112-150-104.austin.res.rr.com ([70.112.150.104]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Jan 2011 17:32:04 +0100 Received: from tommy.kelly by cpe-70-112-150-104.austin.res.rr.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 22 Jan 2011 17:32:04 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org I just figured out why, despite having a setq in my .emacs, my org-agenda-files wasn't what I thought it should be. It's because if you modify that variable using C-c [ or C-c ], then any explicit setq is rendered obsolete by the custom-set-variables entry that gets added automatically. Tell us something we don't know, says y'all, and maybe it's as it should be. But in that case would it be worth adding a note to the relevant part of section 10.1 in the manual? Tommy P.S. The current online section 10.1 says that C-c [ is bound to org-agenda-to-front. In fact it appears to be bound to org-agenda-file-to-front.