Skip to content
dharmx edited this page May 13, 2024 · 6 revisions

Some features need special attention when using. Workarounds are always being on the way. But, for the time being be careful.

Unmarking terminal commands.

This might not work all the time. No fixes for this.

Marking $ENV.

This will work perfectly if you manually paste $XDG_CONFIG_HOME/.config/mimeapps.list (say) into the pad and then save it. But, to preserve $ENV_VARS when marking from :Mark you'd need to escape the \$ or, Neovim will expand it automatically.

So, :Mark \$XDG_CONFIG_HOME/.config/mimeapps.list will work as expected.

Conflicts between commands.

Say we mark two commands like the following (=゚▽゚)/

  • Mark term://eza\ --tree
  • Mark term:///home/dharmx/.config//eza\ --tree

Essentially, these are the same commands only when your current working directory is in /home/dharmx/.config. But, when you change your working directory to something else, the former runs the command in the current cwd that was switched from /home/dharmx/.config/ to say, /home/dharmx and the latter is run at the /home/dharmx/.config/ only.

Now, the thing is track.nvim can identify the latter one as the matching pattern is designed that way. So, if you mark both and then run both then only the second one can be highlighted/unmarked. You will have to manually remove the first one from the UI or, :Unmark term://eza\ --tree.

Just running the first command and then running :Unmark on it (may it be through a keymap) will likely not work (╥_╥)

Websites cannot be unmarked.

There is no way of doing that (DUH). You'd need to open an UI and then press dd on the website entry.

Clone this wiki locally