about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorKartik K. Agaram <vc@akkartik.com>2021-07-07 19:34:54 -0700
committerKartik K. Agaram <vc@akkartik.com>2021-07-07 19:34:54 -0700
commitd73c84e299d7617014c67f34ad7afbc641eaf690 (patch)
tree0aa8f451fbf1cc783b164dfac26bbd731fc8c76e
parentd78a45340c27a8a3a4b7ab334c1807a477b97c76 (diff)
downloadmu-d73c84e299d7617014c67f34ad7afbc641eaf690.tar.gz
instructions for Universal Ctags
Thanks Sumeet Agarwal for raising this issue.
-rw-r--r--editor/editor.md7
-rw-r--r--editor/mu.ctags (renamed from editor/exuberant_ctags_rc)0
2 files changed, 4 insertions, 3 deletions
diff --git a/editor/editor.md b/editor/editor.md
index 65f2badb..d3e54f68 100644
--- a/editor/editor.md
+++ b/editor/editor.md
@@ -10,9 +10,10 @@ instructions within.
 The Vim files are most developed. In particular, I recommend some optional
 setup in subx.vim to use multiple colors for comments.
 
-If you use [Exuberant Ctags](http://ctags.sourceforge.net) for jumping easily
-from names to their definitions in your editor, copy the contents of `exuberant_ctags_rc`
-into your `.ctags` file.
+If you use [`ctags`](http://ctags.sourceforge.net) for jumping easily
+from names to their definitions in your editor, set it up to load `mu.ctags`.
+For classic Exuberant Ctags, copy it into `~/.ctags`. For the newer Universal
+Ctags, copy it into `~/.ctags.d/mu.ctags`.
 
 [Here](https://lobste.rs/s/qglfdp/subx_minimalist_assembly_language_for#c_o9ddqk)
 are some tips on my setup for quickly finding the right opcode for any
diff --git a/editor/exuberant_ctags_rc b/editor/mu.ctags
index 92e873f9..92e873f9 100644
--- a/editor/exuberant_ctags_rc
+++ b/editor/mu.ctags