| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The `/media/$USER` locations aren't finalized yet so we're holding off
on that change.
|
|
|
|
|
|
|
|
|
|
|
| |
Because of `udisks2` `/run/media/$USER` is becoming a common directory
for automounting, this adds a keybinding to go there (using the first
available letter in the path).
Similarly the binding for `/media` now points to `/media/$USER`, because
for example ubuntu adopted this new location.
I believe the `$USER` parts have to do with security, giving only the
user that mounted a filesystem access to it.
|
|\
| |
| | |
Make new `rifle` behavior backwards compatible.
|
| |\
| |/
|/| |
|
| |
| |
| |
| | |
Signed-off-by: ael-code
|
| |
| |
| |
| |
| |
| |
| | |
If both `EDITOR` and `VISUAL` are unset, setting `VISUAL` because it's
technically the right thing to do and setting `EDITOR` for backwards
compatibility complicates the logic. `rifle` will now only do the
latter.
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There's 4 possible situation:
1. `VISUAL` set, `EDITOR` set
2. `VISUAL` set, `EDITOR` not set
3. `VISUAL` not set, `EDITOR` set
4. `VISUAL` not set, `EDITOR` not set
All but _No.2_ are already properly handled.
Behavior can differ depending on whether you have an old or a new
`rifle.conf` in cases _No.1_ (if the variables differ the new approach
prefers `VISUAL` instead of `EDITOR`) and _No.2_ (new approach will use
`VISUAL` whereas the old approach would've fallen back to _vim_).
_No.3_ is likely the most common case and works almost identically with
either approach.
_No.4_ still falls back to _vim_ as before.
Fix #1048
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| |\ |
|
| | |\ |
|
| | | |\ |
|
| | | | |\ |
|
| | | |/ / |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When reading a file for which Ranger doesn't have permissions, Python3
throws an OSError. Python2 on the other hand throws a IOError, which
wasn't being caught and caused Ranger to crash. IOError was added to
catch statements for this reason.
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
When reading a file for which Ranger doesn't have permissions, Python3
throws an OSError. Python2 on the other hand throws a IOError, which
wasn't being caught and caused Ranger to crash. IOError was added to
catch statements for this reason.
|
|\| | | | |
|
| | | | | |
|
| | | | | |
|
|\| | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
@hut: please document your settings in the man page too next time ;)
|
| | | | |
| | | | |
| | | | |
| | | | | |
@nfnty: please document your settings in the man page too next time ;)
|
| | | | |
| | | | |
| | | | |
| | | | | |
@Klinkenstecker: please document your settings in the man page next time ;)
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
@kattrali: please add a distinct entry in the man page for every setting
you add
|
| | | | |
| | | | |
| | | | |
| | | | | |
@hut: please document your settings in the man page too next time ;)
|
| | | | |
| | | | |
| | | | |
| | | | | |
@jgreco: please document your settings in the man page too next time ;)
|
| | | | |
| | | | |
| | | | |
| | | | | |
@randynobx: please document your settings in the man page too next time ;)
|
|\| | | | |
|
| |/ / / |
|
| | | | |
|
| | | | |
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | | |
"Fuzzy" is the more applicable term here. "Smart" is often associated
with case sensitivity. So it would avoid confusion between
`set cd_tab_case smart` and `set cd_tab_smart true`.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
`VISUAL` is often misused to mean desktop GUI editor it's actual purpose
was to distinguish editors like `vi` (which is short for visual) from
editors like `ed` (which was probably short for editor), `EDITOR` is
actually intended to point to one of the latter.
Rifle still defaults to `vim` if both variables are undefined, even
with an old `rifle.conf` after trying to fall back on `EDITOR`.
For some better information on this see,
https://unix.stackexchange.com/a/334022
|
| |/
|/|
| |
| | |
Fixes #1035
|
| |
| |
| | |
Prioritise chromium as I think most Linux users would prefer that as default over google-chrome.
|
| |
| |
| |
| | |
Added `has google-chrome` and `has chromium-browser` then adjusted the spacing to adjust for new longer `has chromium-browser` line.
This allows Ubuntu users to open in google-chrome and chromium-browser packages.
|
|\ \ |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
A stringified list, as before, cannot be used in the :set command.
|
|/ / |
|
| | |
|