[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Finding packages to enable by default
From: |
Tom |
Subject: |
Re: Finding packages to enable by default |
Date: |
Tue, 3 Dec 2013 17:05:42 +0000 (UTC) |
User-agent: |
Loom/3.14 (http://gmane.org/) |
Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
>
> Maybe we should look at it the other way: what do we want to use this for?
> IIUC the idea was to try and decide what features to enable by default.
> So, how can we recognize a "feature to enable"?
> Major modes associated to file names don't really fit our needs,
> for example. Applications like Gnus, Ediff, or Org don't either.
We have the list of features enabled in user configs compiled from the bug
reports.
The ideas was to filter out all the default/supporting features from this
list and then we're left with features which can be enabled.
I did some manual filtering as a test and here are some of the top packages
which remained:
(ido . 137)
(uniquify . 136)
(imenu . 114)
(eldoc . 113)
(ispell . 107)
(flyspell . 91)
(recentf . 90)
(saveplace . 77)
(yasnippet . 75)
(windmove . 70)
(auto-complete . 66)
(delsel . 64)
(paredit . 49)
(iswitchb . 46)
(savehist . 43)
(linum . 38)
(icomplete . 34)
(winner . 34)
(hippie-exp . 32)
(ibuffer . 29)
...
As you can see uniqify is there.
Ido is at the top (iswitchb is also here) and ido/isiwtchb would really
make a much better first impression for new users than the default
very barebone buffer switching.
recentf/saveplace/savehist are all great improvements. They could be
enabled by default.
winner/windmove suggest the default window movement is not very
convenient.
Of course, this package measurement should be repeated with
representative data, but even with the data acquired from bug reports
it gives some ideas for packages which could be enabled by default.
- Re: Finding packages to enable by default, Tom, 2013/12/01
- Re: Finding packages to enable by default, Jambunathan K, 2013/12/01
- Re: Finding packages to enable by default, Stefan Monnier, 2013/12/01
- Re: Finding packages to enable by default, Tom, 2013/12/01
- Re: Finding packages to enable by default, Stefan Monnier, 2013/12/01
- Re: Finding packages to enable by default, Tom, 2013/12/02
- Re: Finding packages to enable by default, Stefan Monnier, 2013/12/02
- Re: Finding packages to enable by default,
Tom <=
- RE: Finding packages to enable by default, Drew Adams, 2013/12/03
- Re: Finding packages to enable by default, Tom, 2013/12/03
- RE: Finding packages to enable by default, Drew Adams, 2013/12/03
- Re: Finding packages to enable by default, Tom, 2013/12/03
- [RFC] Micro-Init files in GNU ELPA & Survey suggestions(Re: Finding packages to enable by default), Jambunathan K, 2013/12/03
- Re: [RFC] Micro-Init files in GNU ELPA & Survey suggestions(Re: Finding packages to enable by default), Tom, 2013/12/03
- Re: [RFC] Micro-Init files in GNU ELPA & Survey suggestions(Re: Finding packages to enable by default), Jambunathan K, 2013/12/04
- Re: [RFC] Micro-Init files in GNU ELPA & Survey suggestions(Re: Finding packages to enable by default), Jambunathan K, 2013/12/04
- Re: [RFC] Micro-Init files in GNU ELPA, Ted Zlatanov, 2013/12/04
- Re: [RFC] Micro-Init files in GNU ELPA, Ted Zlatanov, 2013/12/04