From mboxrd@z Thu Jan  1 00:00:00 1970
From: Brian van den Broek <vanden@gmail.com>
Subject: variables governing archiving gone?
Date: Sun, 17 Oct 2010 16:05:33 -0400
Message-ID: <4CBB570D.3050907@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=44120 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1P7ZU9-0003Pk-Ss
	for emacs-orgmode@gnu.org; Sun, 17 Oct 2010 16:05:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <vanden@gmail.com>) id 1P7ZU8-0001XT-Tv
	for emacs-orgmode@gnu.org; Sun, 17 Oct 2010 16:05:37 -0400
Received: from ironport2-out.teksavvy.com ([206.248.154.181]:16207
	helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vanden@gmail.com>) id 1P7ZU8-0001XL-Rd
	for emacs-orgmode@gnu.org; Sun, 17 Oct 2010 16:05:36 -0400
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/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: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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 <emacs-orgmode@gnu.org>

Hi all,

I've been overhauling my use or orgmode and have also started keeping 
current with the git repository. From a pull less than 24hrs ago, the 
documentation refers to the variables:

  - org-archive-default-command
  - org-archive-save-context-info

But neither C-h a nor M-x customize group org-agenda seems to know of 
either variable.

Doc bug, code bug, or user error?

Best,

Brian vdB