![]() ![]() `keybindings.nu`, `hooks.nu`, `themes/my-theme-dark.nu`)Įasy orderable parts and hard to order parts (`NU_LIB_DIRS`, `ENV_CONVERSIONS`)Īs mentioned last meeting: Path/PATH conversions for a bunch of variables (currently special sauce) We want to be able to break the config into easily digestable chunks (e.g. Scripted config (much greater flexibility but some challenges and order matters much more plus cost of evaluation) Have an easy understandable logic to understand how configuration is loaded with good default experience without needing a PhD to configure nushell > could we bridge the difference or make it more easy to understandĬurrent configs grow really large and get messy (error messages are hard)Īlso handling of fall-back default config if user deletes config or if config is broken Kubouchs problem two separate config files: `env.nu` and `config.nu` ![]() * The vscode nushell extension PR is going to be epic! ĭarren's comparison of different possible paths * Hopefully Windows Terminal flickering will soon be a thing of the past. * The rest of the older PRs probably need another look at and ping the OP to see if we need to close them or if they still plan on working on them. IMO this was a successful experiment and a nice performance improvement, but it's OK if we decide that this isn't the right long-term approach. * Reilly: I'm OK if we decide that we don't want another Value variant. we have too much of it already, adds another combination of config to test * Reilly: would vote against configuration. * str length, str substring, str index-of and split chars now use graphemes instead of UTF-8 bytes - It seems like we've reached a tipping point where we mostly agree that a `-grapheme(-g)` flag should be used but the further discussion suggested by Leon is to make the default bytes vs grapheme configurable. ![]() * Fixes shell crashing because alias name is shorter than alias command and there are pipes present. * Remove deprecated -numbered flag from five commands * convert SyntaxShape::Table into the corresponding Type * add dedicated const in pipeline, const builtin var errors Darren's attempt to spawn ideas fell short here * Further discussion on a new nushell config system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |