bust-a-gem icon indicating copy to clipboard operation
bust-a-gem copied to clipboard

Any chance the "Go to Definition" works with existing `TAGS` file while bust-a-gem is ripping new `TAGS` file?

Open vfonic opened this issue 11 months ago • 3 comments

I set up Bust A Gem to run whenever I save a Ruby file. It works great!

Here's my setup settings.json:

"runOnSave.commands": [
    {
      "match": "\\.(rb|rake)$",
      "command": "bust-a-gem.rebuild",
      "runIn": "vscode",
      "runningStatusMessage": "Rebuilding project tags",
      "finishStatusMessage": "Project tags rebuilt"
    }
  ],

I use this dated, but still working VS Code extension: https://marketplace.visualstudio.com/items?itemName=pucelle.run-on-save

Since my projects grew bigger and I also allow Bust A Gem to rip some gems so I can "Go to Definition" directly inside the gem files, it's taking about 3 seconds for Bust A Gem to generate TAGS file. During this time, "Go to Definition" doesn't work.

Any chance this can be changed?

If this is changed, my setup would be PERFECT! :) I could use "Go to Definition" all the time, even for new files and whenever I save a file Bust A Gem will automatically generate TAGS, but it will work all the time, except for the newly added definitions that are just being added to TAGS for the first time. Only for those I'd need to wait those ~3 seconds.

vfonic avatar Aug 03 '23 23:08 vfonic