Open psprint opened 1 year ago
I've also updated README.
@jankatins : I've added an example of named dir. Thanks
As mentioned in https://github.com/zdharma-continuum/zinit/pull/378, I have questions about introducing named directories as a core feature.
Such "something useful" should be realized as a plugin, not as a part of zinit itself. Convenience can be achieved through plugins, but simplicity is not.
Such "something useful" should be realized as a plugin, not as a part of zinit itself. Convenience can be achieved through plugins, but simplicity is not.
I've never wrote "something useful". And the hypothetical plugin would be an EMPTY one (1 line of code), to provide for zinit, which knows the paths best and owns them, so it should manage to label them via named dirs. Otherwise it would be laughable.
I've no interest in future argument. I think that it is clear that Zinit should provide for itself, especially as it is single line of code, and I hope that other developers agree with me like @jankatins apparently is.
I stoped using them again because I found typing ~
on a mac too much pain :-/. Went back to use making aliases cdx
for all my relevant dirs I need... The rest is in mcfly/ctrl+r
Description
Remove global aliases because their limited use (
ZIDIR/…
isn't working) and replacetypeset -g …
withhash -d …
so that the named directories are completed. Eg.:~ZI<tab>
looks like:Motivation and Context
As in #378.
Related Issue(s)
378.
Usage examples
How Has This Been Tested?
Types of changes
Checklist: