All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
These are not completely removed yet, but will be in version 2.0.0.
tb2
CONFIG support. Affected user.js
es can only be updated by using -c
.-s
option. Switch to -u
.main
. Versions prior to 1.3.0 can only be updated manually.eval
commandfirefox/profiles.ini
getting basically parsed twice if thunderbird was not installed.-g
option: You can now specify a path to a user overrides file or directory which will be applied to every Firefox profile. If it's a directory every file in it that ends on .js
will be applied. If you use the default path ~/.mozilla/firefox/global-user-overrides.js
you don't even need to use this option explicitly.empty
config: You may now specify -c empty
on a profile which creates a basically empty user.js
. User overrides are still appended so you can solely apply your (global) user overrides to a profile – without a user.js
template from anywhere.-c
option: arkenfox
(Firefox) and HorlogeSkynet
(Thunderbird) are now available-r
failing because some other, in that case not even needed function failed early-i
opening an empty file because the script exited and deleted the user.js
faster than the system open command opened itmedium
config. It's called medium streng in Privacy-Handbuch, streng
corresponds to sehr streng.user.js
and the updater itself during updatescompatibility.ini
for a first Firefox user.js
in a profile if -e
is not useduser.js
installation may be confirmed with j/J-t
option: Dry-run – Do a trial run without actual changes but mostly the same output-q
option: Quieter – Print less output for every given q (up to 4 for complete silence)-e
> previous user.js
> compatibility.ini
> firefox --version
stderr
user.js
only gets installed if it is different (overrides are taken into account)user.js
update now is also confirmed by just hitting return-i
) will open the new user.js
before you are asked for confirmation. Also you won't even be bothered with the confirmation dialogue if user.js
es are identical.tb-streng
user.js
could not be parseduser-overrides.js
user.js
version extraction failed due to new layout by Privacy-Handbuchtb-streng
config-b
and -d
options doing the opposite of what is stated in the usage text-a
option: update all Thunderbird and Firefox profiles (in standard locations) with already existing user.js
es.-e
option now supports 0
to force release variant of user.js
-v
option: display versionuser.js
download; precedence now is: -e
option > read from user.js
> firefox --version
> release (fallback)tb2
CONFIG support-s
: Switch to -u
! Update options are used consciously. Asking for another confirmation is thus pointless. Both options are synonymous now (silent), but -s
will be removed eventually.PATH
variable-l
output for more claritymain
-c
argumentsfirefox --version
check with firejailfirefox --version
fails because Firefox is not installed (thunderbird only usage)user.js
es; an ESR and a release one-v
option is renamed to -i
("inspect")user.js
URL-p
paths plus the one selected with -l
)-l
and -p
in conjunctionstdout
is not a terminal