about summary refs log tree commit diff stats
diff options
context:
space:
mode:
-rw-r--r--cpp/013run5
-rw-r--r--cpp/018record12
-rw-r--r--cpp/019address10
-rw-r--r--cpp/020array23
4 files changed, 18 insertions, 32 deletions
diff --git a/cpp/013run b/cpp/013run
index ef608cb6..9790bfdd 100644
--- a/cpp/013run
+++ b/cpp/013run
@@ -147,7 +147,10 @@ void write_memory(reagent x, vector<int> data) {
 
 :(code)
 size_t size_of(const reagent& r) {
-  type_info t = Type[r.types[0]];
+  return size_of(r.types);
+}
+size_t size_of(const vector<type_number>& types) {
+  type_info t = Type[types[0]];
   // End size_of Cases.
   return t.size;
 }
diff --git a/cpp/018record b/cpp/018record
index 5c1715a4..55c4df0d 100644
--- a/cpp/018record
+++ b/cpp/018record
@@ -43,9 +43,7 @@ case GET: {
   size_t offset = instructions[pc].ingredients[1].value;
   int src = base_address;
   for (size_t i = 0; i < offset; ++i) {
-    reagent tmp;
-    tmp.types.push_back(Type[base_type].elements[i][0]);
-    src += size_of(tmp);
+    src += size_of(Type[base_type].elements[i]);
   }
   trace("run") << "address to copy is " << src;
   assert(Type[base_type].elements.size() > offset);
@@ -121,9 +119,7 @@ case GET_ADDRESS: {
   size_t offset = instructions[pc].ingredients[1].value;
   int src = base_address;
   for (size_t i = 0; i < offset; ++i) {
-    reagent tmp;
-    tmp.types.push_back(Type[base_type].elements[i][0]);
-    src += size_of(tmp);
+    src += size_of(Type[base_type].elements[i]);
   }
   trace("run") << "address to copy is " << src;
   vector<int> result;
@@ -158,9 +154,7 @@ recipe main [
 if (t.is_record) {
   size_t result = 0;
   for (size_t i = 0; i < t.elements.size(); ++i) {
-    reagent x;
-    x.types.push_back(t.elements[i][0]);
-    result += size_of(x);
+    result += size_of(t.elements[i]);
   }
   return result;
 }
diff --git a/cpp/019address b/cpp/019address
index be1ce74c..13d59465 100644
--- a/cpp/019address
+++ b/cpp/019address
@@ -49,7 +49,7 @@ bool has_property(reagent x, string name) {
 reagent deref(reagent x) {
 //?   cout << "deref\n"; //? 1
   static const int ADDRESS = Type_number["address"];
-  reagent result("");
+  reagent result;
   assert(x.types[0] == ADDRESS);
 
   // compute value
@@ -110,9 +110,7 @@ case GET: {
   size_t offset = instructions[pc].ingredients[1].value;
   int src = base_address;
   for (size_t i = 0; i < offset; ++i) {
-    reagent tmp;
-    tmp.types.push_back(Type[base_type].elements[i][0]);
-    src += size_of(tmp);
+    src += size_of(Type[base_type].elements[i]);
   }
   trace("run") << "address to copy is " << src;
   assert(Type[base_type].is_record);
@@ -152,9 +150,7 @@ case GET_ADDRESS: {
   size_t offset = instructions[pc].ingredients[1].value;
   int src = base_address;
   for (size_t i = 0; i < offset; ++i) {
-    reagent tmp;
-    tmp.types.push_back(Type[base_type].elements[i][0]);
-    src += size_of(tmp);
+    src += size_of(Type[base_type].elements[i]);
   }
   trace("run") << "address to copy is " << src;
   vector<int> result;
diff --git a/cpp/020array b/cpp/020array
index 96591366..5e086ebc 100644
--- a/cpp/020array
+++ b/cpp/020array
@@ -32,15 +32,12 @@ recipe main [
 +mem: storing 15 in location 7
 +mem: storing 16 in location 8
 
-:(before "End size_of Cases")
-if (t.is_array) {
-  int base = r.value;
-  if (Memory[base] == 0) return 0;
-  reagent x;
-  x.set_value(base+1);
-  x.types.push_back(t.element[0]);
-  return 1 + Memory[base]*size_of(x);
-}
+:(after "size_t size_of(const reagent& r)")
+  const type_info& t = Type[r.types[0]];
+  if (t.is_array) {
+    int base = r.value;
+    return 1 + Memory[base]*size_of(t.element);
+  }
 
 :(before "End Globals")
 // Operator to look at elements of arrays.
@@ -58,9 +55,7 @@ case INDEX: {
   assert(Type[base_type].is_array);
   trace("run") << "ingredient 1 is " << instructions[pc].ingredients[1].name;
   size_t offset = instructions[pc].ingredients[1].value;
-  reagent elem;
-  elem.types.push_back(Type[base_type].element[0]);
-  int src = base_address + 1 + offset*size_of(elem);
+  int src = base_address + 1 + offset*size_of(Type[base_type].element);
   trace("run") << "address to copy is " << src;
   int src_type = Type[base_type].element[0];
   trace("run") << "its type is " << src_type;
@@ -106,9 +101,7 @@ case INDEX_ADDRESS: {
   assert(Type[base_type].is_array);
   trace("run") << "ingredient 1 is " << instructions[pc].ingredients[1].name;
   size_t offset = instructions[pc].ingredients[1].value;
-  reagent elem;
-  elem.types.push_back(Type[base_type].element[0]);
-  int src = base_address + 1 + offset*size_of(elem);
+  int src = base_address + 1 + offset*size_of(Type[base_type].element);
   trace("run") << "address to copy is " << src;
   vector<int> result;
   result.push_back(src);
lass="p">, '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.