- Library users please refer to the latest API docs and examples.
- New homepage: https://xplr.dev
<sub>Like this project so far? **[Please consider contributing][5]**.</sub>
#### [v0.13.7][2] -> [v0.14.7][3]
- macOS users need to place their config file (`init.lua`) in
@ -64,9 +84,8 @@ compatibility.
- Since version `v0.14.6`, the `-C` or `--extra-config` CLI argument is
available.
<sub>Like this project so far? **[Please consider contributing][5]**.</sub>
#### [v0.12.1][6] -> [v0.13.7][2]
- Lua functions called using [`CallLua`][7] and [`CallLuaSilently`][8] messages will receive [`CallLuaArg`][9] object as the function argument (instead of the [`App`][10] object).
- Each `node_types` config will inherit defaults from matching less specifig `node_types` config and overwrite them.
- Since version `v0.13.2`, you don't need to use/send `Refresh` anymore. It will be auto-handled by xplr.
@ -158,7 +177,6 @@ Else do the following
#### [v0.4.2][27] -> [v0.4.3][26]
If you have customized `general.table.row.cols`, you might want to [update it][28] to use the new variables with better symlink support.
#### [v0.4.1][29] -> [v0.4.2][27]
@ -169,7 +187,7 @@ In case you have mapped the keys `q`, `ctrl-i` and `ctrl-o`, you may want to rev
A lot has changed (apologies). But I promise from now on, upgrading will be much less painful (thanks to [@maximbaz][31]'s valuable [inputs][32] and [code reviews][33]).
So, to start with the upgrade, let's remove everything from your config file except the `version` field and your custom modifications. If `version` is the only thing remaining, update it to `v0.4.1` and you are done.
So, to start with the upgrade, let's remove everything from your config file except the `version` field and your custom modifications. If `version` is the only thing remaining, update it to `v0.4.1` and you are done.
Else, do the following
@ -182,6 +200,7 @@ Else, do the following
- Finally, update the `version` to `v0.4.1`.
#### [v0.3.8][40] -> [v0.3.13][30]
Your current config should work fine. However, you might want to replace some `Call` and `BashExec` messages with `CallSilently` and `BashExecSilently` to remove the flickering of the screen.
If you haven't made any changes to the configuration, you can delete and regenerate it.
@ -209,6 +228,7 @@ Else, do the following
If you haven't made any changes to the configuration, you can delete and regenerate it.
Else do the following:
- `$XPLR_APP_YAML` has been removed. You can use `Debug` to export the app state.
- `$XPLR_RESULT` has been ported to file `$XPLR_PIPE_RESULT_OUT`. Use `cat` instead of `echo`, `<` instead of `<<<` etc.
- `$XPLR_GLOBAL_HELP_MENU` has been ported to
@ -219,46 +239,46 @@ Else do the following:
- `$XPLR_PIPE_RESULT` has been ported to file `$XPLR_PIPE_RESULT_OUT`. Use `cat` instead of `echo`, `<` instead of `<<<` etc.
- Finally, update the `version` in your config file.
Arijit Basu
3 years ago
committed by
Arijit Basu