Implement simple custom columns for dynamic blocks - #515
Open
libanp wants to merge 1 commit into
Open
Conversation
Allows passing a function in an org-ql dynamic block's columns list to act on a matched heading's Org element.
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
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.
I've implemented a simple custom columns mechanism. There is a
customcolumn type that takes a function and applies it toelement. Though I notice there's a line saying "MAYBE: custom column functions", so I understand if this is something you'd rather not support or if you'd prefer a different approach.It currently works like:
Lambdas work too e.g by adding
((lambda (x) "hi") "example")to the :columns list