about summary refs log tree commit diff stats
path: root/LICENSE.txt
blob: 751a2c57959dc41138df66e3bd555455e2731cad (plain) (blame) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

Profanity
Copyright (C) 2012 - 2019 James Booth <boothj5@gmail.com>

Profanity is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

Profanity is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with Profanity.  If not, see <http://www.gnu.org/licenses/>.

There is an additional exception from the author permitting linking
with OpenSSL:

As copyright holder, I give permission for profanity to be linked to
the OpenSSL libraries. This includes permission for profanity
binaries to be distributed linked against the OpenSSL libraries.
All other obligations under the GPL v3 remain intact.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-28 08:34:17 +0000
9; font-style: italic } /* Name.Label */ .highlight .nn { color: #bb0066; font-weight: bold } /* Name.Namespace */ .highlight .py { color: #336699; font-weight: bold } /* Name.Property */ .highlight .nt { color: #bb0066; font-weight: bold } /* Name.Tag */ .highlight .nv { color: #336699 } /* Name.Variable */ .highlight .ow { color: #008800 } /* Operator.Word */ .highlight .w { color: #bbbbbb } /* Text.Whitespace */ .highlight .mb { color: #0000DD; font-weight: bold } /* Literal.Number.Bin */ .highlight .mf { color: #0000DD; font-weight: bold } /* Literal.Number.Float */ .highlight .mh { color: #0000DD; font-weight: bold } /* Literal.Number.Hex */ .highlight .mi { color: #0000DD; font-weight: bold } /* Literal.Number.Integer */ .highlight .mo { color: #0000DD; font-weight: bold } /* Literal.Number.Oct */ .highlight .sa { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Affix */ .highlight .sb { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Backtick */ .highlight .sc { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Char */ .highlight .dl { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Delimiter */ .highlight .sd { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Doc */ .highlight .s2 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Double */ .highlight .se { color: #0044dd; background-color: #fff0f0 } /* Literal.String.Escape */ .highlight .sh { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Heredoc */ .highlight .si { color: #3333bb; background-color: #fff0f0 } /* Literal.String.Interpol */ .highlight .sx { color: #22bb22; background-color: #f0fff0 } /* Literal.String.Other */ .highlight .sr { color: #008800; background-color: #fff0ff } /* Literal.String.Regex */ .highlight .s1 { color: #dd2200; background-color: #fff0f0 } /* Literal.String.Single */ .highlight .ss { color: #aa6600; background-color: #fff0f0 } /* Literal.String.Symbol */ .highlight .bp { color: #003388 } /* Name.Builtin.Pseudo */ .highlight .fm { color: #0066bb; font-weight: bold } /* Name.Function.Magic */ .highlight .vc { color: #336699 } /* Name.Variable.Class */ .highlight .vg { color: #dd7700 } /* Name.Variable.Global */ .highlight .vi { color: #3333bb } /* Name.Variable.Instance */ .highlight .vm { color: #336699 } /* Name.Variable.Magic */ .highlight .il { color: #0000DD; font-weight: bold } /* Literal.Number.Integer.Long */
Colorschemes
============

This text explains colorschemes and how they work.

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

Context tags provide information about the context and are Boolean values (`True`
or `False`). For example, if the tag `in_titlebar` is set, you probably want to
know about the color of a part of the titlebar now.

The default context tags are specified in `/ranger/gui/context.py` in the
constant `CONTEXT_KEYS`. Custom tags can be specified in a custom plugin file in
`~/.config/ranger/plugins/`. The code to use follows.

```python
# Import the class
import ranger.gui.context

# Add your key names
ranger.gui.context.CONTEXT_KEYS.append('my_key')

# Set it to False (the default value)
ranger.gui.context.Context.my_key = False

# Or use an array for multiple names
my_keys = ['key_one', 'key_two']
ranger.gui.context.CONTEXT_KEYS.append(my_keys)

# Set them to False
for key in my_keys:
    code = 'ranger.gui.context.Context.' + key + ' = False'
    exec(code)
```

As you may or may not have guessed, this only tells ranger that they exist, not
what they mean. To do this, you'll have to dig around in the source code. As an
example, let's walk through adding a key that highlights `README.md` files
differently. All the following code will be written in a standalone plugin file.

First, from above, we'll add the key `readme` and set it to `False`.

```python
import ranger.gui.context

ranger.gui.context.CONTEXT_KEYS.append('readme')
ranger.gui.context.Context.readme = False
```

Then we'll use the hook `hook_before_drawing` to tell ranger that our key is
talking about `README.md` files.

```python
import ranger.gui.widgets.browsercolumn

OLD_HOOK_BEFORE_DRAWING = ranger.gui.widgets.browsercolumn.hook_before_drawing

def new_hook_before_drawing(fsobject, color_list):
    if fsobject.basename === 'README.md':
        color_list.append('readme')

    return OLD_HOOK_BEFORE_DRAWING(fsobject, color_list)

ranger.gui.widgets.browsercolumn.hook_before_drawing = new_hook_before_drawing
```

Notice we call the old `hook_before_drawing`. This makes sure that we don't
overwrite another plugin's code, we just append our own to it.

To highlight it a different color, just [add it to your colorscheme][1]

[1]:#adapt-a-colorscheme

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 terminal emulator in use.

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 a custom 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 maintenance work and a greater chance that your colorscheme will work with
future versions of ranger.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-28 08:34:13 +0000