-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't overwrite the users variables #6
Comments
Example:
|
Indeed. The same would be with |
Well, it will not work for the variable I think the easiest solution for By the way, I'm really grateful for finding this old issue, I should start fixing things for this project. :) |
Sure, I will do that. : ) |
That's awesome! Just say if you want any help, and I have a complete test-suite as well, so don't be afraid that things might break. :) |
Argh, I just got bitten by this myself, I guess I should update my own software! :) |
@Tarrasch I don't see why we need |
I find it unintuitive. Also we want to highlight that we're dealing with "special" syntax.
Maybe. I haven't touched this in a while. Do you mind trying it out? If so please remember test cases! |
I find “$1” very intuitive 😆
Don’t count on me for fixing the X bug anytime soon, I won’t get to it if
it doesn’t cause me problems.
…On Sat, Oct 20, 2018 at 9:46 PM Arash Rouhani ***@***.***> wrote:
What's wrong with $1?
I find it unintuitive. Also we want to highlight that we're dealing with
"special" syntax.
Anyways, can't you use local x in the internals?
Maybe. I haven't touched this in a while. Do you mind trying it out? If so
please remember test cases!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#6 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Aii--lla9iXlkd-QfFjkXRfmjjc53YhKks5um2higaJpZM4AfNjI>
.
|
Currently, if a user of zsh-functional has the shell variable
x
defined, it'll be rewritten by some temporary value by the internals of zsh-functional.The text was updated successfully, but these errors were encountered: