-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On June 4, 2014 4:28:31 PM GMT+03:00, Kai Weber <kai.we...@glorybox.de> wrote: >❦ Thomas Bondo Homburg <thomas.homb...@gmail.com>: > >> When I type a colon, the current line is unindented immediately. > >Same problem here. > >I tried the following plugin and it works well. >https://github.com/chase/vim-ansible-yaml > >I am still not convinced wether indent/yaml.vim is wrong or ansible. I >read >about the nested dicts problem in the Salt documentation >http://docs.saltstack.com/en/latest/topics/troubleshooting/yaml_idiosyncrasies.html They blame YAML for its features, spread FUD like YAML supporting only ASCII (even YAML-1.0 required UTF-8 or UTF-16 string, -1.2 allows UTF-8, -16 and -32, with additional requirement for the first character being ASCII in case of UTF-8) and do not know the instrument they are using (automatic string to something conversion is easily disablable if you override one class variable by subclassing Loader and this does not contradict with YAML documentation as this variant is named "failsafe schema" and YAML parser "should" support this "at least as an option": failsafe schema only supports mappings, sequences and strings (for values without an explicit tag)). Their "double short decs" is a huge "success": I do not know what hacks they have coded for supporting "single short decs", but based on their third example I think all they needed was foo: bar: baz: in place of foo: bar baz . Knowledge of the YAML spec is certainly not their strong point. You should not trust Salt developers on this matter. I would not trust Salt developers at all anymore though. -----BEGIN PGP SIGNATURE----- Version: APG v1.1.1 iQI1BAEBCgAfBQJTjy3MGBxaeVggPHp5eC52aW1AZ21haWwuY29tPgAKCRCf3UKj HhHSvgrsD/4ms1lGQnkHjaRWWkPpzYXfYwZclvWORjbBAmSQzgydfdVbedE/HbtD xGeJ3pY2/xRyU7oht2Dno3WySLvyHTiYgqjvme1zaLnBaUa0u7QN/k486uZloPWH xvv2MG79VbaHcogr2Qsdw2L9lBQ61XOByKwIxhnpe3LUIbdBk5K07FodF5kk/eGm WbcEaNo0JrSs9U3+5+tgRgzSUE8XyYexK5A+VVdY8/9ptUYcNjCpszUJq5stIJq9 75oZqXp0bcdXxXLw1hdQOmAJZ8EPQoEmEK6Ckvr3RaGDFG43s3HMtSIc8xvbpErv UmLVa1ky6QzO924CFOceLW9FgPX/Hf8HlAwhGV3P25R+UPOVe3GPT2xpH44LPM2W XKMCSR9G59rDM0vekPko/6tLqEBHz3i8ZXGfBtZxAUPN9tkyiDGeU6EAOltAhp1C 9pqC5DzZby8i5iCY2Z3SDUoYXwC1BA1rIKZzllHp+n3N6qHmeTut1Hi6/9d4vQQL a4+lWL8tW/gVuvUaImaOezm+G7siWz19nuKlJ9hCWM+xa4xMlQDgZYCa4lEDROtr dCF3f5jtP5DUjgM0zFqEcQNDIOu+V8SlXhFnHS6BBt/rOhCX1PGrLsKoVRDRleDs 55tzRNMzwL6/2AUfroP9krwLND6Di6V+BcvLz3h1JW0cR3eQ3LUwMw== =3a+s -----END PGP SIGNATURE----- -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
