Updates the set command to disallow configlocation and updates associated man apge entry #96

sloum · 2019-11-18T23:47:48Z

sloum commented

2019-11-18 23:47:48 +00:00

If a user tries to :set configlocation x to any value for x they will get error messaging letting them know that they tried to set a read only setting. The man page was updated with the configlocation setting. In the entry it lists it as readonly, but points out that check can still be used with it to read its value.

I avoided adding extra language to the man page about setting the value in defaults.go prior to compile out of a belief that build instructions are largely out of scope for an application man page. Let me know if you think differently (or feel free to update the text, either way is good by me).

If a user tries to `:set configlocation x` to any value for x they will get error messaging letting them know that they tried to `set` a _read only_ setting. The man page was updated with the `configlocation` setting. In the entry it lists it as readonly, but points out that `check` can still be used with it to read its value. I avoided adding extra language to the man page about setting the value in defaults.go prior to compile out of a belief that build instructions are largely out of scope for an application man page. Let me know if you think differently (or feel free to update the text, either way is good by me).

sloum added this to the 2.0.0 milestone 2019-11-18 23:47:48 +00:00

sloum added the

bug

enhancement

documentation

labels 2019-11-18 23:47:48 +00:00

asdf approved these changes 2019-11-19 00:06:53 +00:00

asdf closed this pull request

2019-11-19 00:07:30 +00:00

asdf deleted branch config-loc

2019-11-19 00:07:36 +00:00

asdf referenced this pull request