On Sun, Dec 5, 2021 at 8:42 AM Tim Cross wrote:
> I think your working off a false premise. Your view is that org mode
> should be available in other editors/software so that others can realise
> the power and benefits it provides. I can understand that position.
>
> However, the FSF position
On Tue, Nov 30, 2021 at 9:27 AM Alex Fenton wrote:
>
> On 30/11/2021 15:09, Bruce D'Arcus wrote:
> AFAIK pandoc still doesn't support the official Org Mode syntax.
>
> ox-pandoc relies on the fact that it first exports to an intermediate
> org file before handing off to
On Tue, Nov 30, 2021 at 7:50 AM Alex Fenton wrote:
> The current version includes initial support for org citations in Org 9.5.
> This feature is experimental and I welcome feedback and reports on this or
> any other aspect of the package.
Did pandoc get support for org-cite?
There's been
On Sun, Nov 28, 2021 at 5:19 PM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > Is there any reason not to autoload the processors?
>
> I am not sure about what you mean. Could you elaborate?
Primarily I am asking if there's a way to
Is there any reason not to autoload the processors?
Bruce
On Sun, Nov 28, 2021 at 4:34 PM Jean-Christophe Helary
wrote:
>
> Considering the total incompatibility between markdown and org-mode it does
> not seem to me that ’orgdown’ is a useful name. It will only confuse people
> and generate useless comments and counter-comments wherever org-mode
On Sun, Nov 28, 2021 at 12:19 PM Bruce D'Arcus wrote:
>
> On Sun, Nov 28, 2021, 12:04 PM Rasmus wrote:
>
>> However, I think it is currently too aggressive in overwriting styles.
>>
>> Could it perhaps accept any style that is given in
>> ‘org-cite-biblatex-opt
On Sun, Nov 28, 2021, 11:25 AM Rasmus wrote:
> One frustration with oc-csl.el is that is does not like relative dirs,
> which I guess is fine overall as one would probably store styles
> centrally, somewhere, similarly to LaTeX.
>
> However, one niece that would seem useful is to simply dump
On Sun, Nov 28, 2021, 12:04 PM Rasmus wrote:
However, I think it is currently too aggressive in overwriting styles.
>
> Could it perhaps accept any style that is given in
> ‘org-cite-biblatex-options’ / ‘org-latex-packages-alist’ and only
> overwrite it if another style is explicitly specified
On Fri, Nov 26, 2021 at 5:48 AM Nicolas Goaziou wrote:
> It should now be fixed. Thanks.
Confirmed; thanks!
Bruce
On Wed, Nov 24, 2021 at 4:57 PM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > I can't fully pin this down, but I and a couple of others I've
> > discussed this with are seeing the following behavior.
> >
> > With t
I can't fully pin this down, but I and a couple of others I've
discussed this with are seeing the following behavior.
With this example:
a citation [cite:@couper2014] and another [cite:@kohn2006]
... the first citation is highlighted, and the second (and any
subsequent) is not.
In some way I
On Wed, Nov 17, 2021 at 12:18 PM Uwe Brauer wrote:
> > I type "As we have seen in section [[*Intro]]" (literally, I tend to
> > not use any keybindings or function to insert the link). This (the
> > "*Intro" inside double square brackets) is called an internal link to
> > headlines and they are
Just a head's up that org-cite support for the Doom Emacs biblio module is
now merged.
Currently works best with the new, and now default, vertico completion
module, which uses my citar package.
So basically, make sure the following are uncommented in your init.el file:
- biblio
- vertico
- org
On Fri, Nov 19, 2021 at 9:11 AM Ihor Radchenko wrote:
> WDYT?
I don't understand all the technical details, but it sounds like a
GREAT idea to me in general!
Bruce
On Wed, Nov 17, 2021 at 12:47 PM Rudolf Adamkovič wrote:
> In the meantime, can I use the BibLaTeX backend (or something else) for
> *HTML* export?
I don't believe so, unless there's some good latex -> html solution
I'm not aware of.
Bruce
On Wed, Nov 17, 2021 at 9:59 AM Rudolf Adamkovič wrote:
> I would like to start using the new citations with the APA Style. To cite in
> APA, I use a CSL file. Everything works well with Pandoc, but with Org, all
> citations with no "date" BibTeX field render as "$AUTHOR" instead of "$AUTHOR
On Fri, Nov 5, 2021 at 10:23 AM Eric S Fraga wrote:
>
> On Sunday, 31 Oct 2021 at 18:49, Bruce D'Arcus wrote:
> > For those of you who have been using oc-bibtex-actions with org-cite,
> > two relevant name changes:
> >
> > First, packages are now "citar&quo
On Thu, Nov 4, 2021 at 6:20 PM Nicolas Goaziou wrote:
> I think there are two ways forward when a relative file name is used:
>
> 1. First check `org-cite-csl-styles-dir' and, if it is nil, expand
>against `default-directory';
>
> 2. Drop `org-cite-csl-styles-dir' and always expand against
>
On Wed, Nov 3, 2021 at 11:16 AM Nicolas Goaziou wrote:
> I pushed a change along these lines in bugfix branch.
Thank you!
> Please let me know if it works for you.
This returns the correct result.
(org-cite-basic--get-year "kohn2005" nil)
How do I get that in the basic activate processor
On Wed, Nov 3, 2021 at 12:21 PM Nicolas Goaziou wrote:
> oc-basic relies on a cache. The cache key contains a hash of the
> contents of the bib file. So whenever the bib file is modified, the
> cache is invalidated, and oc-basic parses again the file.
Of course; clever!
Bruce
On Tue, Nov 2, 2021 at 1:44 PM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > This is a tiny change that just checks for a 'date' field if 'year' is
> > nil, and if present, grabs the first four characters.
>
> The date field may
For those of you who have been using oc-bibtex-actions with org-cite, two
relevant name changes:
First, packages are now "citar" and "citar-org", and the melpa recipe
simply "citar".
Naturally all related variable and functions names also change accordingly.
Second, the org-cite processor name
ier one; is that correct?
From c1b634f5c8a31ad98f7453b77fd45ab9322f9cf2 Mon Sep 17 00:00:00 2001
From: Bruce D'Arcus
Date: Fri, 29 Oct 2021 08:42:27 -0400
Subject: [PATCH] oc-basic: Add function to shorten names
* lisp/oc-basic.el (org-cite-basic--shorten-names): new function to
shorten author names
* lisp/oc-basic.e
This is a tiny change that just checks for a 'date' field if 'year' is
nil, and if present, grabs the first four characters.
Bruce
From feee2ca6d54d3495050de334c258438950494372 Mon Sep 17 00:00:00 2001
From: Bruce D'Arcus
Date: Fri, 29 Oct 2021 08:17:43 -0400
Subject: [PATCH] oc-basic: Support
On Sat, Oct 23, 2021 at 9:41 AM Ihor Radchenko wrote:
>
> Carlos Pita writes:
>
> >>> But then c-a-p is very lenient since it lists lower and upper case block
> >>> variants even when I typed a lower case prefix, and upper case usually
> >>> will go first in the list, hence promoting a seemingly
On Thu, Oct 21, 2021 at 11:58 AM Eric S Fraga wrote:
>
> Hi Bruce,
>
> thank you for the quick response.
>
> On Thursday, 21 Oct 2021 at 11:27, Bruce D'Arcus wrote:
> > Maybe I'm missing something, but why is that necessary?
>
> It's highly likely that I am missing s
On Thu, Oct 21, 2021 at 10:12 AM Eric S Fraga wrote:
>
> Dear all,
>
> simple question: how can I get org-cite to rescan my bibliography (.bib)
> file when it changes? When I'm writing a paper, as I'm doing now, I add
> entries to my bibliography as I write but org-cite is not aware of any
> new
On Thu, Oct 21, 2021 at 10:29 AM Eric S Fraga wrote:
>
> Hello all,
>
> I may be violating some coding convention but the attached patch re-uses
> the org-cite-basic-goto function from the basic org-cite processor to
> implement the follow directive for the bibtex processor. Seemed like an
>
On Tue, Oct 19, 2021 at 4:09 PM Eric S Fraga wrote:
>
> On Tuesday, 19 Oct 2021 at 22:04, Nicolas Goaziou wrote:
> >> 1. set =org-cite-basic-author-column= to a larger number
> >
> > You can ignore this step, which is useful (but is not as you report)
> > only when using `basic' insert
The cool thing about embark-act in this context is it provides actions both
in the minibuffer and in the buffer at point (in this case, when on a
citation).
So it's like merging ivy-actions and a hydra.
On Tue, Oct 19, 2021, 3:54 PM Eric S Fraga wrote:
> Nicolas & Bruce,
>
> thank you for the
Eric - since you're using selectrum, any reason why not just use
oc-bibtex-actions?
Performance should be better, and it has a template system like
bibtex-completion.
On Tue, Oct 19, 2021 at 1:18 PM Eric S Fraga wrote:
>
> Hello all,
>
> TL;DR: how can I format the suggestions listed by
.
Bruce
From bdd33dd4efc1cd237dd90dc1a5c5741604cfd807 Mon Sep 17 00:00:00 2001
From: Bruce D'Arcus
Date: Wed, 13 Oct 2021 18:04:20 -0400
Subject: [PATCH] org-manual: minor org-cite additions
* doc/org-manual.org (Handling citations): Add note and example to load
a processor package
Try adding this where you want the bibliography.
#+print_bibliography:
On Wed, Oct 13, 2021 at 5:27 PM Leszek Wroński wrote:
>
> Guys,
>
> thank you very much for your responses to my previous query. (I will
> study the ebib package more closely; as of now it does not seem to
> work with the
On Wed, Oct 13, 2021, 1:41 PM Leszek Wroński wrote:
> Thank you very much! I will explore more. The keys are correct. On
> reopening the .org file, the behavior is now consistent: clicking on
> any citation does nothing :-)
Try org-open-at-point. That at least should work.
Bruce
Forgot to reply-all ...
On Wed, Oct 13, 2021 at 11:36 AM Leszek Wroński wrote:
> I've been using Emacs for about 20 years, but I'm only now starting to
> seriously explore the Org-mode, since I read about the new citation
> options. I'd like to report my initial experience since maybe this
>
On Tue, Oct 12, 2021 at 7:28 PM John Kitchin wrote:
>
> I am not sure it really fits the model of the exporters that are in org,
> since it is basically just a pre-processing hook.
[snip]
> It also is (IMO) a part of org-ref since it uses the links that are defined
> in org-ref. I see it as
On Tue, Oct 12, 2021 at 5:16 PM John Kitchin wrote:
>
> I think the existing link capability of org-mode is completely adequate for
> cross-references. LaTeX exports are almost completely covered in org-ref. I
> made a refproc
>
On Mon, Oct 11, 2021 at 1:57 PM M. ‘quintus’ Gülker
wrote:
> As explained, the positioning is now correct. However, instead of the
> section § sign it now has two pilcrow signs ¶¶. It should be just one
> sign, and it should be a section sign rather than a pilcrow one.
Looks like § is currently
On Mon, Oct 11, 2021 at 11:54 AM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > On Mon, Oct 11, 2021 at 10:28 AM John Kitchin
> > wrote:
> >>
> >> you should probably trim each key, and re-add spaces where you want the
On Mon, Oct 11, 2021 at 10:28 AM John Kitchin wrote:
>
> you should probably trim each key, and re-add spaces where you want them in
> the function that does these kinds of things.
I realize that's an option, but something about that feels wrong to me.
We're adding a single space as prefix,
On Mon, Oct 11, 2021 at 5:40 AM Nicolas Goaziou wrote:
>
> Hello,
>
> Vikas Rawal writes:
>
> > I find it works better for me if I insert spaces between multiple
> > citations. For example: [cite: @john56; @john35; @bruce2021] rather
> > than [cite:@john56;@john35;@bruce2021].
> >
> > The of
On Sun, Oct 10, 2021 at 4:41 PM Nicolas Goaziou wrote:
> >> And if we were to add this, we'd still need to answer my first
> >> question: when and how to add specific style/variant mappings to the
> >> oc processors.
>
> It is possible to send a patch if it is something useful. Some
> processors
Just bumping this. Nicolas, in particular, any thoughts?
On Thu, Sep 9, 2021 at 2:37 PM Bruce D'Arcus wrote:
>
> The current list of styles and variants included in the oc export
> processors was a first step, with a goal to provide a solid starting
> point, and citations that are
Can we go back to this question of whether internal links are adequate
for cross-references, and if not, what's missing?
On Fri, Aug 13, 2021 at 11:22 AM Eric S Fraga wrote:
>
> Hello John & co.,
>
> I need to chime in when it comes to the UI:
>
> On Thursday, 12 Aug 2021 at 13:19, John Kitchin
On Sun, Oct 10, 2021 at 8:00 AM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > Is there any technical reason citations aren't allowed in captions?
>
> Yes, there is. Captions are somewhat fragile: they may or may not be
> included in t
Is there any technical reason citations aren't allowed in captions?
If not, could that restriction be removed?
I do note LaTeX requires special handling for that though;
\protect\cite{ref} or {\cite{ref}}.
On Fri, Oct 8, 2021 at 12:38 PM M. ‘quintus’ Gülker
wrote:
> I am not entirely sure if this is a bug, a missing feature (if so, I
> would like to request it), or a user error on my side. Please enlighten
> me.
>From reading the code, it looks like you need to set org-cite-csl-locales-dir.
Have
On Tue, Oct 5, 2021 at 3:57 PM Ypo wrote:
> I think that already works. For me it was overkilling when I tried to use it
> for my personal notes. It was too much work and it cluttered my "global"
> references.bib with an item for each cited page.
>
> But maybe that would be the correct way?
On Tue, Oct 5, 2021 at 11:04 AM Timothy wrote:
> Sounds like the general attitude is “why not?”. So I’ve turned my snippet
> into a
> patch and unless any concerns are raised in the next few days I’ll push it to
> main.
For parity, it would probably make sense to add the equivalent to
On Tue, Oct 5, 2021 at 10:42 AM John Kitchin wrote:
>
> How would this work?
>
> Does [cite/locators:@someone-2021].
>
> imply a specific field in a bibliography entry, e.g. pages, or location? and
> then CSL is responsible for formatting it to something like "p. 42" or "pp.
> 42-44", etc?
As
On Tue, Oct 5, 2021 at 9:19 AM Timothy wrote:
> > It’s just odd to have a name without any other citation marker. How
> > would a reader know it’s a citation?
>
> For context, I’m basically just using this as a way to insert the author’s
> name
> without any chance of typos.
Right.
I don't
On Tue, Oct 5, 2021 at 1:35 AM Timothy wrote:
> Is there any reason why we haven’t added `a/b', `a/bc', `a/bf', `a/bcf' ?
There is a reason, though it may not be the strongest.
It's just odd to have a name without any other citation marker. How
would a reader know it's a citation?
Is it for
On Mon, Oct 4, 2021 at 10:11 AM Bruce D'Arcus wrote:
>
> On Sun, Oct 3, 2021 at 6:23 PM Nicolas Goaziou wrote:
> >
> > Hello,
> >
> > Elias Bounatirou writes:
> >
> > > Just to clarify the BUG:
> > > Citations in a footnote in the follo
On Sun, Oct 3, 2021 at 6:23 PM Nicolas Goaziou wrote:
>
> Hello,
>
> Elias Bounatirou writes:
>
> > Just to clarify the BUG:
> > Citations in a footnote in the following environment are not exported to
> > LaTeX: when the footnote follows two or more citations, of which one has a
> > suffix,
On Sun, Oct 3, 2021 at 4:57 PM autofrettage wrote:
>
> Hi all,
>
> I have really seen forward to the release of org mode 9.5 with
> its new and shiny support for citations. The initial frenzy of
> experimentation has lead to mixed results.
>
> Right now I am trying to use the biblatex processor,
On Sun, Oct 3, 2021 at 9:18 AM Rudolf Adamkovič wrote:
>
> "Bruce D'Arcus" writes:
>
> > ATM, your only option is to do "(p. 42)."
>
> Bummer.
You could put in a feature request though ;-)
Aside: the other way to handle this, which has been discu
On Sun, Oct 3, 2021 at 6:35 AM Rudolf Adamkovič wrote:
> I use APA (via CSL) to cite and would like to write
>
> > According to Someone (2021), foo-bar (p. 42).
>
> I can almost do it with
>
> > Accordint to [cite/text:@someone-2021], foo-bar
> > .
>
> Any ideas? In APA, this pattern comes up
On Sat, Oct 2, 2021 at 1:46 AM Kyle Meyer wrote:
>
> [reordering top-posting...]
>
> Bruce D'Arcus writes:
>
> > On Fri, Oct 1, 2021 at 8:33 AM Bruce D'Arcus wrote:
> >>
> >> It looks like that /etc/csl directory isn't included in the emacs source
&g
On Sat, Oct 2, 2021 at 1:24 AM Kyle Meyer wrote:
> Is there a reason to avoid updating to the latest version?
No; updating them makes sense.
Bruce
Actually, that whole etc directory is outdated.
On Fri, Oct 1, 2021 at 8:33 AM Bruce D'Arcus wrote:
>
> It looks like that /etc/csl directory isn't included in the emacs source tree.
>
> On Fri, Oct 1, 2021 at 4:57 AM Rudolf Adamkovič wrote:
> >
> > Hi there,
>
It looks like that /etc/csl directory isn't included in the emacs source tree.
On Fri, Oct 1, 2021 at 4:57 AM Rudolf Adamkovič wrote:
>
> Hi there,
>
> I compiled Emacs from "master" (2e92f90a5d) to try the new
> citations.
>
> > ./configure --with-json
> > make
> > make install
>
> (per usual,
We have some initial documentation for org-cite included in the manual
to accompany the release of Org 9.5.
https://orgmode.org/manual/Citation-handling.html#Citation-handling
But it still needs a fair bit of work.
Questions:
1. What else should/must be added to the manual?
2. What might we
On Tue, Sep 28, 2021 at 7:42 AM Nicolas Goaziou wrote:
>
> Hello,
>
> Bastien writes:
>
> > Denis Maier writes:
> >
> >> I think the suffix parsing in oc-biblatex could be improved.
> >
> > Can you provide a patch for this?
>
> I don't think this improvement is needed. We could get away with it
Great start!
A few quick comments:
1. I'm not sure we should call them "citation links", since they
aren't really links.
2. "four bibliograhic backends are available": a) note typo (which I
think I saw elsewhere; there are a number of spelling errors
throughout), b) "available" -> "included"
On Mon, Sep 27, 2021 at 6:31 AM Bastien Guerry wrote:
>
> Hi all,
>
> Bastien writes:
>
> >> Emmanuel Charpentier (Cc'ed) wrote some nice documentation for this
> >> feature. He might want to chime in.
> >
> > that'd be great - thanks in advance Emmanuel!
>
> Just a quick heads up to mention
Pretty sure it just means no documentation has yet been written for it.
On Thu, Sep 23, 2021 at 10:19 AM Kai von Fintel
wrote:
>
> In a recent message there was a pointer to the etc/ORG-NEWS file located at
>
> http://git.savannah.gnu.org/cgit/emacs/org-mode.git/tree/etc/ORG-NEWS
>
> I take it
If inserting a new org-cite citation, one can insert multiple references.
If editing an existing citation, one can only insert one.
In ny processor, for example, the user can select multiple references,
but org-cite-insert will only insert the first one.
Is there a reason for this? Can we
Elias - do you mean org-cite-insert won't allow this?
[fn:1] [cite:@doe2019].
If yes, I don't see that; it inserts fine.
I'm using bibtex-actions for the insert processor, but I don't think
that should make any difference, since it's org-cite that's handling
that.
On Sat, Sep 18, 2021 at 4:23
I'm not going to defend what Nicolas characterized as a "terrible
idea,", but to explain a bit ...
The idea was motivated by wanting to access org-cite activate and
follow functionality from the property drawer; NOT export (which as
Nicolas says, would cause problems).
The current
Just bumping this.
Another question about where to allow cite elements.
On Fri, Aug 20, 2021 at 4:18 PM Bruce D'Arcus wrote:
>
> So this is a tentative request/question; I'm not really sure the best
> approach here.
>
> This is based on discussion with one of the org-roam-bi
The current list of styles and variants included in the oc export
processors was a first step, with a goal to provide a solid starting
point, and citations that are more-or-less portable across the
backends.
But that raises an obvious question: what next?
I'd like, for example, to suggest adding
It does seems there's a little bug with this; for in-footnote citation
outputs, but the second not.
Body text with a citation: [cite:@mcneill2011 with a suffix][fn:2].
Body text with a citation: [cite:@low2001; @mcneill2011; with a suffix][fn:3].
On Mon, Sep 6, 2021 at 7:50 AM Bruce D'Arcus
This works fine for me:
#+bibliography: test.bib
#+cite_export: biblatex verbose
Body text with a citation: [cite:@mcneill2011].
Footnote: [fn:1]
#+print_bibliography:
* Footnotes
[fn:1] A commentary, and then a citation: [cite:@low2001].
Results for the end is:
Body text with a citation:
On Tue, Aug 31, 2021 at 7:21 AM Timothy wrote:
> Thinking about this situation, inserting citations should be fine as
> long as the `point' isn't before or immediately after the bullet itself
> (i.e. no space).
I agree.
Cites in lists can be useful, including for things like CVs.
Bruce
So this is a tentative request/question; I'm not really sure the best
approach here.
This is based on discussion with one of the org-roam-bibtex developers
about what the proper way to indicate an org-roam note is a
bibliographic note; e.g. a note about a bibliographic source.
Traditionally in
On Fri, Aug 20, 2021 at 11:21 AM John Kitchin wrote:
> I think bibtex-completion is agnostic of ivy or helm, and doesn't require
> either of them to work. You can use it for candidates to selectrum if you
> want, and the other many features it offers for notes, pdf, etc...
Sorry; meant to
I think so.
I actually just started the process of removing the bibtex-completion
dependency.
Give it a try in any case. It should work well with org-cite, and you
can even use pieces of org-ref-cite if you prefer that to my
(currently) more minimal embark-based approach.
On Fri, Aug 20, 2021
Though for ODT, you might want to look into oc-csl; citeproc-el just
got improved ODF support.
https://github.com/andras-simonyi/citeproc-el/pull/45
On Fri, Aug 20, 2021 at 9:46 AM Eric S Fraga wrote:
>
> Ignore my question. The following works (had to look at the source,
> which I should have
Yes, I see it, and agree.
On Thu, Aug 19, 2021 at 10:02 AM John Kitchin wrote:
>
> If I have a link like cite:@key, it is fontified as an org-ref link, but if
> it is [[cite:@key]] it is fontified as an org-cite. That seems like a bug,
> only [cite:@key] should be fontified as an org-cite.
>
>
On Thu, Aug 12, 2021 at 1:19 PM John Kitchin wrote:
> so, I guess I am in agreement that it is option 2, and that there needs to be
> a single entry point for each one.
+1
So I guess open questions:
1. a new syntax that mirrors cite (and accompanying new
cross-reference element?), per
On Wed, Aug 11, 2021 at 1:31 PM John Kitchin wrote:
...
> > It's just there needs to be some way to distinguish among types of
> > targets, I think.
>
> At the risk of repeating myself, I don't think this is true.
Just to clarify ...yes, I agree with you; I wrote that before the
subsequent
That'd be my preferred solution, with (notwithstanding name overlap with
org-ref) an org-ref-insert entry point.
On Wed, Aug 11, 2021, 12:10 PM Timothy wrote:
> Hi Bruce, John,
>
> Regarding the issues with overloading [cite:@] syntax, would it be too
> much to
> introduce [ref:@] which would
On Wed, Aug 11, 2021 at 10:56 AM John Kitchin wrote:
> This is a bad idea to me. It is only a fuzzy link (what you call a typed
> internal link) if no one has defined it as an external link. As soon as that
> happens, then you will lose the export behavior defined for fuzzy links, and
> get
On Wed, Aug 11, 2021 at 9:53 AM John Kitchin wrote:
> > #+CAPTION: This is the caption for the next figure link (or table)
> > #+NAME: fig:SED-HR4049
> >
> > [[./img/a.jpg]]
> >
> > Or some other metadata on the target?
>
> I don't think metadata on the target helps with the cases described
>
On Wed, Aug 11, 2021 at 7:13 AM Bruce D'Arcus wrote:
> Is there a workaround for this somehow, or an alternative that gets
> the same thing in the end?
Like, if not typing the link, type the target?
>From this example from org-mode manual, the "fig" in the name keyword
coul
Here's a recent subthread on this question:
https://lists.gnu.org/archive/html/emacs-orgmode/2021-07/msg00233.html
At the end of that discussion, my argument against using citations for
cross-references:
1. Cross-references are not citations, neither conceptually, nor in
software
Hi John,
On Tue, Aug 10, 2021 at 8:58 PM John Kitchin wrote:
> ... I would like what I call an orthogonal approach for cross-references,
> orthogonal in the sense that it can coexist with org-ref, but not require
> org-ref if you don't use it. The built in internal links like [[label]] lack
I don't have a super specific suggestion ATM, but will just make the
following observation:
John Kitchin and I have been working on respective processors, and
they are modular enough that:
1) one can mix-and-match across projects
2) one can customize within each follow processor; for
On Fri, Aug 6, 2021 at 12:47 PM Thomas S. Dye wrote:
>
> Aloha Bruce,
>
> So, I tried calling ebib() with point on a key and it works in some
> instances but not in others.
Just to make sure I'm being clear, I mean this in your config:
(setq org-cite-follow-processor 'basic)
... and then, when
On Fri, Aug 6, 2021 at 11:50 AM Thomas S. Dye wrote:
>
> Aloha Eric,
>
> That function opens a window on the ebib database and displays the
> record with the key at point.
So does the oc-basic follow function not provide this?
I guess I'm unclear if one can configure ebib to open bib files by
What kind of functionality do you want associated with your citations
(when you run `org-open-at-point` on them)?
Is some or all of it specific to ebib?
Or is it more generic; opening the bib entry, notes, PDFs, etc?
Because the modular nature of org-cite makes it easy to mix-and-match
pieces
On Thu, Aug 5, 2021 at 10:41 AM Eric S Fraga wrote:
> This is for a journal that expects submissions in pandoc (never had this
> before) which (in
> some ways) is nice as at least it's not Word...
Never heard of that before either; very cool!
Bruce
Yeah, ideally ox-pandoc would be updated to support org-cite.
I also, FYI, submitted an issue to pandoc awhile ago to update it's
org-cite support (it has support for an early draft).
https://github.com/jgm/pandoc/issues/7329
On Thu, Aug 5, 2021 at 10:07 AM Eric S Fraga wrote:
>
> Dear list,
>
Hi Nicolas,
On Thu, Jul 29, 2021 at 3:28 PM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > But to do that best and most consistently (next step is CSL, for
> > example), I need the citation accessible from there, so I can run
On Wed, Jul 28, 2021 at 10:17 AM von der Malsburg, Titus
wrote:
>
>
> On 2021-07-28 Wed 15:56, John Kitchin wrote:
> > Could it be related to the variable org-mouse-1-follows-link?
>
> This variable is non-nil for me and clicking on ordinary org links works fine
> in my setup.
Just confirming:
Titus' second question got lost a bit, but does anyone have an answer?
I have the same issue, but was thinking clicking should run org-open-at-point.
I know some other people do get clickable links, so am wondering if
it's a config issue?
On Sun, Jul 25, 2021 at 10:47 AM Titus von der Malsburg
Hi Greg,
On Mon, Jul 26, 2021 at 1:56 AM Greg Minshall wrote:
> is a reasonable approach: if local, use just that; if no local, use
> global (if it exists).
>
> then, the "alternative" might be: use both local and global?
That should be the default.
But as Emmanual noted last week, there are
On Sun, Jul 25, 2021 at 11:36 AM Titus von der Malsburg
wrote:
> Sure, that’s always possible. However, my suspicion is that users in the
> majority of cases want /just/ the local bibliography when they specify one.
> If true, a better default would be to only return the local bibliography.
On Sun, Jul 25, 2021 at 10:47 AM Titus von der Malsburg
wrote:
>
>
> Hi,
>
> I’m starting to learn about org’s new capabilities for citations and
> bibliographies. Exciting, and great work!
>
> Two suggestions/requests:
>
> 1. `org-cite-list-bibliography-files' returns the bibliographies
101 - 200 of 483 matches
Mail list logo
