⁨Nico Baier⁩'s Posts

Nico Baier

Jul 17, 2024

Open credit usage display from cmd+k menu

Actions

Explain the problem as you see it

Right now, getting to my AI credit usage requires a couple clicks and there is no keyboard driven way to do it.

Why is this a problem for you?

It's honestly not that big a deal, but it's a little annoying. I prefer to use keyboard shortcuts where I can in Tana.

Suggest a solution

Add "open manage account menu" (or something similar) to the cmd+k menu.

⁨0⁩ ⁨comments⁩

Nico Baier

Jul 26, 2023

Group-by defined vs. undefined

Actions

Explain the problem as you see it

Currently, when using the "group by" view option on a field that has multiple values across the nodes being grouped, each individual value will get a group. While this is fine in some cases, it becomes impractical when a large number of values are possible groups.

Here's an example:
Screenshot 2023-07-25 at 12.49.58 PM.png

We have three nodes that are grouped by "example field." It would be great if there was a way to group nodes 2 and 3 together to the exclusion of node 1

Why is this a problem for you?

It becomes very hard to effectively group nodes and use the group by menu when there are a large number of values. And it could be useful to exclude nodes that have a definition.

Suggest a solution

Add a "is defined" option to the group by options.

⁨0⁩ ⁨comments⁩

Nico Baier

Apr 20, 2023

Improved range of formatting options for title expressions

Actions

Explain the problem as you see it

Currently, there are a small number of options for formatting fields when using them in title expressions. This is limited to:

Character limited via ${field|#...}
Placeholder/optionality via ${field|?}

This is extremely limiting. There is no way to add to / transform the content a field used in a title expression without using kludgy workarounds.

Why is this a problem for you?

The core problem it limits the usefulness of title expressions. For example, while it is often useful to display a date in the title of nodes tagged with #todo and the like, these additions to the title become extremely long, especially when a start and end time are part of that date field. By allowing other types of date formatting options (as suggested https://ideas.tana.inc/posts/135-format-date-fields-in-build-in-title), we would gain a lot of flexibility in the way we build titles.

Another case comes from the potential addition of delimiters. Suppose I want to have all todos with a due date have the title structure in (1) and all todos without a due date have the title structure in (2):

(1) todo name | due date #todo
(2) todo name #todo

That is, when there is a due date, it is used in the title but is separated by a vertical line |. Currently. it is not possible to have condition separators without a unpleasant workaround.

Suggest a solution

The core syntax I would suggest is the following:

unformatted field = ${field name}
formatted field = ${field name|<formatting options>}

That is, use the current formatting syntax for title expressions, just expand the options. It would be great to eventually get something like Python f-strings .

⁨4⁩ ⁨comments⁩