From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ilya Shlyakhter Subject: Re: are super-hidden technical blocks required? Date: Sat, 04 Aug 2012 14:10:52 -0400 Message-ID: References: <20120730144259.GA1017@nausicaa.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:52117) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sxioe-0007RO-JH for emacs-orgmode@gnu.org; Sat, 04 Aug 2012 14:11:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Sxiod-0007aE-Q4 for emacs-orgmode@gnu.org; Sat, 04 Aug 2012 14:11:08 -0400 Received: from plane.gmane.org ([80.91.229.3]:56652) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Sxiod-0007a8-Ig for emacs-orgmode@gnu.org; Sat, 04 Aug 2012 14:11:07 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1Sxioc-0005CV-I3 for emacs-orgmode@gnu.org; Sat, 04 Aug 2012 20:11:06 +0200 Received: from pool-71-174-46-72.bstnma.east.verizon.net ([71.174.46.72]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 04 Aug 2012 20:11:06 +0200 Received: from ilya_shl by pool-71-174-46-72.bstnma.east.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 04 Aug 2012 20:11:06 +0200 In-Reply-To: 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: emacs-orgmode@gnu.org On 7/31/2012 9:23 AM, Robert Horn wrote: > I agree. The real use needs more clarification. Things like ID are > already well hidden as :PROPERTIES: until the user explicitly opens the > drawer for viewing. I don't understand the need to hide those further, so > a better explanation of why is needed. One common use would be to store the creation & last-modification dates of each entry. I've tried various ways of doing it and they all were too obtrusive to use on _every_ entry. Time-stamping of all entries would be extremely useful, just as time-stamping of files is. But I don't want to see the timestamps during normal Org usage.