-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
Configuration is case sensitive but many ssh versions aren't #51
Comments
Yes, I completely agree, I also made the mistake myself :) I will try to support insensitive keys or at least display warnings |
Awesome 👍 |
I opened an issue here: go-yaml/yaml#123 Depending on the resolution of this issue, I found an interesting alternative YAML library: https://github.com/BurntSushi/toml with case-insensitivity and more features |
YAML is case sensitive by spec, so I don't think they will accept it if they want to provide the smallest library parsing Yaml. Maybe they could offer it as a helper or something but seems unlikely I'd say. I'll keep in tune to see how it goes. Now, Toml is way way better for this case. I was thinking about it when I saw the error. It's not space sensitive and hence is less error prone, I'd give it a +10! |
I'm not fully convinced with the TOML alternative, see: https://github.com/moul/advanced-ssh-config/pull/62/files, especially https://github.com/moul/advanced-ssh-config/blob/fix-51/README.md#configuration What I suggest now is :
|
Here is another pull-request which add a yaml
This is trivial but seems to work quite well I think I can merge it for now, and remove this later @davidpelaez: what do you think/prefer ? |
I choose the |
@moul it works fine for me. It's simple yet clear. 👍 |
Loving this tool, thanks for releasing it! However, it did give me a minor headache when I started because it's case sensitive and doesn't complain about error. I suggest that the tool either complains about unknown keys or downcases all of them before using them. In my regular config file
Hostname
worked, but in assh you have to write itHostName
(capital N) or it won't work. This small mismatch with how things are handled by some versions of ssh could be annoying and unneeded friction.What do you think?
The text was updated successfully, but these errors were encountered: