-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding new tags #35
Comments
Right that's a bit confusing.
There are two things to distinguish: adding a new tag to the current zettel (which is what
What exactly do you mean by "adding text for a new tag"? If you're talking about adding the tag in the zettel YAML metadata block then that's now possible thanks to #33 which was just merged. More generally, I agree that the code needs to be refactored a little bit, since I have basically been learning elisp along with writing neuron-mode. In particular, I exclusively use |
Ah, I see, I must have missed #33 when was perusing earlier, or it was merged right before I looked. That is the exact issue I was looking at fixing myself. Fantastic work on this, and thanks for taking the time. |
Tangential note: support for tags in zettel body is in neuron's roadmap. srid/neuron#189 |
Ah right, I forgot about that, so I suggest we leave |
A little spelunking has surfaced an issue or maybe non-issue that I think deserves discussion. There are currently two functions for "adding" tags to a zettel,
neuron-add-tag
andneuron-insert-tag
. I can see the differences in both, however I am slightly confused as to their naming versus their intention.From the naming I would expect
add
to add a new tag andinsert
to insert and existing tag, though that is not the case. BOTH only query the existing tag set and present them via anivy-read
call.add
attempts to do the correct thing but doesn't add text for a new tag.I think a bit of refactoring
neuron--select-tag-from-query
is needed to properly return the text if it is a new tag. I am open to working on that, but wanted to open a discussion about the intended functionality before slamming in a PR.The text was updated successfully, but these errors were encountered: