Repository navigation
feat: property and computed columns in collection views - #78
Merged
Merged
Conversation
Notes carry their :PROPERTIES: drawer and vulpea indexes it, but the collection view had no way to show or filter on it. - (property KEY) column, offered as prop:KEY by c a; e edits it on the selection (undoable), = narrows to its value - :properties filter with the :meta shape, prop:KEY=VALUE and prop:KEY=* in queries, / p in the buffer; pushed down to the property index when no tag condition is cheaper - adaptive columns include the filtered properties - (fn NAME FUNCTION) computed columns for anything else Property writes find the entry by ID, so a batch touching several notes of one file does not write through stale positions.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Notes already carry their
:PROPERTIES:drawer and vulpea indexes it (vulpea-db-query-by-property), but the collection view could not show or filter on it, and there was no way to add a column of your own. Came up on Reddit.What's new:
(property KEY)column.c aoffersprop:KEYfor every property found on the notes in view.esets it on the selection (empty input removes it,Zundoes) and=narrows to its value.:propertiesfilter, same shape as:meta:(("COMMIT_ID" . "abc") ("CREATED_TS" . t)). In queries it'sprop:KEY=VALUE/prop:KEY=*, in the buffer/ p. Keys are case-insensitive like in org. When no tag condition is cheaper, it's pushed down to the property index.(fn NAME FUNCTION)computed columns: FUNCTION gets the note and returns the cell, so anything derivable from a note can be a column.Property writes locate the entry by its ID rather than the stored position, since positions go stale once an earlier write in the same batch touched the file.
README and CHANGELOG are updated.