Hi Tom,
I've used fontification in Org code blocks constantly for a couple of
months now, and I do not agree that there are any editing or unfolding
delays which should deter typical Org users from using fontified src
blocks. In typical usage I do not experience any delays whatsoever (my
Maybe my problem is not related to slow folding/unfolding behavior that you
are getting, but if I set the org-src-tab-acts-natively variable to t the
folding/unfolding of headlines becomes very slow for me.
In fact, I was thinking that I had the problem described here, but I just
isolated the
Sébastien Vauban wrote:
Hi Bastien and Dan,
Bastien wrote:
Dan Davison davi...@stats.ox.ac.uk writes:
(We badly need a customize group for these org-src but non-babel
variables[1]. That suggests to me subsuming the Babel group (Should be
Org Babel for consistency?) within a new group,
On Tue, Sep 7, 2010 at 3:43 PM, Dan Davison davi...@stats.ox.ac.uk wrote:
David O'Toole dto1...@gmail.com writes:
I agree Bastien :)
I agree too, but note that what we are agreeing to is a conditional
statement...
On Mon, Sep 6, 2010 at 2:30 PM, Bastien bastien.gue...@wikimedia.fr wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
I *do* like the idea mentioned earlier to use a different background
when fontification is turned on. Just a slight grey instead of white,
for example. That would help distinguish things in export mode.
+1
Or maybe a different font?
I think it'd help for new users to keep it on by default, but since it
can be changed, I'm fine either way. How hard would it be to use a
property, so it could be changed on a per-file basis? If it's
difficult, that time may be better spent profiling and speeding it up.
- Tom
On Tue, Sep 7, 2010
On Tue, Sep 7, 2010 at 4:33 PM, Bastien bastien.gue...@wikimedia.fr wrote:
Carsten Dominik carsten.domi...@gmail.com writes:
I *do* like the idea mentioned earlier to use a different background
when fontification is turned on. Just a slight grey instead of white,
for example. That would
Bastien bastien.gue...@wikimedia.fr writes:
Carsten Dominik carsten.domi...@gmail.com writes:
I *do* like the idea mentioned earlier to use a different background
when fontification is turned on. Just a slight grey instead of white,
for example. That would help distinguish things in export
Tom Short tshort.rli...@gmail.com writes:
I think it'd help for new users to keep it on by default, but since it
can be changed, I'm fine either way. How hard would it be to use a
property, so it could be changed on a per-file basis? If it's
difficult, that time may be better spent
maybe there could be an on-by-default variable called
org-warn-when-editing-src-block-in-org-buffer, or make the text
readonly, etc.
making this on-by-default would seem to create another discussion
about things being on-by-default :)
however, if fontification is on by default, then this should
On 09/06/2010 11:59 AM, Richard Riley wrote:
Eric S Fragaucec...@ucl.ac.uk writes:
On Thu, 02 Sep 2010 08:51:16 -0700, Dan Davisondavi...@stats.ox.ac.uk wrote:
I've just pushed changes which mean that Org now fontifies code in code
blocks. Currently, this is turned on by default, so it
If setting org-src-fontify-natively to `t' by default triggers a debate
on whether we need to set org-warn-when-editing-src-block-in-org-buffer
on or off by default, I'd rather set org-src-fontify-natively off by
default...
My 2 cts,
--
Bastien
I agree Bastien :)
On Mon, Sep 6, 2010 at 2:30 PM, Bastien bastien.gue...@wikimedia.fr wrote:
If setting org-src-fontify-natively to `t' by default triggers a debate
on whether we need to set org-warn-when-editing-src-block-in-org-buffer
on or off by default, I'd rather set
13 matches
Mail list logo
