Aaron Ecay wrote:
> 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
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
Hello,
Sebastien Vauban wrote:
> Bastien wrote:
>> Hi Yasushi, Michael and Nicolas,
>>
>> Michael Brand 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 "~/"
Hello,
Bastien wrote:
> Hi Yasushi, Michael and Nicolas,
>
> Michael Brand 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 ab
Hi Yasushi, Michael and Nicolas,
Michael Brand 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.
Hi Nicolas,
At Sun, 16 Feb 2014 10:20:55 +0100,
Nicolas Goaziou wrote:
>
> If we do change them, it should only happen in "org-element.el". I don't
> think that would break existing documents, as code and verbatim are
> really close to each other.
>
> I don't care either way. Though, I lean towa
Hi Nicolas
On Sun, Feb 16, 2014 at 11:00 AM, Nicolas Goaziou wrote:
> Indeed, that's the very issue we're discussing in this thread.
>
> I'm not sure to understand what you mean here.
For me it was not explicit enough that this
((equal marker "~") 'code)
((equal marker "=") 'verbatim)
Hello,
Michael Brand writes:
> When I read org-element-text-markup-successor
>
> ((equal marker "~") 'code)
> ((equal marker "=") 'verbatim)
>
> it confuses me because of the well known Org manual
>
> You can make words *bold*, /italic/, _underlined_, =code= and
> ~verbatim~
Ind
Hi Nicolas
On Sun, Feb 16, 2014 at 10:20 AM, Nicolas Goaziou wrote:
> If we leave it as-is, documentation needs to be updated anyway.
>
> If we do change them, it should only happen in "org-element.el". I don't
> think that would break existing documents, as code and verbatim are
> really close t
Hello,
Yasushi SHOJI writes:
> Nick Dokos wrote:
>>
>> I think it's a code bug: ~verbatim~ is the precedent-setting latex
>> convention.
>>
>> However fixing it might break existing documents (although in many
>> instances code and verbatim are treated equivalently, so that might
>> not be muc
Hi,
At Sat, 15 Feb 2014 09:23:41 -0500,
Nick Dokos wrote:
>
> I think it's a code bug: ~verbatim~ is the precedent-setting latex
> convention.
>
> However fixing it might break existing documents (although in many
> instances code and verbatim are treated equivalently, so that might
> not be muc
Yasushi SHOJI writes:
> Hello,
>
> While writing a new exporter I've noticed that `=' is actually for
> verbatim and `~' is for code emphasis despite the fact that the
> current org manual says:
>
> You can make words *bold*, /italic/, _underlined_, =code= and
> ~verbatim~
>
> Is this
Hello,
While writing a new exporter I've noticed that `=' is actually for
verbatim and `~' is for code emphasis despite the fact that the
current org manual says:
You can make words *bold*, /italic/, _underlined_, =code= and
~verbatim~
Is this documentation bug?
regards,
--
13 matches
Mail list logo
