Fabian Boehm

>definitely worth adding something in the release notes Got an idea for the wording? How about something like """ Currently, conf.d snippets are sourced in ~/.config/fish first, then in /etc/fish...

>This is really something not working as intended, I think it's a bug. Or if it was intended this way, certainly a misfeature. It works as written and documented, that...

Okay. I would then simply punt this entirely to after 3.4. Not even a notice there, because we're not 1000% sure on what the new behavior would look like.

Okay, so there's two plausible sort orders: 1. Go through directories, from least to most important, and source every file that isn't in any of the later dirs. This is...

#8265 now has the elements to implement the interleaved version easily in script: ```fish for file in (path sort --what=basename --unique --null-out $__fish_config_dir/conf.d/*.fish $__fish_sysconf_dir/conf.d/*.fish $vendor_confdirs/*.fish \ | path filter -rf...

>Putting aside those that should really be _fish* functions, They should not. They're for use by normal users, so they should just be called `fish_`. If anything, we're overusing dunderscores....

>seq.fish should really probably just be put out to pasture If you want to abandon OpenBSD support,... >nextd-or-forward-word.fish, up-or-search.fish, … I really hate these readline functions that are effectively "hanging...

I don't see how this helps. It's an inconsistency, for very little gain. You can see for yourself - the screenshot does use "half" of the space for the prefix,...

>Hopefully it's not too controversial to say that the first is objectively worse than the latter here It is, I do not believe it is worse at all. The first...

> I'm suggesting, if you ask the majority of people Voting isn't a good way to make design decisions. >Literally over 50% of it is the same duplicate text If...