[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: scratch/command 064f146 1/2: Change command to interactive ... modes
From: |
Juri Linkov |
Subject: |
Re: scratch/command 064f146 1/2: Change command to interactive ... modes |
Date: |
Wed, 17 Feb 2021 19:45:10 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) |
>>>> As for verbosity, it's not like there weren't any suggestions to
>>>> reduce the number of annotations either (like tying command
>>>> definitions to packages, or custom groups, etc).
>>>
>>> And I responded to all of those and said why I thought those were bad
>>> ideas.
>>
>> Then why we are removing :group tags from defcustom? Because they are
>> redundant.
>> Completion annotations are redundant the same way.
>
> Not exactly in the same way, because the overwhelmingly most common case
> with :group tags is that all defcustoms in one file share the same group.
>
> With completion annotations, we have seen ratios from 50-75 %.
I don't know where you see such low ratios. In a typical package like
gomoku.el there are 16 commands tagged with 'gomoku-mode', and 2 untagged.
This is 90% vs 10%.
It makes more sense to make tagging opt-out, i.e. to tag the whole package
like defgroup does. Then tag only a few commands available globally.
Usually most commands in a package are internal, only a few of commands are
entry points. Package entry points are usually tagged with the autoload cookie.
So only 10% of entry points need the `declare' tag, other 90% don't need any
tagging.
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, (continued)
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Eli Zaretskii, 2021/02/16
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Lars Ingebrigtsen, 2021/02/16
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Dmitry Gutov, 2021/02/16
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Lars Ingebrigtsen, 2021/02/16
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Dmitry Gutov, 2021/02/16
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Lars Ingebrigtsen, 2021/02/17
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Dmitry Gutov, 2021/02/17
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Juri Linkov, 2021/02/17
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Stefan Kangas, 2021/02/17
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Lars Ingebrigtsen, 2021/02/17
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes,
Juri Linkov <=
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Óscar Fuentes, 2021/02/17
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Stefan Kangas, 2021/02/17
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Stefan Monnier, 2021/02/17
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Eli Zaretskii, 2021/02/17
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Dmitry Gutov, 2021/02/17
- RE: [External] : Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Drew Adams, 2021/02/16
- RE: [External] : Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Matt Armstrong, 2021/02/17
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Alan Mackenzie, 2021/02/16
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Lars Ingebrigtsen, 2021/02/16
- Re: scratch/command 064f146 1/2: Change command to interactive ... modes, Alan Mackenzie, 2021/02/16