| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| | |
Resolve https://github.com/ranger/ranger/issues/2311
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This commit also renames the method to "get_filesystem_objects" for
symmetry to "get_directory".
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The trash command used to crash ranger when passing so may arguments
that the argument length limit of the OS is reached. See the discussion
in pull request #1871 for steps to reproduce.
Now it displays an error message instead of crashing.
(It does not move the files to trash though.)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously the File() constructor was called for every path (if the
paths to be moved to trash were supplied after the command instead of
deleting the selection, e.g. ":trash a b c").
This commit adds a method paths_to_filesystem_objects() to find the
existing objects that ranger has in memory and use those instead.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The execute() method of the trash command (in ranger/config/commands.py)
used to pass a list of file paths (as strings) to fm.execute_file().
The documentation of the execute_file() method states that the 'files'
parameter must not be strings:
[...]
files: a list of file objects (not strings!)
[...]
So I changed 'files' to be a list of File objects and that seems to fix the
issue.
Fixes #1798
|
| | | |
|
| | |
| | |
| | |
| | | |
Fixes #2292
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
On some systems (e.g. archlinuxarm) man is not installed by default, hit
'?' and 'm' will cause ranger crashed, showing:
AttributeError: 'NoneType' object has no attribute 'poll'.
|
| | |
| | |
| | | |
For the correct file URI scheme specification, see RFC 8089 at https://tools.ietf.org/html/rfc8089.
|
|\ \ \
| | | |
| | | |
| | | | |
Fixes #1744
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Transpose last two words even if on the first letter of last word. This
behavior is consistent with readline and emacs.
The previous code move one word back if it was anywhere in the last word
but that meant the third and second to last words were transposed if the
cursor was on the first character of the last word.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
There's no sensible action at the start of the line but we don't want to
issue the warning about invalid regions either.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The calculations for cutting out and repositioning the second now
shifted region was complicated. Simply cutting the two regions out of
the string and swapping them is conceptually simpler.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
There's no point transposing equal regions, the result would be the
same.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Allowing negative regions makes it harder to verify there's no overlap
between regions.
|
| | | |
| | | |
| | | |
| | | | |
Inspired by emacs/readline.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes #2086
Fixes #2125
Fixes #2136
Fixes #2173
Fixes #2205
Fixes #2209
|
| | | | |
| | | | |
| | | | |
| | | | | |
Fix #2173.
|
| |\ \ \ \ |
|
| | |/ / /
| | | | |
| | | | |
| | | | | |
Fixes #2071
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
A non-existent tag file leads to an opaque crash without indication to
the user of what went wrong as in #2200. These errors are now reported
through ranger's notify mechanism.
The tag file is no longer created conditionally on `__init__`, only upon
saving tags. This changes the behavior somewhat in that an empty
"tagged" file should never be created.
|
|/ / / |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The maps without explicit target only changed user permissions. The
chmod utility changes all permissions when the target's omitted. This
brings both more in line.
Fixes #2161
|