As Emmenuel pointed out, we missed that Nicolas already thought of
this, and you can do this:
#+org-cite-global-bibliography: nil
With that, there's no problem, and lots of flexibility.
On Mon, Jul 19, 2021 at 8:53 PM Thomas S. Dye wrote:
>
> I used to have a global bibliography that my
I used to have a global bibliography that my employees all used.
Every project also had a local bibliography for citations that
didn't appear in the global bibliography. At the end of a
project, after the editor had cleaned up the local bibliography,
I'd merge it with the global bibliography
On Mon, Jul 19, 2021 at 7:28 PM Emmanuel Charpentier <
emm.charpent...@free.fr> wrote:
> > In natbib there is \citetext{priv.\ comm.} which is used to add a
> > textual citation to the bibliography that doesn't have a key
> > associated with it.
>
> Hmmm... why should you bother to reference a
> It seems like that should not be the case, i.e. if you define BIBLIOGRAPHY
> keywords it means you do not want to use the ones
> in org-cite-global-bibliography. Is there a scenario where the union of those
> makes sense?
I second this. The local bibliographies should supercede the global.
> In natbib there is \citetext{priv.\ comm.} which is used to add a
> textual citation to the bibliography that doesn't have a key
> associated with it.
Hmmm... why should you bother to reference a personal communication ?
Such private communications may be mentionned in the text (possibly by
a
Le lundi 19 juillet 2021 à 13:54 -0400, John Kitchin a écrit :
> That doesn't seem consistent with other ways that file-local keywords
> are used though, and it would lead (for me anyway) to citing
> unintended
> references (and including unintended bib files in the export) if
> there is
> only
On Mon, Jul 19, 2021 at 1:54 PM John Kitchin wrote:
> Maybe a reasonable compromise is something like
>
> #+bibliography: :local t
>
> which could indicate not to use the global variable.
I like it!
Bruce
That doesn't seem consistent with other ways that file-local keywords
are used though, and it would lead (for me anyway) to citing unintended
references (and including unintended bib files in the export) if there is
only one bibliography file that should be used for a document.
Maybe a reasonable
Yes, you're right Emmanuel.
I guess this goes back to my file type/extension issue then.
I do expect this to be a non-issue in time though, as related packages
update to fully support all three common input formats.
On Mon, Jul 19, 2021 at 1:29 PM CHARPENTIER Emmanuel
wrote:
>
> > It seems
> It seems like that should not be the case, i.e. if you define
> BIBLIOGRAPHY keywords it means you do not want to use the ones in
> org-cite-global-bibliography. Is there a scenario where the union of
> those makes sense?
Yes indeed: you may have
- A library for background issues (e. g.
In natbib there is \citetext{priv.\ comm.} which is used to add a textual
citation to the bibliography that doesn't have a key associated with it.
I don't see a way to get something like that in org-cite, since it seems
that a key is always required.
This isn't currently recognized as a cite,
I was wondering about this the other day too, and am not sure.
It can actually be a problem, and has been for me, if you're mixing
export processors; like biblatex, and CSL (which is best to use with
json currently).
So I definitely see a downside currently, and can't think of a problem
in
The org-cite-list-bibliography-files function in oc.el returns a
combination of file-local files and the bibfiles defined
in org-cite-global-bibliography.
It seems like that should not be the case, i.e. if you define BIBLIOGRAPHY
keywords it means you do not want to use the ones
in
On Friday, 16 Jul 2021 at 12:06, William Denton wrote:
> People who write one-sentence-per-line, have you had this problem, and if so
> how
> did you handle it?
If I will be exporting to LaTeX, I do the following:
--8<---cut here---start->8---
One sentence
>
> I don't know if that works, but what about exporting to org?
>
Exporting to org works.
Vikas
It seems, something goes wrong with LaTeX export at least in git master
>8
#+PROPERTY: header-args :eval never-export :exports code :results silent
src_elisp{(delete-dups nil)}
8<
Export as LaTeX buffer:
\texttt{\texttt{(delete-dups nil)}}
I see no reason why \texttt
Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version
3.24.23, cairo version 1.16.0)
of 2021-01-18, modified by Debian
Package: Org mode version 9.3 (release_9.3 @
/usr/share/emacs/27.1/lisp/org/)
Hi,
When I am working in an indirect buffer and am currently clocked into a
Am 18.07.2021 um 07:02 schrieb Vikas Rawal:
I don't know if this is crazy. But I was wondering if it is possible
(or worth exploring as an idea) to turn #+print_bibliography into
something that can be evaluated to throw the bibliography as results
in the org file itself.
This would then allow
18 matches
Mail list logo
