why is which-function-mode global?

why is which-function-mode global?

[Leo]

As suggested in the subject.

Leo

Re: why is which-function-mode global?

[Harald Hanche-Olsen]

[Leo <sdl.web@gmail.com> (2012-04-14 08:51:44 UTC)]

> As suggested in the subject.

No idea, but then again, I see no reason why it shouldn't be.
Maybe you could give some reasons why not?

- Harald

Re: why is which-function-mode global?

[Chong Yidong]

I assume it because if you want that functionality anywhere, you're like
to want it everywhere, so enabling it in individual buffers would be a
pain.

Nowadays it'd probably be handled with a buffer-local mode plus a
globalized mode, but I think it predates define-globalized-minor-mode.

Re: why is which-function-mode global?

[Andreas Röhler]

Am 14.04.2012 15:35, schrieb Chong Yidong:
> I assume it because if you want that functionality anywhere, you're like
> to want it everywhere, so enabling it in individual buffers would be a
> pain.
>
> Nowadays it'd probably be handled with a buffer-local mode plus a
> globalized mode, but I think it predates define-globalized-minor-mode.
>
>


IMO exist reasons to have it buffer-local rather.

Remember several reports of slowness from CEDET in past.

We have a similar situation now at python-mode.el, however with certain files only, i.e with very large definitions.

That might make Emacs slow, without user being aware of the reasons.

Cheers,

Andreas