add an option to disable refreshing fset for some option name #1553
Comments
flashcode
added a commit
that referenced
this issue
Aug 20, 2020
emilford
added a commit
to emilford/dotfiles
that referenced
this issue
Nov 26, 2020
When an option is modified, the fset buffer is refreshed. This can have undesirable side-effects (e.g., CPU spike) when a trigger exists that modifies options at a frequent rate (e.g., every second). An option was introduced in Weechat 3.0 to set a command separated list of options to automatically refresh on the fset buffer. "*", the default and the recommended value, refreshes all options. "!" also exists as a negative value to prevent an option from being refreshed. weechat/weechat#1553 https://weechat.org/files/changelog/ChangeLog-3.0.html#v3.0
emilford
added a commit
to emilford/dotfiles
that referenced
this issue
Dec 5, 2020
When an option is modified, the fset buffer is refreshed. This can have undesirable side-effects (e.g., CPU spike) when a trigger exists that modifies options at a frequent rate (e.g., every second). An option was introduced in Weechat 3.0 to set a command separated list of options to automatically refresh on the fset buffer. "*", the default and the recommended value, refreshes all options. "!" also exists as a negative value to prevent an option from being refreshed. weechat/weechat#1553 https://weechat.org/files/changelog/ChangeLog-3.0.html#v3.0
emilford
added a commit
to emilford/dotfiles
that referenced
this issue
Dec 5, 2020
When an option is modified, the fset buffer is refreshed. This can have undesirable side-effects (e.g., CPU spike) when a trigger exists that modifies options at a frequent rate (e.g., every second). An option was introduced in Weechat 3.0 to set a command separated list of options to automatically refresh on the fset buffer. "*", the default and the recommended value, refreshes all options. "!" also exists as a negative value to prevent an option from being refreshed. weechat/weechat#1553 https://weechat.org/files/changelog/ChangeLog-3.0.html#v3.0
emilford
added a commit
to emilford/dotfiles
that referenced
this issue
Dec 5, 2020
When an option is modified, the fset buffer is refreshed. This can have undesirable side-effects (e.g., CPU spike) when a trigger exists that modifies options at a frequent rate (e.g., every second). An option was introduced in Weechat 3.0 to set a command separated list of options to automatically refresh on the fset buffer. "*", the default and the recommended value, refreshes all options. "!" also exists as a negative value to prevent an option from being refreshed. weechat/weechat#1553 https://weechat.org/files/changelog/ChangeLog-3.0.html#v3.0
emilford
added a commit
to emilford/dotfiles
that referenced
this issue
Dec 5, 2020
When an option is modified, the fset buffer is refreshed. This can have undesirable side-effects (e.g., CPU spike) when a trigger exists that modifies options at a frequent rate (e.g., every second). An option was introduced in Weechat 3.0 to set a command separated list of options to automatically refresh on the fset buffer. "*", the default and the recommended value, refreshes all options. "!" also exists as a negative value to prevent an option from being refreshed. weechat/weechat#1553 https://weechat.org/files/changelog/ChangeLog-3.0.html#v3.0
emilford
added a commit
to emilford/dotfiles
that referenced
this issue
Dec 6, 2020
When an option is modified, the fset buffer is refreshed. This can have undesirable side-effects (e.g., CPU spike) when a trigger exists that modifies options at a frequent rate (e.g., every second). An option was introduced in Weechat 3.0 to set a command separated list of options to automatically refresh on the fset buffer. "*", the default and the recommended value, refreshes all options. "!" also exists as a negative value to prevent an option from being refreshed. weechat/weechat#1553 https://weechat.org/files/changelog/ChangeLog-3.0.html#v3.0
emilford
added a commit
to emilford/dotfiles
that referenced
this issue
Jan 9, 2021
When an option is modified, the fset buffer is refreshed. This can have undesirable side-effects (e.g., CPU spike) when a trigger exists that modifies options at a frequent rate (e.g., every second). An option was introduced in Weechat 3.0 to set a command separated list of options to automatically refresh on the fset buffer. "*", the default and the recommended value, refreshes all options. "!" also exists as a negative value to prevent an option from being refreshed. weechat/weechat#1553 https://weechat.org/files/changelog/ChangeLog-3.0.html#v3.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature description
As stated on #weechat-fr, whenever an option is modified, the fset buffer is refresh. When you have a trigger or something that modify an option like every second, the cpu usage get crazy
An option to disable some options from refreshing fset would be useful
The text was updated successfully, but these errors were encountered: