setting about:config entries via findbar
should not accept a "nul" response as a 0 (or default)
as it is, i often forget the syntax (to view a setting)
so if i type
/zoom
i get zoom=134
/zoom=
RESETS ZOOM TO DEFAULT
so now i have to remember if i need to include the = in my query or not
imo, it would be better to force the user to specifically include some
value after the = in order to force a change; so /zoom=0 (or /zoom=100)
Vim:
set tw=
E521: Number required after =: tw=
setting about:config entries via findbar
Re: setting about:config entries via findbar
I will consider enforcing a number after the =
Thank you for the suggestion.
Thank you for the suggestion.
Re: setting about:config entries via findbar
I'm confused. Isn't the purpose of supplying a naked (no value) "=" after any setting supposed to revert the setting to its default value? Wouldn't the requirement of a value prevent this?
Re: setting about:config entries via findbar
Yes.
And yes.
IMO, rather then resetting a Pref back to default (when given a "nul" value), a user should specifically be required to enter a value - such that not entering a value does not reset to default.
To me, it is "safer" that way.
And yes.
IMO, rather then resetting a Pref back to default (when given a "nul" value), a user should specifically be required to enter a value - such that not entering a value does not reset to default.
To me, it is "safer" that way.
I don't know "supposed", but it does.supposed
Re: setting about:config entries via findbar
In that case, I will just adamantly disagree and discourage @void from making in any change to this behavior.
If you want to see what the current value is for a setting, omit the "=" sign entirely. Resist the urge to type it.
If you want to change the value of a setting, then go ahead and use that "=" sign. Blank resets the value to default.
If you want to see what the current value is for a setting, omit the "=" sign entirely. Resist the urge to type it.
If you want to change the value of a setting, then go ahead and use that "=" sign. Blank resets the value to default.
Re: setting about:config entries via findbar
It has nothing to do with resisting, it has to do with remembering (if you should include the = or not ) .
Re: setting about:config entries via findbar
I mean, that sounds more like a hint that it's time to retire and enjoy the warm glow of your sunset years, than an actual flaw in the software.
Manually editing the ini/settings via notepad or command are considered "for expert users only" and "advanced tinkering and hacking," not intended for the faint of heart or mind. ¯\_(ツ)_/¯
You propose to diminish the capabilities of this advanced feature by prohibiting the setting of default values.
Manually editing the ini/settings via notepad or command are considered "for expert users only" and "advanced tinkering and hacking," not intended for the faint of heart or mind. ¯\_(ツ)_/¯
You propose to diminish the capabilities of this advanced feature by prohibiting the setting of default values.
-
- Posts: 495
- Joined: Thu Dec 15, 2016 9:44 pm
Re: setting about:config entries via findbar
To me having an = after a value indicates it's being set to something, rather than viewed.
If there's a problem, such as too much similarity, maybe ? could also (as well as the existing) be used for viewing, e.g.
/zoom?
/?zoom
these could actually be combined so
/?zoom=200
would popup the current value and ask if you want to change it to 200
whereas /zoom=200
could directly set it
Those who needed it could then habituate to using a ?
d
If there's a problem, such as too much similarity, maybe ? could also (as well as the existing) be used for viewing, e.g.
/zoom?
/?zoom
these could actually be combined so
/?zoom=200
would popup the current value and ask if you want to change it to 200
whereas /zoom=200
could directly set it
Those who needed it could then habituate to using a ?
d
Re: setting about:config entries via findbar
= should be used when the intent is to assign a value.
I find an empty value after = to set the default very useful.
The Everything.ini shares this same syntax.
Maybe a config audit would be useful?
Maybe showing the previous value in the statusbar would help? eg: Changed zoom from 134 to 100.
I would like to keep a backup of your Everything.ini around.
I have on my TODO list to treat your Everything.ini as invalid if it contains NUL characters.
Everything would load your backup ini if the main one is invalid.
You could then compare values against the backup ini.
Help -> Troubleshooting Information will show all your changed settings.
Note: There's currently a bug in 1331 where the changed settings don't show unless the debug console window is shown (Tools -> Debug -> Console)
I find an empty value after = to set the default very useful.
The Everything.ini shares this same syntax.
Maybe a config audit would be useful?
Maybe showing the previous value in the statusbar would help? eg: Changed zoom from 134 to 100.
I would like to keep a backup of your Everything.ini around.
I have on my TODO list to treat your Everything.ini as invalid if it contains NUL characters.
Everything would load your backup ini if the main one is invalid.
You could then compare values against the backup ini.
Help -> Troubleshooting Information will show all your changed settings.
Note: There's currently a bug in 1331 where the changed settings don't show unless the debug console window is shown (Tools -> Debug -> Console)