| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
if you use ":tab_open 1 /path" while being in tab 1, the path should
change to /path, but it doesn't.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The quotes are not required anymore since :set doesn't eval the argument
anymore.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Without this, if you enter another tab, the cursor of the directory may
change and get_selection() will not return the actual selected file of
the tab anymore (unless they have been marked, in which case
everything's fine).
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
SettingObject can store settings local to a directory. Then LocalSettingObject
choses the right settings according to context.
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, you could change settings in both rc.conf and options.py.
With this commit, options.py is deprecated and you are encouraged to use
rc.conf to change settings. I chose to do this because it is more
elegant to use a simple list of ranger commands for configuration
rather than a python file with lots of magic around it and potential
syntax errors for inexperienced users.
The existing "set" command doesn't evaluate python objects anymore,
instead it always takes strings and converts to the proper type
automatically. This means that the old set command will not work
anymore and you have to update your commands.py if it still uses the old
definition of the "set" command.
This is how to convert your options.py:
old way, in options.py | new way, in rc.conf
---------------------------+------------------------
show_hidden = False | set show_hidden false
sort = 'basename' | set sort basename
column_ratios = (1, 5, 3) | set column_ratios 1,5,3
For backward compatibility, you still can use options.py, but you get a
warning when you start ranger. You can pipe stderr to /dev/null to
silence the warning, or just move your stuff from options.py to rc.conf
and plugins and delete the options.py.
Finally, to extend ranger, which you previously could do through
monkey-patching in options.py, you should now use the plugin system.
This was an experimental, undocumented feature of ranger for some time,
but this and the following commits will imrpove and document it.
You can simply move all the monkey-patching code from options.py to a
*.py file in ~/.config/ranger/plugins/.
|
| |/
|
|
|
|
|
|
|
|
|
| |
* implemented 22, 24, 26, 27, 28, to disable attributes, and don't reset fg,
bg attr on every escape block so that, for example, fg color persists
through different escape blocks until it is changed.
* Support for xterm256 colors
* Support aixterm escapes for high intensity colors (8 light but not bold
colors)
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
before, in the search_next method, item.mimetype could be None,
resulting in an exception in lst.sort(key=fnc) when
order == 'mimetype'.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This reverts commit 14412eea0cd7ec556062f8f984dc5577ebdc8b30.
Since rifle now does file-extension-based file type recognition, this
commit is not necessary anymore.
|
| |
|
|
|
|
|
|
|
| |
file is unreliable, often simple file-extension based recognition yields
better results.
See:
https://github.com/hut/ranger/issues/44
https://bbs.archlinux.org/viewtopic.php?pid=1147719#p1147719
|
| | |
|
| |
|
|
|
|
| |
This reverts commit d6c78470ba0e3a9923d5cc13a5babaca4d52aecf.
It makes ... little sense atm to remove this.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The code implements the functionality of cp and mv coreutils in python
and was removed as of v1.4.0 for efficiency and simplicity reasons.
I moved it back in for several reasons:
1. I plan to enhance shutil_g to report on its copying status so I can
display a progress bar
2. With no need for external cp/mv programs, distribution-specific
differences (like broken backup option on MacOS/BSD?) become irrelevant
3. You can still copy in ranger if you accidently delete /bin/cp
4. It gets rid of the occasional bug that the cp process keeps running
when ranger is terminated while copying
The possible downside is reduced efficiency in copying and ranger might
get stuck if the copying function is blocked. Let's see if it works
out.
|