about summary refs log tree commit diff stats
path: root/examples/plugin_chmod_keybindings.py
Commit message (Collapse)AuthorAgeFilesLines
* linting: Python 2 compat: Import from `__future__`nfnty2017-01-171-0/+2
|
* linting: pylint and flake8nfnty2017-01-171-2/+5
|
* Add two blank lines where is expectedstepshal2016-06-161-0/+1
|
* Should I dual ranger/cleric or wait for the THAC0 bonus? v1.7.0hut2015-04-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Squashed commit of the following: commit 7236dde27bf33fec5097c223f0d70598b10ba05f Author: hut <hut@lepus.uberspace.de> Date: Mon Apr 13 14:33:59 2015 +0200 wrote changelog entry commit 73e76b0f9a22ad8122154c4a2763c27ebce9be37 Author: hut <hut@lepus.uberspace.de> Date: Mon Apr 13 13:41:27 2015 +0200 update version number in man page commit b1948b9382027ed55d095a936610bc62f7cdba9a Author: hut <hut@lepus.uberspace.de> Date: Mon Apr 13 13:41:08 2015 +0200 update rifle version number commit a96a8a808a3c68eb848a3e0361fd95cb8c643d59 Author: hut <hut@lepus.uberspace.de> Date: Mon Apr 13 13:34:59 2015 +0200 s/ranger-master/ranger-stable/ commit 6967a48193227b4a0c843e8831e5511005179f69 Author: hut <hut@lepus.uberspace.de> Date: Mon Apr 13 13:33:06 2015 +0200 updated version number commit 0cbc401fd25fc4d307d026628e12ef1106a42bdf Author: hut <hut@lepus.uberspace.de> Date: Mon Apr 13 13:18:26 2015 +0200 updated version info in example plugins
* moved "doc/examples" to "examples" for more visibilityhut2015-04-131-0/+20
|
* move examples to doc/exampleshut2013-03-091-20/+0
|
* Added version info to exampleshut2013-03-011-0/+2
|
* examples/plugin_chmod_keybindings.py: fixed crashhut2013-02-221-1/+1
|
* replaced tabs with 4 spaces in all python fileshut2013-02-101-7/+7
| | | | | | | | | PEP 8 (Style Guide for Python Code) suggests the use of 4 spaces: http://www.python.org/dev/peps/pep-0008/#indentation If you need to use tools like "git blame", you can use the -w option to ignore this commit entirely. Patches will continue to work if you substitute tabs with 4 spaces everywhere except in the Makefile.
* updated man page, improved hookshut2012-12-041-5/+5
|
* removed options.py, improved plugins. *UPDATE YOUR COMMANDS.PY*hut2012-12-041-0/+18
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/.
>^
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92


            


                                                  

            











                                                                       

                                 












                                                                        

                










                                                                           
                                                             









                                                                       

                     

                                                   
                              
                             
 


                                                                    
 


                                                  

 

                   






                                                                  
                                                                  






                                                                            
Colorschemes
============

This text explains colorschemes and how they work.


Context Tags
------------

Context Tags provide information about the context.  If the tag
"in_titlebar" is set, you probably want to know about the color
of a part of the titlebar now.

There are a number of context tags, specified in /ranger/gui/context.py
in the constant CONTEXT_KEYS.

A Context object, defined in the same file, contains attributes with
the names of all tags, whose values are either True or False.


Implementation in the GUI Classes
---------------------------------

The class CursesShortcuts in the file /ranger/gui/curses_shortcuts.py
defines the methods color(*tags), color_at(y, x, wid, *tags) and
color_reset().  This class is a superclass of Displayable, so these
methods are available almost everywhere.

Something like color("in_titlebar", "directory") will be called to
get the color of directories in the titlebar.  This creates a
ranger.gui.context.Context object, sets its attributes "in_titlebar" and
"directory" to True, leaves the others as False, and passes it to the
colorscheme's use(context) method.


The Color Scheme
----------------

A colorscheme should be a subclass of ranger.gui.ColorScheme and
define the method use(context).  By looking at the context, this use-method
has to determine a 3-tuple of integers: (foreground, background, attribute)
and return it.

foreground and background are integers representing colors,
attribute is another integer with each bit representing one attribute.
These integers are interpreted by the used terminal emulator.

Abbreviations for colors and attributes are defined in ranger.gui.color.
Two attributes can be combined via bitwise OR: bold | reverse

Once the color for a set of tags is determined, it will be cached by
default.  If you want more dynamic colorschemes (such as a different
color for very large files), you will need to dig into the source code,
perhaps add an own tag and modify the draw-method of the widget to use
that tag.

Run tc_colorscheme to check if your colorschemes are valid.


Specify a Colorscheme
---------------------

Colorschemes are searched for in these directories:
~/.config/ranger/colorschemes/
/path/to/ranger/colorschemes/

To specify which colorscheme to use, change the option "colorscheme"
in your rc.conf:
set colorscheme default

This means, use the colorscheme contained in
either ~/.config/ranger/colorschemes/default.py or
/path/to/ranger/colorschemes/default.py.


Adapt a colorscheme
-------------------

You may want to adapt a colorscheme to your needs without having
a complete copy of it, but rather the changes only.  Say, you
want the exact same colors as in the default colorscheme, but
the directories to be green rather than blue, because you find the
blue hard to read.

This is done in the jungle colorscheme ranger/colorschemes/jungle,
check it out for implementation details.  In short, I made a subclass
of the default scheme, set the initial colors to the result of the
default use() method and modified the colors how I wanted.

This has the obvious advantage that you need to write less, which
results in less maintainance work and a greater chance that your colorscheme
will work with future versions of ranger.