From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Visibility cycling of plain lists? Date: Mon, 31 Dec 2012 10:36:24 +0100 Message-ID: <87k3ryo95z.fsf@bzg.ath.cx> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:59358) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TpbnH-0006bX-2q for Emacs-orgmode@gnu.org; Mon, 31 Dec 2012 04:36:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TpbnF-0002hA-U2 for Emacs-orgmode@gnu.org; Mon, 31 Dec 2012 04:36:26 -0500 Received: from mail-wg0-f51.google.com ([74.125.82.51]:61883) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TpbnF-0002h5-N8 for Emacs-orgmode@gnu.org; Mon, 31 Dec 2012 04:36:25 -0500 Received: by mail-wg0-f51.google.com with SMTP id gg4so5580119wgb.6 for ; Mon, 31 Dec 2012 01:36:24 -0800 (PST) In-Reply-To: (James Harkins's message of "Mon, 31 Dec 2012 12:01:54 +0800") 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: jamshark70@dewdrop-world.net Cc: Emacs-orgmode@gnu.org Hi James, James Harkins writes: > http://orgmode.org/manual/Plain-lists.html#Plain-lists > > "For more details, see the variable org-cycle-include-plain-lists. If > this variable is set to integrate, plain list items will be treated > like low-level headlines." > > This confused me, however, because there is no "integrate" option in > org 7.9. There is an option "As children of outline headings." You are confusing the value of the option (which can indeed be 'integrate as a symbol) and the description of this choice in the customize interface. I reread the docstring of this option and I think it's fine. > Also, org-cycle-include-plain-lists's docstring is wrong: "When t, > make TAB cycle visibility on plain list items." Mhh... what is wrong here? > So... never mind the original question (but there are a couple of > documentation issues). Please report them as bugs in separate threads so that we can handle them. Thanks! -- Bastien