From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: Flexible plain list bullets Date: Fri, 20 Apr 2012 15:38:45 +0200 Message-ID: <8762cuttei.fsf@altern.org> References: <4F8F695D.5090600@kli.org> <87vckw3zk5.fsf@gmail.com> <4F90E3DC.1040901@kli.org> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:52009) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLE1q-0008CS-Cy for emacs-orgmode@gnu.org; Fri, 20 Apr 2012 09:37:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SLE1o-0005GC-IF for emacs-orgmode@gnu.org; Fri, 20 Apr 2012 09:37:37 -0400 Received: from mail-we0-f169.google.com ([74.125.82.169]:63524) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SLE1o-0005F1-8x for emacs-orgmode@gnu.org; Fri, 20 Apr 2012 09:37:36 -0400 Received: by werj55 with SMTP id j55so7891995wer.0 for ; Fri, 20 Apr 2012 06:37:34 -0700 (PDT) In-Reply-To: <4F90E3DC.1040901@kli.org> (Mark E. Shoulson's message of "Fri, 20 Apr 2012 00:19:40 -0400") 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: "Mark E. Shoulson" Cc: org-mode mailing list , Carsten Dominik Hi Mark, I agree with Nicolas that a solution based on overlays would be better. I also agree with you that there are many areas where we let the users modify the content of Org files in a way that makes them unparsable in a systematic manner. This is always a trade-off: user flexibility vs a rigid syntax. On top of this trade-off there are many other one to consider, based on what are the available human (benevolent) resources to maintain Org. I try to prioritize things this way: 1. fix current bugs 2. improve syntax stability (against current state of flexibility) 3. extend current features 4. integrate new features Sometimes, a request raises a discussion somewhere between (3) and (2) -- which is precisely the discussion we have now. But pointing at failure in the current syntactic ground does not help promoting a feature request at (3) :) Also, Nicolas is working on a generic parser which will be the base for future decision on (2), and (consequently) on (3). So yes, this is complicate. We have many users. And an overlay based solution will *not* be a temporary fix, it will be something that any user can enjoy. Thanks, -- Bastien