emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Aaron Ecay <aaronecay@gmail.com>
To: Sebastien Vauban <sva-news@mygooglest.com>, emacs-orgmode@gnu.org
Subject: Re: parser: verbatim or code?
Date: Fri, 23 Jan 2015 15:31:47 -0500	[thread overview]
Message-ID: <87egqlgrws.fsf@gmail.com> (raw)
In-Reply-To: <86ppa5e229.fsf@example.com>

Hi Sebastien,

2015ko urtarrilak 23an, Sebastien Vauban-ek idatzi zuen:
>> Since = and ~ have been inverted, I think it'd make sense to make
>> `org-babel-inline-result-wrap' now default to "~%s" (instead of
>> "=%s"), for markup that produces verbatim text.
> 
> Here is the patch.

If I understand this thread correctly, = 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 – results are not generally
speaking code (though of course in special cases they can be).

I’m 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,

-- 
Aaron Ecay

next prev parent reply	other threads:[~2015-01-23 20:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15 13:43 parser: verbatim or code? Yasushi SHOJI
2014-02-15 14:23 ` Nick Dokos
2014-02-16  8:51   ` Yasushi SHOJI
2014-02-16  9:20     ` Nicolas Goaziou
2014-02-16  9:43       ` Michael Brand
2014-02-16 10:00         ` Nicolas Goaziou
2014-02-16 11:52           ` Michael Brand
2014-03-04  9:52             ` Bastien
2015-01-23 11:33               ` Sebastien Vauban
2015-01-23 19:20                 ` Sebastien Vauban
2015-01-23 20:31                   ` Aaron Ecay [this message]
     [not found]                     ` <87egqlgrws.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-30 11:02                       ` Sebastien Vauban
2014-02-18  4:19       ` Yasushi SHOJI

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87egqlgrws.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sva-news@mygooglest.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).