From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jambunathan K Subject: Re: Flexible plain list bullets Date: Fri, 20 Apr 2012 11:28:08 +0530 Message-ID: <81k41bymfj.fsf@gmail.com> 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]:47849) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SL6rZ-0000mp-HH for emacs-orgmode@gnu.org; Fri, 20 Apr 2012 01:58:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SL6rX-0000S5-IW for emacs-orgmode@gnu.org; Fri, 20 Apr 2012 01:58:33 -0400 Received: from mail-pz0-f49.google.com ([209.85.210.49]:61982) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SL6rX-0000Rt-9W for emacs-orgmode@gnu.org; Fri, 20 Apr 2012 01:58:31 -0400 Received: by dadq36 with SMTP id q36so10277073dad.36 for ; Thu, 19 Apr 2012 22:58:29 -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 "Mark E. Shoulson" writes: > else reconsider my patch Contributions to Org/Emacs requires copyright assignments. Search for FSF in the following page: http://orgmode.org/worg/org-contribute.html I am wondering: Why a overlay solution will not work for you? Why do you need Unicode characters right in the file. Export engines can replace the ASCII bullets with Unicode bullets. For the sake of argument, if the Org parser fails to parse and export a non-canonical Org file will that upset you in anyways. You need to offer a reason that goes beyond mere aesthetics to build a much stronger case. We should leave aside what is already there. Your argument parallels the below social situation. (Replace broken windows => Customizable options, Vandalism => Feature creep) Maintainers are trying to make sure that more customization aren't added until a very strong case is made in support of them. ,---- http://en.wikipedia.org/wiki/Broken_windows_theory | Consider a building with a few broken windows. If the windows are not | repaired, the tendency is for vandals to break a few more | windows. Eventually, they may even break into the building, and if | it's unoccupied, perhaps become squatters or light fires inside. Or | consider a sidewalk. Some litter accumulates. Soon, more litter | accumulates. Eventually, people even start leaving bags of trash from | take-out restaurants there or breaking into cars. `---- That said, it is just a customizable option. People use Org for diverse needs. If one is willing to pay the penalty of having a non-standard Org file - broken export being one - then she is well within her rights to shoot herself in the foot. Btw, your proposal has received 3 downvotes already and not even a single upvote yet. --