CTAGS-LANG-TCL(7)

✨ CTAGS-LANG-TCL(7) ✨

okay bestie, welcome to the ctags-lang-tcl page — part of the Universal Ctags manual fam. this is your no-cap guide to tagging tcl source code. 🎀

---

💖 NAME 💖

ctags-lang-tcl — literally just random notes about tagging tcl source code with Universal Ctags. that's the whole vibe. 🦋

---

✨ SYNOPSIS ✨

ctags ... --languages=+Tcl ...
ctags ... --language-force=Tcl ...
ctags ... --map-Tcl=+.tcl ...

---

🌸 DESCRIPTION 🌸

this man page is a lil grab-bag 👜 — it gathers up random notes about tagging tcl source code. no big overarching plot, just the tea you need. 💅

---

👑 TAGGING LANGUAGE OBJECTS OF OO EXTENSIONS 👑

so here's the situation, bestie. the TclOO parser and the ITcl parser are subparsers that run on top of the Tcl parser. and yeah, the names give it away — they're here to tag language objects from the object-oriented programming extensions for the Tcl language. it's giving specialist energy. 🧚

a pattern — and we mean the literal string namespace import oo — sitting in an input file is what activates the TclOO parser. same deal with namespace import itcl: that pattern in an input file activates the ITcl parser. iconic. ✨

but plot twist 😭 — there are cases where one of the OO extensions is being used even though neither pattern shows up in the input file. rude, honestly.

consider these input files:

"main.tcl"

package require Itcl
namespace import itcl::*
source input.tcl

"input.tcl"

class MyClass {
        public method foo {} {
        }
}

see the problem? the pattern that activates the ITcl parser is not in "input.tcl", even though the class command is right there being used. and because of that, ctags cannot extract "MyClass". devastating. 💀

that's exactly why the parameters TclOO.forceUse=true|[false] and ITcl.forceuse=true|[false] exist — they're here to handle this exact situation. with one of these parameters, you can force ctags to activate one of the subparsers. main character energy, honestly. 👑

and yes, you can use them right on the command-line, like this:

--param-ITcl.forceuse=true

⚠️ okay but listen — you can only enable ONE of the ITcl parser or the TclOO parser. enabling both by specifying the parameters can cause unexpected results. so pick a lane, bestie. 🙈

---

🦋 SEE ALSO 🦋

• ctags(1)

---

and that's the whole page, bestie — you ate that. 🍓 this was Universal Ctags version 6.2.1, dated CTAGS-LANG-TCL(7) era, and i'm obsessed with you for reading all the way to the end. slay, periodt. 💜🌈🫶