Install lnstags in $GOPATH/bin by running:

go install -tags gopherlua github.com/ifritJP/lnstags@latest

$ git clone --depth 1 https://github.com/ifritJP/lnstags
$ cd lnstags
$ make build ONLY_GO=y

The above will generate lnstags/lnstags.

lctags update updates the information based on the lns source file list registered in the DB.

Unlike lctags build, you don't need to specify the source file to analyze.

If the number of lns files to be analyzed increases or decreases, lctags build should be used instead of lctags update.

inq makes an inquiry by specifying a symbol name.

// @lnsFront: ok
class Foo {
   pub fn func() {
   }
}
class Bar {
   pub fn func() {
   }
}
let foo = new Foo();
foo.func();
let bar = new Bar();
bar.func();

For example, given the mini.lns file above, the symbolic name for the func method in the Foo class would be:

@mini.Foo.func

where @mini indicates the module name and mini refers to mini.lns. For example, for abc/def/ghi.lns, the module name will be @abc.@def.@ghi. Foo.func points to the func method of the Foo class.

And by executing the following command, the definition location of @mini.Foo.func is listed.

$ lnstags inq def @mini.Foo.func
@mini.Foo.func      2 mini.lns            pub fn func() {

The def of this command lnstags inq def specifies the definition location query.

The types of inquiries are as follows.

If you know the fully qualified name of the symbol you want to inquire about, you can use the inq command, but finding out the fully qualified name can be difficult or cumbersome.

So inq-at queries for a symbol at a given position in the source.

When querying the definition location of foo.func() in the 5th column of the 10th line when there is the following source,

// @lnsFront: ok
class Foo {
   pub fn func() {
   }
}
class Bar {
   pub fn func() {
   }
}
let foo = new Foo();
foo.func();
let bar = new Bar();
bar.func();

Run the following command.

$ lnstags inq-at def mini.lns 10 5
@mini.Foo.func      2 mini.lns            pub fn func() {

This will query for the symbol at the specified location.

In the above case, we recognize that the fully qualified name of foo.func in mini.lns 10 5 is @mini.Foo.func and def query it.

When using inq-at, the specified lns file must be built without errors.

Also, it takes time to parse the AST of the specified lns file.

inq-at gets the fully qualified name by specifying the location of the lns file, while suffix gets the list of fully qualified names with a suffix match on the symbol name.

For example, to display a list of fully qualified names that match func at the end:

$ lnstags suffix func
@mini.Foo.func
@mini.Bar.func