| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
| |
All the log calls that were using the old logging approach
(appending to FileManager.log queue) will now use the standard logging
library of python. Proper log levels have been choosed for each call
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The goal is to provide an easy api to log stuff and a straigthforward way of inspect them. This has been achieved using the standard logging library. The default behaviour is pretty similar to the old one, in the sense that all the the produced logs will be collected in a queue that can be inspected with the curses log viewer (`display_log` command). Moreover the `--logfile` cli option has been added and it can be used to specifya destination file for all the logs in such a way that the same log can be viewed at runtime as well as inspected after a program crash.
The verbosity and the format of the log message is controlled by the already existent `--debug` command line flag:
- Normal mode:
A concise log format will be used and only important message will be logged (log level > INFO)
Example:
```
[INFO] Ranger version 1.7.2
[INFO] Running on Python 3.5.2 (default, Jun 28 2016, 08:46:01) [GCC 6.1.1 20160602]
[INFO] Process ID is 1497
```
- Debug mode:
An extended log format will be used and all the message will be logged.
Example:
```
23:17:43,719 [ranger.core.main] |INFO| Ranger version 1.7.2
23:17:43,719 [ranger.core.main] |INFO| Running on Python 3.5.2 (default, Jun 28 2016, 08:46:01) [GCC 6.1.1 20160602]
23:17:43,719 [ranger.core.main] |INFO| Process ID is 1515
23:17:43,720 [ranger.core.main] |DEBUG| config dir: '/home/groucho/.config/ranger'
23:17:43,720 [ranger.core.main] |DEBUG| cache dir: '/home/groucho/.cache/ranger'
23:17:43,738 [ranger.core.actions] |DEBUG| Sourcing config file '/path/to/ranger/config/rc.conf'
```
fixes #713
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| | |
Previously the displayer was not changed after the initialization, so
only the value read from rc.conf was used.
|
| |\ \ |
|
| | |/ |
|
| | | |
|
| |\ \ |
|
| | |/ |
|
| |\ \
| | |
| | |
| | | |
https://github.com/richboss/ranger
|
| | |/ |
|
| |\ \ |
|
| | |/ |
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | | |
|
| | |/
| |
| |
| |
| | |
- replaced calls to subprocess.check_output by code downported from
Python 2.7
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Now only the first token of TERMCMD needs to exist in PATH. Previously
the whole value was checked, which could contain additional parameters.
The check and term guessing were performed in two places. Now it's done
by the get_term() function to reduce the code duplication. In that
function the second check was indented one level deeper (relative to the
original code). Keeping both checks on the same level, while visually
pleasing, was conveying the wrong message. One never wants to perform
the second check if the first one fails. Nesting shouldn't be a problem:
if the nesting will need to be any deeper than this, this code will need
to be refactored anyway.
Fixes #613.
|
| |\ \
| | |
| | |
| | | |
https://github.com/stepshal/ranger
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | | |
Ensure that only one newline is rstripped
|
| | |/ / |
|
| |\ \ \ |
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
This is required for shell commands to succeed with filenames that
start with the hash character. The 'mv' command invoked by 'bulkrename',
for instance, will fail with such files unless hashes are escaped.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This reverts commit 8132885c2fbddc9e686f2285b307e28a1f29f2a7.
|
| | | | |
|
| |\ \ \ |
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This results from finalize being called in order for the widgets.
Previously when ranger changed viewmodes, it would delete then readd the widget
object which meant that the finalize for the viewmode was called last instead
of before console, which meant the finalize of the viewmode was setting
and overriding the cursor position.
|
| |/ / /
| | |
| | |
| | |
| | | |
The full size is only shown when ALL files (hidden or filtered) are
selected.
|
| | | |
| | |
| | |
| | |
| | | |
The incorrect part of the conditional is already covered correctly
in has_preview(), so it is redundant and can be removed.
|
| |/ / |
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | | |
The default rc.conf uses 'scout' with the '-r' flag in several places,
but the flag isn't documented.
|
| | | | |
|
| | | | |
|
| | |/
|/|
| |
| | |
the view was rebuilt *before* the setting was changed, not *after*
|