| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Set the match data according to bibtex-entry-head before calling
bibtex-key-in-head. bibtex-key-in-head relies on bibtex-entry-head
having generated the most recent match data, but I was using it as
though it took care of the matching. By luck, it seems that the most
recent match data tends to be correct right after cleaning the entry.
|
|
|
|
- Use Bog-specific record of last indirect buffer instead of
clobbering org-last-indirect-buffer.
- Add variable that controls whether or not previous buffer from
bog-citekey-tree-to-indirect-buffer is replaced during the next call
(default behavior).
- Show indirect buffer in other window regardless of
org-indirect-buffer-display setting.
|
|
|
|
Use base buffer so that bog--find-citekey-heading-in-notes still tries
to find a heading in the current note file first, regardless of
whether the buffer is an indirect buffer for the note file.
|
|
|
|
Otherwise, setup file will not be loaded, which results in some
citekey headings not being found if custom TODO words are used.
|
|
Otherwise, 'g' will re-populate the buffer using Org agenda files.
|
|
Move current file check from bog-goto-citekey-heading-in-notes to
bog--find-citekey-heading-in-notes so that other functions that use
bog--find-citekey-heading-in-notes (e.g.,
bog-citekey-tree-to-indirect-buffer) have the same behavior.
|
|
|
|
This allows any link under a citekey heading to be opened, not just the
first.
|
|
|
|
|
|
|
|
|
|
|
|
These should have been updated with commit
ecf7cb67ae95cbd5031ecea6600395453dda3621.
|
|
This is already being pulled in by Org.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|