People

Keep a page for a person, mention them in a note, and name your own connections. Everything stays readable Markdown.

Create a person

Open People and choose New person. Give the page a name and a handle such as alice.smith. The default location is People/alice.smith.md. Write freely in the page. To change the person's name, click the bar under the page title (it reads Person) and edit Name; it is saved straight into the page. The handle is shown there too: Rename… beside it changes it in every note that mentions the person. On the phone, the same details open from Properties.

You can also right-click the People folder in the files list and choose Create person, or right-click People/Connections and choose Create connection.

Choose where pages go

Open Settings ▸ Plugins ▸ People. Where pages go lists the folder that new people and new connections start in, with Change… beside each. The same choice is behind the Page defaults button in the People and People connections panels. A changed folder applies to pages made from then on; pages already in the vault stay where they are, and the folder's right-click menu follows the new location.

Mention someone or add a connection

Type @ and part of a name or handle. Choose a result to insert a mention. If there is no page yet, Create person… opens a form and returns the new handle to your original note.

Type /, or use Insert…, to choose a connection and then a person. /ow narrows to Owner. Choosing it writes owner: @ straight away and opens the people list; type part of a name or handle to narrow it. Choosing a person completes the line:

owner: @alice.smith

A connection is drawn as a small pill — the connection's name as a tag, the person beside it — so it stands out on a task line. Put the cursor on the line and it goes back to the words you typed. Read view shows the same pill.

Each connection can have its own pill colour. Open the connection's page and click the bar under its title (it reads People connection): it opens on the connection's details, where you can change its Label, switch Retired on or off, and pick a Pill colour — blue, green, amber, red, purple or grey, or Default for the usual blue tint. Each change is saved straight into the page. The keyword is shown but not edited there: Rename… beside it renames it in every note that uses it. On the phone, the same details open from Properties. You can also set the colour when you create a connection. A grey pill you didn't choose means the word before the colon isn't a connection Gilune knows — often a typo, or a connection that has been retired.

The default connections are assign and owner. Add your own through the connections collection. Their names carry the meaning you give them: Gilune imposes no responsibility hierarchy. A plain mention does not imply assignment.

You can type the same text in any editor. Code examples, escaped references and email addresses do not become connections. Missing or ambiguous handles remain explicit; the lookup will not silently choose the first page.

Follow references and search

Mentions are coloured like links as you write, so you can see at a glance which words Gilune has recognised. To open someone's page from a note, put the cursor anywhere on their mention and press F12 — the key Visual Studio uses for "go to definition". If you would rather use another key, open Settings ▸ People, press Change next to Go to definition, and press the key or combination you want. In presentation mode a click on a mention does the same.

Use Links on a note to open a referenced person. On a person page, Links provides All references, Mentions and Connections. Results open their source pages. A page connection does not automatically apply to each item inside it.

With the Tasks plugin enabled too, a filter can combine independently contributed fields:

type:task is:open people.connection:assign IN ["alice.smith", "bob"]

Rename visible text

Open the person or connection definition and choose Refactor…. Choose Rename handle or Rename connection, enter the new spelling, and prepare a preview. An existing connection destination requires the explicit merge option.

The preview includes defining pages and recognised references in ordinary Markdown, including files without Gilune metadata. Review the before/after text, choose a folder scope or exclude individual files, then apply. Save unsaved editor changes before preparing a preview. Applied changes remain listed if you cancel; resume finishes eligible entries. Conflicts require a fresh preview.

The defining page changes after the other reviewed files succeed. Excluding a file leaves that plan incomplete. A later edit using an old spelling stays as written: use Find remaining occurrences / new preview when you want to update it.

Undo and recovery

Refactor history provides Preview undo. Undo is another guarded edit, preserving subsequent work where the old change can still be identified safely. Ambiguous or overlapping changes need resolution.

Retained copies are available from each document preview, including after People is removed. Inspect a copy and choose Preview restoration to review it against the current file. An external editor keeping an old file handle can still write to a retained copy; Gilune preserves those bytes for explicit recovery.

Managed page changes sync as ordinary revisions. Unmanaged Markdown remains a plain file and uses its existing file-transfer mechanism. Bulk history and recovery copies stay on the originating device until its local application data is removed.

Disabling People keeps your text and pages. Re-enabling it restores lookup and indexed meaning from those documents. Birthdays and other dates can be ordinary page information; reminders are a future capability.