From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pontus Michael Subject: Re: Proposal to replace the prefix repetition with whitespace during expansion of noweb references Date: Mon, 31 Mar 2014 01:13:40 +0400 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b3a8666b478ee04f5d968d1 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44231) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUN31-0001EP-8J for emacs-orgmode@gnu.org; Sun, 30 Mar 2014 17:13:44 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WUN30-00087U-BJ for emacs-orgmode@gnu.org; Sun, 30 Mar 2014 17:13:43 -0400 Received: from mail-lb0-x236.google.com ([2a00:1450:4010:c04::236]:43154) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WUN30-00087N-3b for emacs-orgmode@gnu.org; Sun, 30 Mar 2014 17:13:42 -0400 Received: by mail-lb0-f182.google.com with SMTP id n15so5149417lbi.41 for ; Sun, 30 Mar 2014 14:13:40 -0700 (PDT) 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: ccberry@ucsd.edu, emacs-orgmode@gnu.org --047d7b3a8666b478ee04f5d968d1 Content-Type: text/plain; charset=ISO-8859-1 Hello, Charles. Thank you for your reply. I appreciate your suggestion, however the example which I used is not a limiting factor which I seek help in overcoming. Instead I'm trying to address a potential design flaw. You make a valid point that change of this nature will inevitably break existing code that has been taking advantage of this functionality. From my point of view this is an argument in favor of having this issue addressed as soon as possible. --047d7b3a8666b478ee04f5d968d1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hello, Charles.

Thank you for your reply.

I = appreciate your suggestion, however the example which I used is not a
li= miting factor which I seek help in overcoming. Instead I'm trying to address a potential design flaw.

You make a valid point that change = of this nature will inevitably break
existing code that has been taking = advantage of this functionality. From
my point of view this is an argume= nt in favor of having this issue
addressed as soon as possible.
--047d7b3a8666b478ee04f5d968d1--