On Oct 28, 2010, at 1:10 AM, Dan Davison wrote:
"Thomas S. Dye" writes:
On Sep 9, 2010, at 12:35 PM, Dan Davison wrote:
"Thomas S. Dye" writes:
Hi Dan,
Glad to know that Darlan's slowdown is fixed.
No change here that I can tell. Now that I've had org-src-fontify-
natively set to t f
Jambunathan K writes:
> Jules Bean writes:
>
>>>
>>> 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
>>> blo
Jules Bean writes:
>>
>> 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 exp
>
> 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 whatsoeve
"Thomas S. Dye" writes:
> On Sep 9, 2010, at 12:35 PM, Dan Davison wrote:
>
>> "Thomas S. Dye" writes:
>>
>>> Hi Dan,
>>>
>>> Glad to know that Darlan's slowdown is fixed.
>>>
>>> No change here that I can tell. Now that I've had org-src-fontify-
>>> natively set to t for a while, I can see tha
On Sep 9, 2010, at 12:35 PM, Dan Davison wrote:
"Thomas S. Dye" writes:
Hi Dan,
Glad to know that Darlan's slowdown is fixed.
No change here that I can tell. Now that I've had org-src-fontify-
natively set to t for a while, I can see that the slowdown is
proportional to the number and siz
"Thomas S. Dye" writes:
> Hi Dan,
>
> Glad to know that Darlan's slowdown is fixed.
>
> No change here that I can tell. Now that I've had org-src-fontify-
> natively set to t for a while, I can see that the slowdown is
> proportional to the number and size of code blocks in the Org-mode
> file.
Hi Dan,
Glad to know that Darlan's slowdown is fixed.
No change here that I can tell. Now that I've had org-src-fontify-
natively set to t for a while, I can see that the slowdown is
proportional to the number and size of code blocks in the Org-mode
file. It is most noticeable in a file w
Thank you Dan,
It is perfect now. No perceivable slowdown
At Wed, 08 Sep 2010 13:41:51 -0400,
Dan Davison wrote:
>
> Darlan Cavalcante Moreira writes:
>
> > 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
Erik Iverson writes:
> Sébastien Vauban wrote:
>> Hi Bastien and Dan,
>>
>> Bastien wrote:
>>> Dan Davison 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 consiste
Sébastien Vauban wrote:
Hi Bastien and Dan,
Bastien wrote:
Dan Davison 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, perhaps "Org Code" or
"
Hi Bastien and Dan,
Bastien wrote:
> Dan Davison 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, perhaps "Org Code" or
>> "Org Src" or "Or
Darlan Cavalcante Moreira writes:
> 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.
Thank you Darlan,
I have just pushed a change th
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 cau
Dan Davison 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, perhaps "Org Code" or
> "Org Src" or "Org Source Code" ? Views?
I find "Org Code"
Carsten Dominik writes:
> On Tue, Sep 7, 2010 at 3:43 PM, Dan Davison wrote:
>> "David O'Toole" 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 wrote:
If setting
Sebastian Rose writes:
> Bastien writes:
>
>> Carsten Dominik 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.
>>
>>
Hi Dan,
Yes, I can confirm that (setq org-src-fontify-natively nil) makes
unfolding snappy again.
All the best,
Tom
On Sep 7, 2010, at 3:23 AM, Dan Davison wrote:
"Thomas S. Dye" writes:
Aloha Dan,
This is really nice. Thanks for shepherding it along.
In some of my use cases there is
Tom Short 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 profiling and speeding it up
Hi Carsten, Bastien and the rest,
Bastien wrote:
> Carsten Dominik 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.
Thank
Bastien writes:
> Carsten Dominik 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
+2
> Or maybe a different fon
On Tue, Sep 7, 2010 at 4:33 PM, Bastien wrote:
> Carsten Dominik 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.
I mean
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
Carsten Dominik 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?
People might want to use an
Dan Davison writes:
> But I do think we are gravitating towards turning it off, if it is
> causing noticeable slowness on startup. So unless there are more voices
> in favour of keeping it turned on for new users then I'll turn it off
> later today.
I didn't test turning it on and off long enoug
On Tue, Sep 7, 2010 at 3:43 PM, Dan Davison wrote:
> "David O'Toole" 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 wrote:
>>> If setting org-src-fontify-natively to `t' by def
Dan Davison writes:
> "Thomas S. Dye" writes:
>
>> Aloha Dan,
>>
>> This is really nice. Thanks for shepherding it along.
>>
>> In some of my use cases there is a substantial delay when opening a
>> large file and then unfolding sections with many source code blocks.
>
> Hi Tom,
>
> I think thi
"David O'Toole" 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 wrote:
>> If setting org-src-fontify-natively to `t' by default triggers a debate
>> on whether we need to set org-warn-when
Richard Riley writes:
> Dan Davison writes:
>
>> Richard Riley writes:
>>
>>> Eric S Fraga writes:
>>>
On Thu, 02 Sep 2010 08:51:16 -0700, Dan Davison
wrote:
>
> I've just pushed changes which mean that Org now fontifies code in code
> blocks. Currently, this is turned
"Thomas S. Dye" writes:
> Aloha Dan,
>
> This is really nice. Thanks for shepherding it along.
>
> In some of my use cases there is a substantial delay when opening a
> large file and then unfolding sections with many source code blocks.
Hi Tom,
I think this is a good point and probably as you
Hi all,
Richard Riley wrote:
> Eric S Fraga writes:
>
>> On Thu, 02 Sep 2010 08:51:16 -0700, Dan Davison
>> 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 would be helpful
>>> if people could repo
"David O'Toole" writes:
> I agree Bastien :)
Possibly a customize interface for it would be nice too if the code is touched!
>
> On Mon, Sep 6, 2010 at 2:30 PM, Bastien wrote:
>> If setting org-src-fontify-natively to `t' by default triggers a debate
>> on whether we need to set org-warn-when
I agree Bastien :)
On Mon, Sep 6, 2010 at 2:30 PM, Bastien 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 org-src-fontify-natively off by
> default...
Dan Davison writes:
> Richard Riley writes:
>
>> Eric S Fraga writes:
>>
>>> On Thu, 02 Sep 2010 08:51:16 -0700, Dan Davison
>>> 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 would be helpf
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
___
Richard Riley writes:
> Eric S Fraga writes:
>
>> On Thu, 02 Sep 2010 08:51:16 -0700, Dan Davison
>> 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 would be helpful
>>> if people could report an
On 09/06/2010 11:59 AM, Richard Riley wrote:
Eric S Fraga writes:
On Thu, 02 Sep 2010 08:51:16 -0700, Dan Davison 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 would be helpful
if people could report any
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 a
Eric S Fraga writes:
> On Thu, 02 Sep 2010 08:51:16 -0700, Dan Davison
> 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 would be helpful
>> if people could report any problems, and opinions as to wh
Hi Dan (and David),
Dan Davison 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 would be helpful if
> people could report any problems, and opinions
Three remarks:
1. That simply *is* great! Thanks a lot,
40 matches
Mail list logo
