Lukas/CortexFutura

Explain the problem as you see it

When adding an instance field that has its initialization set to "random node with this supertag" to the day tag, the random nodes only show up on days that don't "exit" at time of adding the field to the supertag. That is, when I've already visited the daily node for tomorrow when I add the field to the #day tag, I won't see random nodes until two days from now.

Why is this a problem for you?

I want to be prompted by a random couple of fleeting notes/zettels every day to get my creative juices flowing. But right now any day that already has a daily node won't get this, because of the way fields are initialized.

Suggest a solution

I see two solutions to my problem:

1) Create a command that allows me to re-run initializations on any field
2) Add a RANDOM N search operator to live searches that shows N random results from the total result set of the live search

Explain the problem as you see it

I want to have a set of commands that automatically show up on any voice note. Right now when I'm in my inbox I have pull up any voice note commands through the command line, which is much less convenient than automatically showing a button on each voice note.
I could go through and tag every voice note myself as #voice-note and have commands associated with that – but that's busy work that I should not need to do.

Why is this a problem for you?

I have to remember all the voice note specific commands that I have instead of being prompted by the voice note itself.

Suggest a solution

Allow a search parameter IS_VOICENOTE that I can put into the >Node filter parameter of my voice notes that makes command buttons automatically appear next to my voice notes.

Explain the problem as you see it

Right now the Inbox node is becoming a second "Library" node – unless you are fastidious about cleaning it out every day, it is basically impossible to move nodes added there to the day node of the day they were created. Ideally the Inbox node should be extremely easy to keep empty and in a state of "Inbox Zero".

Why is this a problem for you?

Inboxes should be empty, and I would like to keep the convention of treating the day node as my main gathering point of things added on a specific day. Right now I can move nodes easily to the library node or today's today-node. But when I open up Tana on a Monday morning I want to move the nodes I have added through Tana Capture on the weekend to Saturday/Sunday – which right now is impossible to do automatically.

Suggest a solution

Allow me to set up a command like this, where I can move any node to the day node of the day it was created.

Explain the problem as you see it

Tana does not allow using line breaks to structure the content of a single node

Why is this a problem for you?

Whether it's a verse of a poem, or a single tweet – line breaks can have meaning and help in structuring thinking.

The only current way of noting "these two lines of text belong together and/or form a cohesive thought" is one of the following:

• Put both lines into a single node, no line break. Horrible to read.
• Put both lines into separate lines as sibling nodes. Unclear that the lines belong together and should be referenced together.
• Put both lines into separate lines, with one line the "parent" node of the other line. Creates artificial hierarchy that is not necessarily implied by the text. Impossible to see content of both at a glance.

This artificial restriction is strange because Tana does not place any other restrictions on the size or shape of a node. I can put thousands of characters into a single node without a problem, but I am offered no way of structuring a node that contains even just 240 characters.

Suggest a solution

Allow line breaks inside a node

Explain the problem as you see it

Right now it is ~ impossible to effectively share writing done inside Tana outside of it.

Why is this a problem for you?

Whether it's writing academic papers or quarterly reports, eventually my writing needs to leave Tana and will be sent out to others via email, collaborated on in a Google Doc, or turned into a PDF.

Without an effective way of getting my writing out of Tana, it will always create significant friction in my work – or make it even impossible to use Tana as the central hub because the friction is not worth it.

Suggest a solution

I should be able to export any node and its children into a plainly formatted (i.e. no bullet points) text document in different file formats:

1. Markdown (especially important for further processing in academic work -> LaTeX)
2. MS Word
3. Google Doc

Ideally, this would work through and Cmd+K command "Export to..." and then being offered a choice between the different formats.