From mboxrd@z Thu Jan 1 00:00:00 1970 From: Achim Gratz Subject: Re: Allowing loose ordering in Org files Date: Tue, 10 Nov 2015 21:38:30 +0100 Message-ID: <87fv0dzj21.fsf@Rainer.invalid> References: <871tc83p01.fsf@flynn.nichework.com> <84611j19hk.fsf@gmail.com> <5638C2A1.2090801@iancu.ch> <87h9l32gfc.fsf@nicolasgoaziou.fr> <87d1vq3mh4.fsf@nicolasgoaziou.fr> <874mh23iw0.fsf@nicolasgoaziou.fr> <878u6eu5wg.fsf@Rainer.invalid> <315DDEDC-1BD9-4680-A8C8-B36821EB931C@gmail.com> <874mh2u2w0.fsf@Rainer.invalid> <87ziytyl3z.fsf@free.fr> <877flqskci.fsf@gmail.com> <87vb99zlb0.fsf@Rainer.invalid> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57268) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwFgh-00077M-Sb for emacs-orgmode@gnu.org; Tue, 10 Nov 2015 15:38:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZwFgd-0001eQ-Rw for emacs-orgmode@gnu.org; Tue, 10 Nov 2015 15:38:43 -0500 Received: from plane.gmane.org ([80.91.229.3]:42325) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwFgd-0001eG-LH for emacs-orgmode@gnu.org; Tue, 10 Nov 2015 15:38:39 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1ZwFgc-0004ia-6S for emacs-orgmode@gnu.org; Tue, 10 Nov 2015 21:38:38 +0100 Received: from p54b47902.dip0.t-ipconnect.de ([84.180.121.2]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 10 Nov 2015 21:38:38 +0100 Received: from Stromeko by p54b47902.dip0.t-ipconnect.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 10 Nov 2015 21:38:38 +0100 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 John Wiegley writes: > In my regimen, every single entry has a PROPERTIES drawer, since I tag each > one with ID and CREATED, for future reference. Most items are SCHEDULED as > well. So when I open up a headline to look at the contents, I see: > > * Head > SCHEDULED > text > :PROPERTIES:... > > It's a trivial thing, but I'd rather not scan past two lines to start reading > my entry. So isn't your request rather to hide the properties drawer better by default? You were _only_ talking about the UX in this whole thread and that might be a lot easier to adapt while not changing the way Org syntax is defined. There were lots of bugs to be fixed with properties and properties inheritance and I dabbled in that endeavour, which makes me more cautious about wading in and changing it yet again. Knowing where to find the properties quickly is key to this not falling apart again, IMHO. Even then, due to inheritance properties are probably the most complex thing to wrap your head around in Org aside from Babel. […] > I *care*, which is maybe both a blessing and a curse. It is the origin of my > creative contributions, but also the cause of these annoying threads. I'd > rather work with you guys than against you; but there are some sacred cows > that moan plaintively, when a sharp parenthesis is drawn across their throats. As I said above, the solution may well be different than both what you want to keep and what Org offers now. I don't find that thread particularly annoying, btw. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Waldorf MIDI Implementation & additional documentation: http://Synth.Stromeko.net/Downloads.html#WaldorfDocs