| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The old name, --fail-if-run, is still valid and working.
|
|
|
|
|
| |
It causes an error here:
/usr/bin/env: python -O: No such file or directory
|
| |
|
|
|
|
|
| |
This will discard assert statements which are unnecessary
for end users.
|
| |
|
| |
|
|
|
|
| |
This is OK since it comes at almost no cost
|
|
|
|
|
|
|
|
|
| |
Fear not. You still get the same functionality by using a function like:
ranger() {
$(which ranger) $@ &&
cd "$(grep \^\' ~/.ranger/bookmarks | cut -b3-)"
}
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This breaks cd-after-exit after Ctrl+C again, but enables
compatibility with zsh which I prefer over the former.
If you only use bash, you can safely revert this commit unless
future changes make it break.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|