| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
- Split into two functions instead of having no-sort argument.
- Use push instead of add-to-list.
|
|
|
|
Because bog-citekey-at-point used "(thing-at-point 'word)", it didn't
handle hyphenated citekeys properly.
Now the function relies on a set of characters that are allowed to
precede citekeys.
|
|
Old `bog-citekey-p' was not being used.
|
|
Before, citekeys could be listed as either heading titles or properties,
but these two styles could not be mixed. Now, they can, and the
following method is used to find the citekey.
1. Take the citekey from title of the current heading.
2. Take the citekey from the property of the current heading.
3. If no citekey found, go to parent heading and repeat.
The process stops as soon as a citekey is found or a top-level heading
is reached.
|
|
|
|
|
|
|
|
|
|
|
|
When 4dfcc52 changed remoed the path from choices, this should have been
kept as the full path.
|
|
This should have been changed with 9f58e9b.
|
|
`bog-citekey-action' generalizes the common setup (citekey selection
from notes or from user completion) of the citekey functions, but it
doesn't allow much flexibility for functions to handle citekey selection
differently. Replacing this with `bog-citekey-from-notes' shares the
citekey selection from notes but doesn't couple this to the user
selection.
|
|
`bog-citekey-action' should not try to select a citekey from the note
context when ASK-FUNC returns non-nil.
|
|
|
|
Now citekeys can be taken either from properties or from headings. This
provides greater compatibility with org-bibtex.el.
|
|
|
|
New name, `bog-citekey-from-heading-title', provides a clearer
indication of what it is doing.
|
|
|
|
|
|
|