From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Wiegley Subject: Re: Allowing loose ordering in Org files Date: Tue, 10 Nov 2015 12:11:46 -0800 Message-ID: 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: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50008) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwFGi-00056K-VU for emacs-orgmode@gnu.org; Tue, 10 Nov 2015 15:11:53 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZwFGf-0004NA-OO for emacs-orgmode@gnu.org; Tue, 10 Nov 2015 15:11:52 -0500 Received: from mail-pa0-x229.google.com ([2607:f8b0:400e:c03::229]:33687) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwFGf-0004N6-Ip for emacs-orgmode@gnu.org; Tue, 10 Nov 2015 15:11:49 -0500 Received: by pabfh17 with SMTP id fh17so6734226pab.0 for ; Tue, 10 Nov 2015 12:11:49 -0800 (PST) In-Reply-To: <87vb99zlb0.fsf@Rainer.invalid> (Achim Gratz's message of "Tue, 10 Nov 2015 20:49:55 +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: Achim Gratz Cc: emacs-orgmode@gnu.org >>>>> Achim Gratz writes: > If you don't use properties then it doesn't affect you at all. If you do, > then=E2=80=A6 well, I personally simply don't care. Just like there's sev= eral style > guides for writing C; as long as these are applied consistently I can live > with most of them and put the braces and indents the way they prescribe. 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 readi= ng my entry. What a lot of people want is trivial, and only relevant to them, but part of the Emacs philosophy is to give them the freedom to customize their environment the way they want it to work, rather than decide for them what = is the "right way". I won't argue for this anymore, if it really does incur work for you that o= nly benefits me and a few others. I suppose that I'm still writing these e-mails because I want to inject some sensitivity about these matters into your fut= ure decisions, so you don't take away such flexibility again lightly. > So write the advise and move on? If you weren't so heavily invested in wh= at > you perceive as "the right style" you quite likely wouldn't care, or would > you? I'm invested in the spirit of the project, since I've been using it for a v= ery long time, and continue to recommend it to many people as an amazing tool f= or self-organization. The more it becomes something I have to hack to like, the less I feel like putting my heart into it. 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 throa= ts. Yours, John