While diagnosing a server condition, I was listing parts of a system log
via a babel expression. The 130 lines in the babel output are wrapped in
an example block. This block caused massive slowdown of scrolling and
other operations.
Using the emacs profiler I see:
- redisplay_internal (C functi
Hello,
Thomas S. Dye writes:
> William Denton writes:
>
>> On 5 December 2015, Nicolas Goaziou wrote:
>>
>>> However, this report raises an interesting question about footnotes:
>>> should we still support plain (e.g., "[1]") footnotes in Org documents?
>>>
>>> The pattern is very common an reg
Hello,
Aaron Ecay writes:
> The way I read the report, org-footnote-in-valid-context-p takes 44%
> of the cumulative time, which is composed of
> org-inside-LaTeX-fragment-p (25%) + org-in-block-p (16%) + other stuff
> (3%). So org-inside-LaTeX-fragment-p accounts for >50% of the time
> spent in
William Denton writes:
> On 5 December 2015, Nicolas Goaziou wrote:
>
>> However, this report raises an interesting question about footnotes:
>> should we still support plain (e.g., "[1]") footnotes in Org documents?
>>
>> The pattern is very common an regularly introduces false positives.
>> Al
On 5 December 2015, Nicolas Goaziou wrote:
However, this report raises an interesting question about footnotes:
should we still support plain (e.g., "[1]") footnotes in Org documents?
The pattern is very common an regularly introduces false positives.
Also, IIRC, it was introduced for non-Org b
as with others, i am ok with nixing those [1] footnotes if nobody objects.
on the other hand, i strongly want inline footnotes to work again with
multiple paragraphs, including in fontifying. i know export is
incompatible with post-8.0 paragraphs and will accept a filter or
something if needed as
Nicolas Goaziou writes:
> However, this report raises an interesting question about footnotes:
> should we still support plain (e.g., "[1]") footnotes in Org documents?
>
> The pattern is very common an regularly introduces false positives.
> Also, IIRC, it was introduced for non-Org buffers (e.g
Alan L Tyree writes:
> I would be delighted to see the 'plain' footnote format abolished. I
> use org for writing legal text which often has things like Bank of New
> South Wales v Laing [1954] AC 135. Rasmus helped me with a patch to
> ignore these kinds of references, but they remain a nuisance.
On 05/12/15 23:58, Nicolas Goaziou wrote:
Hello,
Derek Feichtinger writes:
While diagnosing a server condition, I was listing parts of a system log
via a babel expression. The 130 lines in the babel output are wrapped in
an example block. This block caused massive slowdown of scrolling and
ot
Hi Nicolas,
2015ko abenudak 5an, Nicolas Goaziou-ek idatzi zuen:
>
> Hello,
>
> Aaron Ecay writes:
>
>> Indeed. However, this code was needlessly slow because it failed to
>> take advantage of short-circuit evaluation.
>
> According to the profile report, I don't understand the logic of your
Hello,
Aaron Ecay writes:
> Indeed. However, this code was needlessly slow because it failed to
> take advantage of short-circuit evaluation.
According to the profile report, I don't understand the logic of your
patch.
>>> - org-footnote-in-valid-context-p 4106 44%
>>>
Hi Nicolas,
2015ko abenudak 5an, Nicolas Goaziou-ek idatzi zuen:
>
> This is a limitation of our current way to fontify a buffer. Changing it
> implies some serious work, which I'd rather spend on switching to
> syntax-based (instead of regexp-based) fontification.
Indeed. However, this code wa
Hello,
Derek Feichtinger writes:
> While diagnosing a server condition, I was listing parts of a system log
> via a babel expression. The 130 lines in the babel output are wrapped in
> an example block. This block caused massive slowdown of scrolling and
> other operations.
>
> Using the emacs p
While diagnosing a server condition, I was listing parts of a system log
via a babel expression. The 130 lines in the babel output are wrapped in
an example block. This block caused massive slowdown of scrolling and
other operations.
Using the emacs profiler I see:
- redisplay_internal (C functio
14 matches
Mail list logo
