Removing line numbers from ref labels

For reference throughout, including in queries, Linked Mentions, Linked Tasks and such, would it be possible to remove the @<lineno> part from the label (but not the actual link)?

For instance, the first two links here are Manual@2485 and Manual@2485. I’d like each to simply read Manual, but retain the links to the line numbers.

I see that these come from the built in templates, and I tried to override one of them using space-lua:

-- Renders a task object as a togglable task
templates.taskItem = template.new([==[
* [${state}] [[${ref}|Task]] ${name}
]==])

This did not work. I’m able to create my own templates like the above and use them, but how do I override built-ins?

Force the execution of your space-lua at the end of the stack by assigning a negative value to the priority property (note: specific syntax):

-- priority: -1

-- Renders a task object as a togglable task
templates.taskItem = template.new([==[
* [${state}] [[${ref}|Task]] ${name}
]==])

This is strange. I asked deepwiki, it said the same thing, and its solution worked. But why did mine not work? It’s not clear to me: if I add an x anywhere in my template, it works. If I remove it, it doesn’t. Not sure why. I at least do have it working for now.

Thank you for the suggestion. I did this and it worked, but now, it’s working without that either. I’m not sure what’s going on, but I do have it working. Thanks again!

It’s weird … ! For me:

  • setting the priority to 0 (as recommended by deepwiki) does not work
  • setting it to -1 works in all cases
1 Like

It is also necessary to distinguish:

  • create a task (in a list, on a page - Example : list Todo)
  • view it (on this same page or any other) via a template

The task status can be changed in two places:

  • in the original list (eg: list Todo): the new status is NOT automatically propagated in the visualization (the space-lua expression must be reload)
  • in the visualization: the new status is immediately propagated in the original list PROVIDED that the ref is still valid (as you point out in your other post: Observations on Live Editing)
1 Like