App-FirefoxUtils
view release on metacpan or search on metacpan
* exclude_all_tags => *array[str]*
Exclude all items that have ALL tags specified.
* exclude_any_tags => *array[str]*
Exclude all items that have any tags specified.
* include_all_tags => *array[str]*
Include all items that have ALL tags specified.
* include_any_tags => *array[str]*
Include all items that have any tag specified.
* items* => *array[hash]*
(No description)
* kde_activity => *str*
Switch to the specified KDE activity.
* new_window => *bool*
(No description)
* query => *array[str]*
(No description)
* shuffle => *bool*
(No description)
Returns an enveloped result (an array).
First element ($status_code) is an integer containing HTTP-like status
code (200 means OK, 4xx caller error, 5xx function error). Second
element ($reason) is a string containing error message, or something
like "OK" if status is 200. Third element ($payload) is the actual
result, but usually not present when enveloped result is an error
response ($status_code is not 2xx). Fourth element (%result_meta) is
called result metadata and is optional, a hash that contains extra
information, much like how HTTP response headers provide additional
metadata.
Return value: (any)
pause_and_unpause_firefox
Usage:
pause_and_unpause_firefox(%args) -> [$status_code, $reason, $payload, \%result_meta]
Pause and unpause Firefox alternately.
A modern browser now runs complex web pages and applications. Despite
browser's power management feature, these pages/tabs on the browser
often still eat considerable CPU cycles even though they only run in the
background. Pausing (kill -STOP) the browser processes is a simple and
effective way to stop CPU eating on Unix and prolong your laptop battery
life. It can be performed whenever you are not using your browser for a
little while, e.g. when you are typing on an editor or watching a movie.
When you want to use your browser again, simply unpause (kill -CONT) it.
The "pause-and-unpause" action pause and unpause browser in an alternate
fashion, by default every 5 minutes and 30 seconds. This is a compromise
to save CPU time most of the time but then give time for web
applications in the browser to catch up during the unpause window (e.g.
for WhatsApp Web to display new messages and sound notification.) It can
be used when you are not browsing but still want to be notified by web
applications from time to time.
If you run this routine, it will start pausing and unpausing browser.
When you want to use the browser, press Ctrl-C to interrupt the routine.
Then after you are done with the browser and want to pause-and-unpause
again, you can re-run this routine.
You can customize the periods via the "periods" option.
This function is not exported by default, but exportable.
Arguments ('*' denotes required arguments):
* cmndline_pat => *re_from_str*
Filter processes using regex against their cmndline.
If one of the "*-pat" options are specified, then instead of the
default heuristic rules to find the browser processes, these "*-pat"
options are solely used to determine which processes are the browser
processes.
* exec_pat => *re_from_str*
Filter processes using regex against their exec.
If one of the "*-pat" options are specified, then instead of the
default heuristic rules to find the browser processes, these "*-pat"
options are solely used to determine which processes are the browser
processes.
* fname_pat => *re_from_str*
Filter processes using regex against their fname.
If one of the "*-pat" options are specified, then instead of the
default heuristic rules to find the browser processes, these "*-pat"
options are solely used to determine which processes are the browser
processes.
* periods => *array[duration]*
Pause and unpause times, in seconds.
For example, to pause for 5 minutes, then unpause 10 seconds, then
pause for 2 minutes, then unpause for 30 seconds (then repeat the
pattern), you can use:
300,10,120,30
* pid_pat => *re_from_str*
Filter processes using regex against their pid.
If one of the "*-pat" options are specified, then instead of the
default heuristic rules to find the browser processes, these "*-pat"
options are solely used to determine which processes are the browser
processes.
* users => *array[unix::uid::exists]*
Kill browser processes that belong to certain user(s) only.
Returns an enveloped result (an array).
First element ($status_code) is an integer containing HTTP-like status
code (200 means OK, 4xx caller error, 5xx function error). Second
element ($reason) is a string containing error message, or something
like "OK" if status is 200. Third element ($payload) is the actual
result, but usually not present when enveloped result is an error
response ($status_code is not 2xx). Fourth element (%result_meta) is
called result metadata and is optional, a hash that contains extra
information, much like how HTTP response headers provide additional
metadata.
Return value: (any)
pause_firefox
Usage:
pause_firefox(%args) -> [$status_code, $reason, $payload, \%result_meta]
Pause (kill -STOP) Firefox.
A modern browser now runs complex web pages and applications. Despite
browser's power management feature, these pages/tabs on the browser
often still eat considerable CPU cycles even though they only run in the
background. Pausing (kill -STOP) the browser processes is a simple and
effective way to stop CPU eating on Unix and prolong your laptop battery
life. It can be performed whenever you are not using your browser for a
little while, e.g. when you are typing on an editor or watching a movie.
When you want to use your browser again, simply unpause (kill -CONT) it.
This function is not exported by default, but exportable.
Arguments ('*' denotes required arguments):
* cmndline_pat => *re_from_str*
Filter processes using regex against their cmndline.
If one of the "*-pat" options are specified, then instead of the
default heuristic rules to find the browser processes, these "*-pat"
options are solely used to determine which processes are the browser
processes.
* exec_pat => *re_from_str*
Filter processes using regex against their exec.
If one of the "*-pat" options are specified, then instead of the
default heuristic rules to find the browser processes, these "*-pat"
options are solely used to determine which processes are the browser
processes.
* fname_pat => *re_from_str*
Filter processes using regex against their fname.
If one of the "*-pat" options are specified, then instead of the
default heuristic rules to find the browser processes, these "*-pat"
options are solely used to determine which processes are the browser
processes.
* pid_pat => *re_from_str*
Filter processes using regex against their pid.
If one of the "*-pat" options are specified, then instead of the
default heuristic rules to find the browser processes, these "*-pat"
options are solely used to determine which processes are the browser
processes.
* users => *array[unix::uid::exists]*
Kill browser processes that belong to certain user(s) only.
Returns an enveloped result (an array).
First element ($status_code) is an integer containing HTTP-like status
code (200 means OK, 4xx caller error, 5xx function error). Second
element ($reason) is a string containing error message, or something
like "OK" if status is 200. Third element ($payload) is the actual
result, but usually not present when enveloped result is an error
response ($status_code is not 2xx). Fourth element (%result_meta) is
called result metadata and is optional, a hash that contains extra
information, much like how HTTP response headers provide additional
metadata.
( run in 1.243 second using v1.01-cache-2.11-cpan-f56aa216473 )