You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current indicators are hard-coded, with the only configurable
details being the symbols in `citar-symbols`.
To make this all configurable, add a `citar-indicators` variable, which
is a list of `citar-indicator` indicator specs.
Also add the following functions:
* `citar--make-indicator-processors`
* `citar--make-indicator-symbols`
* `citar--make-indicator-tags`
BREAKING CHANGE: `citar-symbols` will be deprecated in favor of
`citar-indicators`
Signed-off-by: Bruce D'Arcus <bdarcus@gmail.com>
Copy file name to clipboardexpand all lines: README.org
+23-8
Original file line number
Diff line number
Diff line change
@@ -203,19 +203,34 @@ Note:
203
203
5. The ~%~ character preceeds a token defined as a key in ~citar-display-transform-functions~, whose value is a list of functions and optional arguments.
204
204
Note that if you include this, if you include this and a width specification, it must come after the width.
205
205
206
-
*** Icons
206
+
*** Indicators
207
207
208
-
By default, this UI is plain text, but you can configure it to use icons instead.
209
-
Here's how to configure it to use =all-the-icons= as in the screenshot at the top:
208
+
The UI includes configurable indicators.
209
+
By default, it includes plain text indicators for:
210
+
211
+
- Notes ::
212
+
Indicates presence of notes related to the reference.
213
+
- Files ::
214
+
Indicates presence of library files related to the reference.
215
+
- Links ::
216
+
Indicates present of links associated to the reference.
217
+
218
+
For other indicators, see the [[https://github.com/emacs-citar/citar/wiki/Indicators][wiki]].
219
+
220
+
Here's a screenshot using this configuration, which remove the links indicator, and mixes plain text and an icon indicator using ~all-the-icons~.
You can create your own indicators, of course, though important to keep in mind the included predicate functions must be performance optimized, since the completion UI runs them on your entire library every time to use it.
0 commit comments