Joseph Wright
Joseph Wright
The major use case for groups is where keys need to be at the same path level but need to be set in order - you can then do then...
> OK. to a point... I found out about the 'non error' trying to track a bug in a personal package... I ended breaking down my key tree in 2...
BTW, in general I'd expect keys to be a poor internal choice: they are really a friendly interface thing but at the code level can never compete with simply setting...
> Though (and I know TeX doesn't have to concept or support for namespaces) it would be nice to be able to have a public/private concept for keys. For `l3keys`,...
> > > Though (and I know TeX doesn't have to concept or support for namespaces) it would be nice to be able to have a public/private concept for keys....
Before adjusting the text, I'll see if there are other views on the behaviour.
Like things like colours and messages, key definitions all 'live' in one place and we have no way of knowing the local/global status from the names - nor could we...
I'm going to close here not-planned - it really doesn't fit with the scoping model in `expl3`.
You can create a file `_sass/hamilton/custom-styles.scss` containing ```css .site-main { scrollbar-width: auto; } ``` to reset the behaviour.
That's true (or at least there is no convenient way), but then I've never come across a case where it was needed: can you point to one?