Skip to content

Improve default options and behaviour. #131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 36 commits into from
Mar 21, 2025
Merged

Improve default options and behaviour. #131

merged 36 commits into from
Mar 21, 2025

Conversation

CogentRedTester
Copy link
Owner

This PR is to do a wide update of file-browsers default options and behaviour
to make things more user friendly.

File-browser is several years old now, and in that time there are some legacy options
that can be improved, and some experimental features that now provide a superior
experience.

This removes the LuaJit requirements.

This is still rather experimental, so there may be bugs that appear when
parsing non-spec UTF16 strings (which Windows apparently supports in
filepaths!?).
To address this the parser is set to throw errors on any invalid input.
If an error is thrown the parser will abort and file-browser will
fallback to the default parser.
No longer throw an error if the directory cannot be read,
just make a verbose log message.
No longer throws an error if the custom keybind file is not found,
send a verbose log message instead.

Invalid syntax in the keybind file still throws an error.
The keybind system sends arguments to the callback function, which was
messing with the rescan function.
Some people seem to treat this file as a set of defaults despite the
installation instructions explicitly saying not to. To avoid people
shooting themselves in the foot all of the less useful keybinds, and the
keybinds that will fail if used on the wrong OS or without the
required commandline tools, have been removed.
@CogentRedTester CogentRedTester merged commit 474b440 into master Mar 21, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant