Hi Carsten,
Carsten Dominik writes:
> I don’t have strong feelings either way. Lets turn it on a see what
> the impact will be.
Done in master, thanks,
--
Bastien
On 14 Jan 2014, at 21:47, Bastien wrote:
> Hi Sébastien,
>
> "Sebastien Vauban"
> writes:
>
>> I think this overall results of the poll is quite clear, no?
>
> Well, I think we should wait for Carsten's vote on this.
>
> Carsten, do you think `org-src-fontify-natively' should
> be set to
Hello Bastien,
Bastien wrote:
> When `org-src-fontify-natively' will be `t' by default,
> it will be important to keep the distinction between source
> blocks and HTML/LaTeX blocks.
>
> So HTML blocks should remain unfontified by default, just
> to mark the difference with "active" source blocks.
When `org-src-fontify-natively' will be `t' by default,
it will be important to keep the distinction between source
blocks and HTML/LaTeX blocks.
So HTML blocks should remain unfontified by default, just
to mark the difference with "active" source blocks.
I still think an option to highlight th
Hi Sébastien,
"Sebastien Vauban"
writes:
> I think this overall results of the poll is quite clear, no?
Well, I think we should wait for Carsten's vote on this.
Carsten, do you think `org-src-fontify-natively' should
be set to `t' by default for Org 8.3? Votes are for this
default in majori
Hello Bastien,
Eric S Fraga wrote:
> +1 for org-src-fontify-natively set to t by default. I've had this
> turned on forever... I cannot imagine using org without it!
I think this overall results of the poll is quite clear, no?
Best regards,
Seb
--
Sebastien Vauban
Sebastien et al.,
+1 for org-src-fontify-natively set to t by default. I've had this
turned on forever... I cannot imagine using org without it!
--
: Eric S Fraga (0xFFFCF67D), Emacs 24.3.1, Org release_8.2.4-322-gece429
Nicolas Goaziou wrote:
>> Oh, maybe I see. You want highlighting in #+BEGIN_LaTeX
>> and #+BEGIN_HTML.
>>
>> Actually it makes sense.
>>
>> So that #+BEGIN_HTML would really be short for #+BEGIN_SRC html-mode
>> but with no need for header vars and all the plumbing.
>>
>> Nicolas, what do you thin
Hello,
Bastien writes:
> Oh, maybe I see. You want highlighting in #+BEGIN_LaTeX
> and #+BEGIN_HTML.
>
> Actually it makes sense.
>
> So that #+BEGIN_HTML would really be short for #+BEGIN_SRC html-mode
> but with no need for header vars and all the plumbing.
>
> Nicolas, what do you think?
I
Hi Joseph,
Joseph Vidal-Rosset writes:
> I must add that the highlighting works only in code with begin_src-
> ... end_src à la org.
Yes, this is by design.
> But then, at least in my configuration, it blocks
> the export in LaTeX or in HTML.
Not sure I grok this part...
> I have not
On 2014-01-09 13:22 Sebastien Vauban wrote:
> WDYT if we turn it on by default?
+1. I turned this on the minute I found out about this feature. This was
one of the many wow-moments while discovering Org-mode.
Regards,
--
Alexander Baier
On 2014-01-09 07:22, Sebastien Vauban wrote:
Hello,
(setq org-src-fontify-natively t)
as the default value of `org-src-fontify-natively' is `nil'.
WDYT if we turn it on by default?
+1.
Le jeu. 09 janv. 2014à 01:22:31 , "Sebastien Vauban"
a envoyé ce message:
> Hello,
>
> Currently, to get "code highlighting" (which is contextual to the
> language of the code block) enabled within your Org buffers, you need to
> add the following line to your Emacs config file
Sebastien Vauban writes:
>...
> (setq org-src-fontify-natively t)
>
> as the default value of `org-src-fontify-natively' is `nil'.
>
> WDYT if we turn it on by default?
>...
I vote: YES, true by default
Hello,
Currently, to get "code highlighting" (which is contextual to the
language of the code block) enabled within your Org buffers, you need to
add the following line to your Emacs config file:
(setq org-src-fontify-natively t)
as the default value of `org-src-fontify-natively' is `nil'.
WD
15 matches
Mail list logo
