Disabling a mode based on the size of a buffer?

Disabling a mode based on the size of a buffer?

[Tim Visher]

Hi All,

When a buffer gets to a certain size, paredit mode specifically begins
to struggle, as do some other modes.

I'm basically wondering if there are predefined hooks with which I can
make a decision to disable said modes if a buffer has reached a
certain size limit.

Thoughts?

--

In Christ,

Timmy V.

http://blog.twonegatives.com/
http://five.sentenc.es/ -- Spend less time on mail

Re: Disabling a mode based on the size of a buffer?

[Michael Heerdegen]

Tim Visher <tim.visher@gmail.com> writes:

> Hi All,
>
> When a buffer gets to a certain size, paredit mode specifically begins
> to struggle, as do some other modes.

I don't see that for paredit.  In a buffer with >10000 lines, any
paredit command is still executed without measurable delay.  In which
way does it struggle for you?  What are these other modes?

> I'm basically wondering if there are predefined hooks with which I can
> make a decision to disable said modes if a buffer has reached a
> certain size limit.

No, not that I knew.  You could use a timer to observe the buffer size.

Michael.

Re: Disabling a mode based on the size of a buffer?

[Juanma Barranquero]

On Tue, Aug 20, 2013 at 7:08 PM, Tim Visher <tim.visher@gmail.com> wrote:

> I'm basically wondering if there are predefined hooks with which I can
> make a decision to disable said modes if a buffer has reached a
> certain size limit.

Not very sofisticate:

(add-hook 'after-change-functions
          (lambda (&rest _ignore)
            (when (> (buffer-size) 1000000)
              (fundamental-mode)))
          nil t)

HTH,

   J

Re: Disabling a mode based on the size of a buffer?

[Tim Visher]

On Tue, Aug 20, 2013 at 5:44 PM, Michael Heerdegen
<michael_heerdegen@web.de> wrote:
> Tim Visher <tim.visher@gmail.com> writes:
>
>> Hi All,
>>
>> When a buffer gets to a certain size, paredit mode specifically begins
>> to struggle, as do some other modes.
>
> I don't see that for paredit.  In a buffer with >10000 lines, any
> paredit command is still executed without measurable delay.  In which
> way does it struggle for you?  What are these other modes?

Mine is [31000 lines][bible.cljs]. The enabled modes in that buffer are

    Clojure Auto-Composition Auto-Compression Auto-Encryption
    Column-Number Cua Diff-Auto-Refine Eldoc Electric-Indent Electric-Pair
    Erc-Autojoin Erc-Button Erc-Fill Erc-Irccontrols Erc-List Erc-Match
    Erc-Menu Erc-Move-To-Prompt Erc-Netsplit Erc-Networks Erc-Noncommands
    Erc-Pcomplete Erc-Readonly Erc-Ring Erc-Stamp Erc-Track Erc-Track
    File-Name-Shadow Font-Lock Global-Font-Lock Global-Hl-Line Hi-Lock Hs
    Idle-Highlight Ido-Everywhere Ido-Ubiquitous Line-Number
    Nrepl-Interaction Recentf Shell-Dirtrack Show-Paren Textmate
    Transient-Mark Whitespace Winner Yas

I'm assuming several of them could be the culprit, but I would guess
it would be Clojure mode attempting to do syntax highlighting.

Anyway, if you position your cursor just inside the verses vector in
[this file][bible.cljs] and use
`paredit-splice-sexp-killing-backward`, does it work lickety-split?

[bible.cljs]: https://raw.github.com/timvisher/bible-plan/master/src/cljs/bible_plan/bible.cljs

--

In Christ,

Timmy V.

http://blog.twonegatives.com/
http://five.sentenc.es/ -- Spend less time on mail

Re: Disabling a mode based on the size of a buffer?

[Tim Visher]

On Tue, Aug 20, 2013 at 9:41 PM, Juanma Barranquero <lekktu@gmail.com> wrote:
> On Tue, Aug 20, 2013 at 7:08 PM, Tim Visher <tim.visher@gmail.com> wrote:
>
>> I'm basically wondering if there are predefined hooks with which I can
>> make a decision to disable said modes if a buffer has reached a
>> certain size limit.
>
> Not very sofisticate:
>
> (add-hook 'after-change-functions
>           (lambda (&rest _ignore)
>             (when (> (buffer-size) 1000000)
>               (fundamental-mode)))
>           nil t)

That'd do it. :)

--

In Christ,

Timmy V.

http://blog.twonegatives.com/
http://five.sentenc.es/ -- Spend less time on mail

Re: Disabling a mode based on the size of a buffer?

[Julien Cubizolles]

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Tim Visher <tim.visher@gmail.com> writes:
>
>> Hi All,
>>
>> When a buffer gets to a certain size, paredit mode specifically begins
>> to struggle, as do some other modes.
>
> I don't see that for paredit.  In a buffer with >10000 lines, any
> paredit command is still executed without measurable delay.  In which
> way does it struggle for you?  What are these other modes?


I'm experiencing it too, with 3000 lines LaTeX buffers, typing '(' can
take up to one second to insert a pair of parenthesis.

Here is the mode description :

Auto-Composition Auto-Compression Auto-Encryption
Autopair Autopair-Global Blink-Cursor Diff-Auto-Refine Display-Time
Erc-Autojoin Erc-Button Erc-Fill Erc-Irccontrols Erc-List Erc-Match
Erc-Menu Erc-Move-To-Prompt Erc-Netsplit Erc-Networks Erc-Noncommands
Erc-Pcomplete Erc-Readonly Erc-Ring Erc-Stamp Erc-Track
File-Name-Shadow Flyspell-Lazy Font-Lock Global-Font-Lock
Helm-Match-Plugin Ido-Everywhere Line-Number Menu-Bar Mouse-Wheel
Paredit Rainbow-Delimiters Reftex Shell-Dirtrack Show-Paren Tabbar
Tabbar-Mwheel Tex-Fold Tex-Pdf Tex-Source-Correlate Tooltip
Transient-Mark Workgroups Yas Yas-Global

(Information about these minor modes follows the major mode info.)

LaTeX/FPS mode defined in `tex-site.el':

Julien.

Re: Disabling a mode based on the size of a buffer?

[Stefan Monnier]

> Not very sofisticate:

> (add-hook 'after-change-functions
>           (lambda (&rest _ignore)
>             (when (> (buffer-size) 1000000)
>               (fundamental-mode)))
>           nil t)

It's still just a workaround, and unless the buffer is really "too
large", this should be reported as a bug (ideally with an
easy-to-reproduce-recipe).


        Stefan

Re: Disabling a mode based on the size of a buffer?

[Juanma Barranquero]

On Sun, Aug 25, 2013 at 3:52 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:

> It's still just a workaround

And a crude one, to boot.

 J