From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: bug in the :VISIBILITY: handling of nested "folded" properties? Date: Sat, 7 Aug 2010 09:28:22 +0200 Message-ID: <1B523266-BAD0-47CB-BB78-6690B1CE9200@gmail.com> References: Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from [140.186.70.92] (port=37665 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Oi9jn-0006lr-PY for emacs-orgmode@gnu.org; Sun, 08 Aug 2010 13:32:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OhdpS-0006J8-Rz for emacs-orgmode@gnu.org; Sat, 07 Aug 2010 03:28:27 -0400 Received: from mail-ew0-f41.google.com ([209.85.215.41]:47767) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OhdpS-0006Iy-Kr for emacs-orgmode@gnu.org; Sat, 07 Aug 2010 03:28:26 -0400 Received: by ewy28 with SMTP id 28so3337941ewy.0 for ; Sat, 07 Aug 2010 00:28:25 -0700 (PDT) In-Reply-To: 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: Rainer Stengele Cc: emacs-orgmode@gnu.org On Jul 30, 2010, at 1:08 PM, Rainer Stengele wrote: > Having > > * headline 1 > :PROPERTIES: > :VISIBILITY: folded > :END: > ** headline 2.1 > - stuff > ** headline 2.1 > :PROPERTIES: > :VISIBILITY: folded > :END: > - stuff > > C-u C-u > Switch back to the startup visibility of the buffer, i.e. =20 > whatever is requested by startup options and =91VISIBILITY=92 = properties =20 > in individual entries. > > > does not result in > > > * headline 1...> > > > as expected. Instead I get: > > > * headline 1...> > ** headline 2.1...> > ** headline 2.1...> > > > removing the second folded propertiy results correctly in: > > * headline 1...> > > > This looks like a bug in the :VISIBILITY: handling!? No, I don't think so. You are asking for trouble by using this property in a nested way. Nooruls patch seems to fix it though, I have applied it. - Carsten