From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bastien Subject: Re: [RFC] Creole-style / Support for **emphasis**__within__**a word** Date: Sat, 22 Mar 2014 16:22:27 +0100 Message-ID: <87lhw2mf64.fsf@bzg.ath.cx> References: <87zjl6ktu2.fsf@gmail.com> <87mwgimiqm.fsf@gmail.com> <87txaqmhzd.fsf@bzg.ath.cx> <87r45uthbc.fsf@med.uni-goettingen.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41882) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WRNl0-0006bD-7M for emacs-orgmode@gnu.org; Sat, 22 Mar 2014 11:22:52 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WRNku-0000C6-8Q for emacs-orgmode@gnu.org; Sat, 22 Mar 2014 11:22:46 -0400 Received: from rs249.mailgun.us ([209.61.151.249]:53855) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WRNku-0000Bs-0Y for emacs-orgmode@gnu.org; Sat, 22 Mar 2014 11:22:40 -0400 In-Reply-To: <87r45uthbc.fsf@med.uni-goettingen.de> (Andreas Leha's message of "Sat, 22 Mar 2014 15:54:15 +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: Andreas Leha Cc: emacs-orgmode@gnu.org Hi Andreas, I'm also in favor of breaking backward compatibility when it benefits Org's users and developers. We should not consider changes only in terms of backward compatibility, we should also consider them by themselves. What I like with *this markup* is that it's non-intrusive: it's easy to type and it does not clutter the document. And in general, I'd rather fix problems then getting rid of them for maintainability purpose. What's the problems with *this markup*? It is difficult to get proper fontification in some cases, fontification of multiple lines is not reliable beyond a certain amout of lines, and we cannot nest markup. Until someone has taken the time to seriously try to fix those problems without changing the current feature, I don't think we should consider changing the feature itself. But of course, this is always a trade-off. -- Bastien