summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorArtur Malabarba <artur@endlessparentheses.com>2018-02-15 20:53:39 -0200
committerArtur Malabarba <artur@endlessparentheses.com>2018-02-15 20:54:15 -0200
commita50d9b2fd059f6a0e5b22063a5375851a087f61a (patch)
tree553cda0009184f88b6925f7d814e6e67ae53f4d7
parent3201f6e1769beb9f6cbbda392bef99fce337acf4 (diff)
Add an example to the readme - Fix #19
-rw-r--r--README.org9
1 files changed, 9 insertions, 0 deletions
diff --git a/README.org b/README.org
index 4e89bea..308ca69 100644
--- a/README.org
+++ b/README.org
@@ -40,6 +40,15 @@ handles the minor-modes list. What can rich-minority /offer in contrast/?
- rich-minority is more versatile:
1. It accepts *regexps*, instead of having to specify each minor-mode individually;
+ That is, where in diminish.el you would do this:
+ #+begin_src emacs-lisp
+ (diminish 'auto-fill-function)
+ #+end_src
+ rich-minority does this:
+ #+BEGIN_SRC emacs-lisp
+ (add-to-list " Fill" 'rm-blacklist)
+ #+END_SRC
+ where ~" Fill"~ could be any regular expression.
2. It also offers a *whitelist* behaviour, in addition to the blacklist;
3. It supports *highlighting* specific minor-modes with completely arbitrary text properties.
- rich-minority takes a cleaner, functional approach. It doesn’t hack