From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Bastien <bzg-mXXj517/zsQ@public.gmane.org>,
Michael Brand
<michael.ch.brand-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Nicolas Goaziou
<n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Org Mode <emacs-orgmode-mXXj517/zsQ@public.gmane.org>
Subject: Re: parser: verbatim or code?
Date: Fri, 23 Jan 2015 12:33:18 +0100 [thread overview]
Message-ID: <86y4otn341.fsf@example.com> (raw)
In-Reply-To: 87lhwq44wu.fsf@bzg.ath.cx
Hello,
Bastien wrote:
> Hi Yasushi, Michael and Nicolas,
>
> Michael Brand <michael.ch.brand-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>> The syntax for inline code snippets seems easier to read by human and
>> to parse with "~" than with "=" because inline code snippets use "~"
>> less often than "=". I avoid "~/" by using "$HOME/" in my notes about
>> shell and shell scripts. Some examples:
>
> I've now fix those inconsistencies, both in the manual and in the
> code. I followed Michael suggestion to use ~code~ and =verbatim=.
>
> We may need to update the way export backend treat this markup, and
> try to be consistent here too.
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.
That will put fix back as what they were for people having different CSS
or LaTeX styles applied to both markers.
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2015-01-23 11:33 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 [this message]
2015-01-23 19:20 ` Sebastien Vauban
2015-01-23 20:31 ` Aaron Ecay
[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=86y4otn341.fsf@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=bzg-mXXj517/zsQ@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
--cc=michael.ch.brand-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=n.goaziou-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).