A few changes. Would also like some preferences as some of the current changes could be seen as a forced change.
Autocomplete for zshell-cli commands in general. Check here for an example:
This would apply to all non flag commands. A flag will give autocomplete suggestions once the user inputs a -. Example here:
Fixed some pyright/ruff type errors
Pillow had some deprecated syntax, resolved them.
Preference question
In this current code, the first zshell-cli command auto installs autocompletion and writes (into) two files. While convenient to me, this could be frowned upon that it writes into files without intentional user input. An alternative could be a hint message or a first time zshell-cli prompt to install autocomplete (only once). If this is preferred, I will adjust.
### Changes
A few changes. Would also like some preferences as some of the current changes could be seen as a forced change.
- Autocomplete for `zshell-cli` commands in general. Check here for an example: 
This would apply to all non flag commands. A flag will give autocomplete suggestions once the user inputs a `-`. Example here:

- Fixed some pyright/ruff type errors
- Pillow had some deprecated syntax, resolved them.
### Preference question
In this current code, the first zshell-cli command auto installs autocompletion and writes (into) two files. While convenient to me, this could be frowned upon that it writes into files without intentional user input. An alternative could be a hint message or a first time zshell-cli prompt to install autocomplete (only once). If this is preferred, I will adjust.
Closes #100
Personally think we should have it as a command like zshell-cli install-completion or similar, and then inform users about it in the project's readme. This is very useful and I like the changes, but I also want the CLI tool to be as unobtrusive as possible. It's really only meant to be used manually by people working on the shell or tool itself.
Personally think we should have it as a command like `zshell-cli install-completion` or similar, and then inform users about it in the project's readme. This is very useful and I like the changes, but I also want the CLI tool to be as unobtrusive as possible. It's really only meant to be used manually by people working on the shell or tool itself.
@zach since you did not leave a "review", @ing you instead. Changes are made. I did add a tip if autocomplete is not installed. Should not be of any harm.
@zach since you did not leave a "review", @ing you instead. Changes are made. I did add a tip if autocomplete is not installed. Should not be of any harm.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Changes
A few changes. Would also like some preferences as some of the current changes could be seen as a forced change.
zshell-clicommands in general. Check here for an example:This would apply to all non flag commands. A flag will give autocomplete suggestions once the user inputs a
-. Example here:Preference question
In this current code, the first zshell-cli command auto installs autocompletion and writes (into) two files. While convenient to me, this could be frowned upon that it writes into files without intentional user input. An alternative could be a hint message or a first time zshell-cli prompt to install autocomplete (only once). If this is preferred, I will adjust.
Closes #100
Personally think we should have it as a command like
zshell-cli install-completionor similar, and then inform users about it in the project's readme. This is very useful and I like the changes, but I also want the CLI tool to be as unobtrusive as possible. It's really only meant to be used manually by people working on the shell or tool itself.Ill look into it and make the changes.
@zach since you did not leave a "review", @ing you instead. Changes are made. I did add a tip if autocomplete is not installed. Should not be of any harm.