From mboxrd@z Thu Jan 1 00:00:00 1970 From: Aaron Ecay Subject: Re: parser: verbatim or code? Date: Fri, 23 Jan 2015 15:31:47 -0500 Message-ID: <87egqlgrws.fsf@gmail.com> References: <87iosg1oge.wl@dns1.atmark-techno.com> <87mwhsfo9e.fsf@gmail.com> <87ob27tp8p.wl@dns1.atmark-techno.com> <87eh33s9ag.fsf@gmail.com> <87a9drs7gj.fsf@gmail.com> <87lhwq44wu.fsf@bzg.ath.cx> <86y4otn341.fsf@example.com> <86ppa5e229.fsf@example.com> 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]:36052) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YEktX-0005I8-UY for emacs-orgmode@gnu.org; Fri, 23 Jan 2015 15:31:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YEktU-0008K7-Om for emacs-orgmode@gnu.org; Fri, 23 Jan 2015 15:31:55 -0500 Received: from mail-yk0-x234.google.com ([2607:f8b0:4002:c07::234]:47004) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YEktU-0008K3-L0 for emacs-orgmode@gnu.org; Fri, 23 Jan 2015 15:31:52 -0500 Received: by mail-yk0-f180.google.com with SMTP id 131so4119104ykp.11 for ; Fri, 23 Jan 2015 12:31:52 -0800 (PST) In-Reply-To: <86ppa5e229.fsf@example.com> 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: Sebastien Vauban , emacs-orgmode@gnu.org Hi Sebastien, 2015ko urtarrilak 23an, Sebastien Vauban-ek idatzi zuen: >> Since =3D and ~ have been inverted, I think it'd make sense to make >> `org-babel-inline-result-wrap' now default to "~%s" (instead of >> "=3D%s"), for markup that produces verbatim text. >=20 > Here is the patch. If I understand this thread correctly, =3D is now consistently interpreted as verbatim and ~ as code. I think verbatim (i.e. the status quo) is what makes sense for inline babel results =E2=80=93 results are not general= ly speaking code (though of course in special cases they can be). I=E2=80=99m not sure what you mean by > That will put fix back as what they were for people having different CSS > or LaTeX styles applied to both markers. It sounds like perhaps there are user customizations which are out of date with this change. Maybe an announcement is needed in ORG-NEWS to raise awareness of this change. Thanks, --=20 Aaron Ecay