| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
Previously, using bog-search-notes and bog-search-notes-for-citekey
clobbered the existing agenda buffer. Make these commands output to a
Bog-specific buffer and take care to restore org-lprops after executing.
Unfortunately, this still relies heavily on Org agenda internals, but I
don't see an obvious way around this.
|
|
|
|
|
|
bog-goto-citekey-heading-in-buffer gives preference to citekeys as
heading titles over citekeys as properties.
The order of preference for bog-goto-citekey-heading-in-notes is the
citekey as a heading title in the current buffer, the citekey as a
property in the current buffer, the citekey as heading title in notes,
and, finally, the citekey as property in notes.
|
|
Before, bog-create-combined-bib only collected citekeys from a single
buffer. Extend it so that it also works with marked files in Dired.
In addition
- Rename combined bib buffer so that it includes "Bog" in the name.
- Offer to skip missing bib files instead of failing.
- Remove bog-collect-references and bog-collect-unique-references, which
overlap with the newer bog-citekeys-in-buffer [1] and should have been
removed when that function was added.
[1] ce74785920d6234072eb2ebef63bd140a25534c2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
- Fix a few places where the group or type was missing.
- Use 'directory' or 'file' instead of 'string' when appropriate.
|
|
|
|
Limit the characters that are allowed in the citekey to letters, digits,
underscores, and hyphens. This allows the citekey to be treated as a
word (temporarily expanding word constituents to include underscore and
hyphen), as opposed to explicitly specifying the characters that can
come before a citekey.
|
|
|
|
I originally allowed leading digits to account for a case where a
consortium's name started with a number. However, looking back at this,
I don't think it makes sense to change the default format for such a
rare case.
|
|
While this was implied in the docstring of `bog-citekey-format', it
wasn't actually true.
|
|
|
|
|
|
In general, 'notes' are used to refer to Org file in
`bog-note-directory'. Rename `bog-citekey-from-notes' (and related
selection functions), which refer to the context around the point in an
Org file, not the collection of note files.
|
|
|
|
|
|
See Projectile commit 2fd7ec96465aea135ff9017ce7f2001f870f7765.
|
|
|
|
|
|
|
|
In Org mode 8.2.10 (built-in version with Emacs 24.4), this function
will still throw an error if it is before the first heading. This was
fixed in Org mode commit 9ba9f916e87297d863c197cb87199adbb39da894.
|
|
Several functions use `org-find-exact-heading-in-directory' to find the
location of a citekey heading. However, when called with a citekey at
point, it is likely that the citekey is in the current file (assuming
files are arranged by general topics), so first check the current buffer
and, only if it isn't found there, search all Org files in
`bog-notes-directory'.
|
|
|
|
|
|
With the previous approach, some citekeys weren't highlighted until text
near them was changed. I'm still not certain why this is, but using
`org-font-lock-hook' seems to fix it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Previously, the names were minor variants of the corresponding
interactive function names. Rename to make it clear which functions are
internal helper functions.
|
|
|
|
|
|
Use `bog-search-notes' in `bog-search-notes-for-citekey' instead of
repeating logic. The STRING argument added to `bog-search-notes' follows
`org-search-view'.
|
|
|