layeh
My feedback
6 results found
-
19 votes
An error occurred while saving the comment layeh
supported this idea
·
-
1,483 voteslayeh
supported this idea
·
-
2,997 votes
Proton and Standard Notes are joining forces: https://proton.me/blog/proton-standard-notes-join-forces
layeh
supported this idea
·
-
628 voteslayeh
supported this idea
·
-
1,941 voteslayeh
supported this idea
·
-
1,942 voteslayeh
supported this idea
·
Adding another use case to this: keeping a CHANGELOG.md in a linked Drive folder.
My setup is a Project with a linked Proton Drive folder holding a changelog
file that I update as work progresses. I want Lumo to always work from the
current version.
The support docs say: "Whenever new assets are added to the linked Proton
Drive folder, Lumo will automatically refer to them when working on the
current Project." That wording covers new files appearing, but says nothing
about an existing file whose contents change. So it's unclear whether editing
a file in place triggers re-indexing, or whether Lumo keeps serving the
version it first indexed.
Two things would resolve this:
1. Documentation of what actually happens when an existing linked file is
modified. Does the index refresh, and if so, how quickly?
2. If it doesn't refresh, a way to force it. Removing and re-adding the file,
or re-linking the folder, is workable but tedious for something that
changes often.
As a workaround I'm considering versioned filenames (changelog-1.0.md,
changelog-1.1.md) so each update counts as a "new asset" under the documented
behaviour. Downside: old versions accumulate in Project Knowledge and may get
retrieved alongside the current one.
Related: even when a file is current, the @ mention picker doesn't always list
every file shown in Project Knowledge, so it's hard to tell whether a stale
version is being served or the file simply wasn't ranked as relevant.