From mboxrd@z Thu Jan 1 00:00:00 1970 From: "bva@alexanderonline.org" Subject: Re: Property for startup visibility? Date: Fri, 9 May 2008 15:58:57 +0100 Message-ID: <9DC620BC-8237-486C-AFF8-2A2038B44CCE@alexanderonline.org> References: <0C137CFD-3F28-4771-B61A-ACD447BA543C@alexanderonline.org> <8BD9FF75-9C07-4010-9152-846E413AE729@science.uva.nl> Mime-Version: 1.0 (Apple Message framework v919.2) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JuU3v-0005rm-6N for emacs-orgmode@gnu.org; Fri, 09 May 2008 10:59:07 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JuU3t-0005ra-Vx for emacs-orgmode@gnu.org; Fri, 09 May 2008 10:59:06 -0400 Received: from [199.232.76.173] (port=52837 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JuU3t-0005rX-Qm for emacs-orgmode@gnu.org; Fri, 09 May 2008 10:59:05 -0400 Received: from harley.gnservers.com ([72.52.242.16]:43828) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JuU3t-0007vB-Df for emacs-orgmode@gnu.org; Fri, 09 May 2008 10:59:05 -0400 In-Reply-To: <8BD9FF75-9C07-4010-9152-846E413AE729@science.uva.nl> 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: Carsten Dominik Cc: emacs-orgmode@gnu.org, Richard KLINDA On 2008-05-08 Thu, at 13:03, Carsten Dominik wrote: > > I am starting to like the idea. > >> Wow, I've never felt so .... convincing before! >> Thought-experiment: Should the VISIBILITY property be automatically >> inherited? > > I dont think so. Better to make possible values for the visibility > that affect the entire tree below. For example: > > folded > children (like the local "children" state) > content (like the global "content" state, but local tree only > all > Yeah, that is clearly a much better idea. To continue with that thought, may I suggest an additional value of 'invisible'? invisible: this headline (and content) is folded into the preceding headline folded: this headline is visible, but the content under it is invisible Perhaps there is better term for this. (What are those ellipses called now?) I would use 'invisible' for: 1. calendar headlines in the recent past. Right now I use the :ARCHIVE: tag to prevent unfolding, but in after I sort in chronological order, I still get too many old things showing up at the top of the tree. The down side is that then these items disappear from my agenda, where I sometimes scroll backwards to see what I did on that day. 2. projects that are completed but not yet archived (for me, everything, as I haven't really gotten comfortable with moving subtrees around using the archive mechanism) 3. reference headlines (phone number or booking confirmation numbers) that I don't need when planning, only while doing I see myself going to my preset visibility (C-u C-u TAB) and looking at my tree in one window. This would complement the agenda view, where doing something may require that phone number, and I have to hit TAB and get a split window. Please don't hold this suggestion against having a visibility property ;-) Next thought experiment: I suppose you'll have an immediate reaction on whether a descendant's visibility setting should override the ancestor's or vice versa. If I bury a task inside a calendar item (like my dad's birthday present in my original email), is it going to get shown (yeah! descendant's setting!) or not (boo!). Alternatively if I've set a Project headline (always a 2nd level headline in my original file) to ':VISIBILITY: children' but then try to set ':VISIBILITY: folded' at the top level head while I focus on something other area of the file, am I going to see the Project and its children (boo!) or will it be invisibly merged into the ellipses of the ancestor? (Yeah! ancestor's setting!) Having just written that, my vote is #1. If I need to focus on something for the time being, I'll just use tab. It'll always ignore the visibility property (curses!) ;-) Hypothetically speaking. -Ben