You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I received this feature request via email. Creating this issue does not mean I have thought the feature through or even endorse its implementation (yet!).
I do think that this kind of feature would be great to have, I just need to think through the design and specific variables to introduce.
Using the Name of the File Where the Capture Was Initiated From
I’d love it if QuickAdd could allow us to reference the name of the file where the capture was triggered. For example:
If I’m working on Atomic_habits.pdf, QuickAdd could provide three new variables:
- {{FILENAME_BASE}}: Atomic_habits (name without the extension).
- {{FILENAME_EXT}}: .pdf (the file’s extension).
- {{FILENAME_FULL}}: Atomic_habits.pdf (full name including the extension).
This would make it possible to easily capture content to a designated file for that specific book. For example, I could quote content from Atomic_habits.pdf directly into Atomic_habits.md.
This feature would be incredibly useful for workflows centered around books, articles, or other resources. It would simplify how we organize and capture quotes or notes based on the source material.
Supporting Custom Date Formats in Filenames
It would also be amazing if QuickAdd could support custom date formats in filenames, similar to how the Daily Notes plugin allows us to use formats like DD-MM-YYYY-dddd (e.g., 02-01-2021-Thursday).
For example, I could specify a capture-to path like:
This would create a file like notes/02-01-2021-Atomic_habits.md. This flexibility would open up a lot of possibilities for integrating QuickAdd with date-based workflows.
Why This Feature Would Be Powerful
This feature would greatly enhance the flexibility and usability of QuickAdd:
It would make it easier to organize content by source material (e.g., books, articles, etc.).
It would simplify workflows for users who work with date-based templates or need to integrate QuickAdd with other plugins like Daily Notes.
It would make QuickAdd a more powerful tool for capturing structured information efficiently, especially for workflows focused on research, reading, and note-taking.
Comment from @chhoumann: The date functionality is already implemented, see here. Pending more information from the user.
The text was updated successfully, but these errors were encountered:
I received this feature request via email. Creating this issue does not mean I have thought the feature through or even endorse its implementation (yet!).
I do think that this kind of feature would be great to have, I just need to think through the design and specific variables to introduce.
I’d love it if QuickAdd could allow us to reference the name of the file where the capture was triggered. For example:
Atomic_habits.pdf
, QuickAdd could provide three new variables:-
{{FILENAME_BASE}}
:Atomic_habits
(name without the extension).-
{{FILENAME_EXT}}
:.pdf
(the file’s extension).-
{{FILENAME_FULL}}
:Atomic_habits.pdf
(full name including the extension).This would make it possible to easily capture content to a designated file for that specific book. For example, I could quote content from
Atomic_habits.pdf
directly intoAtomic_habits.md
.This feature would be incredibly useful for workflows centered around books, articles, or other resources. It would simplify how we organize and capture quotes or notes based on the source material.
It would also be amazing if QuickAdd could support custom date formats in filenames, similar to how the Daily Notes plugin allows us to use formats like
DD-MM-YYYY-dddd
(e.g.,02-01-2021-Thursday
).For example, I could specify a capture-to path like:
This would create a file like
notes/02-01-2021-Atomic_habits.md
. This flexibility would open up a lot of possibilities for integrating QuickAdd with date-based workflows.Why This Feature Would Be Powerful
This feature would greatly enhance the flexibility and usability of QuickAdd:
The text was updated successfully, but these errors were encountered: