Presumably the hotkey file is textual. I would prefer Full also, but a
way to have both the benefits of both Sparse and FULL files is to list
everything, but comment out the entries which are still the default. So
the file shows exactly whats been changed, AND what all the
possibilities are.
+1
On 6/7/19 1:25 PM, Seth Hillbrand wrote:
> +1
>
> On 2019-06-07 12:46, Jon Evans wrote:
>> I vote "full", because I'd rather not have to look two places to see
>> what's what.
>>
>> On Fri, Jun 7, 2019 at 12:40 PM Jeff Young wrote:
>>
>>> Individual hotkey config files need to be able to be
+1
On 2019-06-07 12:46, Jon Evans wrote:
I vote "full", because I'd rather not have to look two places to see
what's what.
On Fri, Jun 7, 2019 at 12:40 PM Jeff Young wrote:
Individual hotkey config files need to be able to be sparse. So for
instance an “Eagle HotKeys” file can specify just
I vote "full", because I'd rather not have to look two places to see what's
what.
On Fri, Jun 7, 2019 at 12:40 PM Jeff Young wrote:
> Individual hotkey config files need to be able to be sparse. So for
> instance an “Eagle HotKeys” file can specify just those ACTIONs it wanted
> to match with
Individual hotkey config files need to be able to be sparse. So for instance
an “Eagle HotKeys” file can specify just those ACTIONs it wanted to match with
Eagle. The user can then read as many of these as they like.
But what about the “standard” user config file where we store hotkey
5 matches
Mail list logo
