Yes, 9.5.
I'm curious about the timeline too.
On Wed, Jul 21, 2021, 8:36 AM Denis Maier wrote:
> Hi,
> I'm helping a scholar at my institution with his emacs/org-mode
> installation. As he'll would like to have automatic citations I
> suggested he should try the new org-cite features, but he
UC that should ensure that they are available to
> your package, as long as you have an
> :after (org oc)
> line in the package's use-package directive.
>
> On Thu, Jul 22, 2021 at 6:31 AM Bruce D'Arcus wrote:
>>
>> The problem was load order I guess; putting this of the
) that it shouldn't break starting
Emacs.
On Thu, Jul 22, 2021 at 4:27 AM Bruce D'Arcus wrote:
> If I comment out those lines and use the oc-basic style selector
> instead to start emacs, and from there reactivate this function and
> compile and reload the code from the buffer, THEN it work
Another odd thing.
If I comment out those lines and use the oc-basic style selector
instead to start emacs, and from there reactivate this function and
compile and reload the code from the buffer, THEN it works without
error.
On Wed, Jul 21, 2021 at 10:17 PM Bruce D'Arcus wrote:
>
> BTW,
traight/build-28..." nil t)
require(bibtex-actions-org-cite nil nil)
On Wed, Jul 21, 2021 at 11:14 AM Bruce D'Arcus wrote:
>
> I have run into a problem in implementing a "select-style" function
> for an org-cite-insert-processor.
>
> The WIP code is here:
>
>
I have run into a problem in implementing a "select-style" function
for an org-cite-insert-processor.
The WIP code is here:
https://github.com/bdarcus/bibtex-actions/pull/182
It was running correctly yesterday morning, but now it doesn't.
I have two related issues:
1. I think, but am not
On Tue, Jul 20, 2021 at 8:50 AM Denis Maier wrote:
> > Certainly in the CSL world, this has never been supported, and I don't
> > ever recall it ever coming up (though I'm sure someone on the Zotero
> > forum raised it at some point)
>
> I'm pretty sure I've brought that up at some point :-)
I'm working on a select-style function for org-cite, where I am adding
previews to the style list.
Current screenshot, with the natbib mapping:
https://user-images.githubusercontent.com/1134/126326341-15ec2046-bf34-411a-a7d8-f2cbe85769c3.png
But to do that best and most consistently (next step
On Mon, Jul 19, 2021 at 8:48 PM John Kitchin wrote:
>
> On Mon, Jul 19, 2021 at 7:28 PM Emmanuel Charpentier
> 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.
>>
>>
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
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
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
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
Unlike John, I don't have a working demo of this particular smaller idea,
but as it relates to the styles/commands question, I thought I'd mention it.
So the idea is to use the style completion UI to show the user what the
options are, by including the export preview; for the tex export
On Sat, Jul 17, 2021 at 10:20 AM Vikas Rawal wrote:
> Thanks, Bruce and John. Indeed, I used biblatex with natbib=true
> option, which gives me citet and citep in biblatex. But using
> \autocite and \textcite is perfect.
>
> I am noticing a few other issues at this stage.
>
> I have a large
We were posting at the same time :-)
On Sat, Jul 17, 2021 at 8:39 AM John Kitchin wrote:
> There is not currently a way to get \citet and \citep with the biblatex
> backend.
Yes, but \autocite andt \textcite produce the expected output, and
have the advantage they are independent of output
On Sat, Jul 17, 2021 at 7:41 AM Vikas Rawal wrote:
> What is the equivalent here of the various citation commands that something
> like biblatex or bibtex provide? The two most common citation commands I use
> are citet and citep (or parencite). These are used to produce the following
> kind
BTW, Nicolas added a helpful function towards the end, which returns
both the full style and variant and names, and also the shortcuts.
(org-cite-supported-styles '(natbib biblatex))
On Fri, Jul 16, 2021 at 2:15 PM John Kitchin wrote:
>
> Hi all,
> It looks like this is not a supported style for the new cite syntax:
>
> [cite/author*:@swain-2016-chemd]
>
> I think it should be allowed, because it maps cleanly to the natbib cite type
> of \citeauthor*. There are a bunch of
On Fri, Jul 16, 2021 at 12:07 PM William Denton wrote:
> However, I was a bit surprised when I found that a commented line starts a new
> paragraph.
I hadn't yet discovered that, but I think it should be considered a
bug. The output of your example should remove the commented line
entirely, and
FWIW, I ran into this issue.
After installing org, oc-csl looks in the wrong path for the etc files.
On Mon, Jul 12, 2021 at 2:07 PM Timothy wrote:
>
> Hello,
>
> It's come to my attention that the current value of
> org-cite-ctl--etc-dir is problematic for anyone managing Org with
> package.el
As I'm trying to put together a PR for the doom module for adding
org-cite support [1], I'm realizing I really don't understand
use-package very well.
Could someone with some expertise in this area recommend how I do the following?
Load org-cite and it's associated packages (oc-basic, oc-natbib,
Can we merge this patch now?
On Wed, Jun 30, 2021 at 7:14 AM Bruce D'Arcus wrote:
>
> Looks good, Bastien, and I think reflects the consensus of that thread.
>
> But trying just now, I'm not able to apply the patch on my local repo
> for whatever reason, so haven't tested it.
>
Thanks for all your work on this Nicolas: really nice job!
On Fri, Jul 9, 2021, 2:54 AM Nicolas Goaziou wrote:
> Hello,
>
> It took years, but citations are now full part of Org syntax.
>
> Thanks to everyone involved over the time!
>
> Now, it needs to be documented, but that will come a bit
On Thu, Jul 8, 2021 at 9:43 AM Timothy wrote:
>
> Hi Nicolas,
>
> > At this point, I don’t have enough understanding of the problem to have
> > an opinion. IIUC, your example does not even mention citations. How
> > should it be used, what should be the output in LaTeX, and in UTF-8
> > export?
On Thu, Jul 8, 2021 at 7:46 AM Nicolas Goaziou wrote:
> In this situation, the function I want to encourage re-using is
> `org-cite-supported-styles'. `org-cite-basic--complete-style' is so
> trivial that I didn't bother exporting it.
Okay, I see now.
So `org-cite-supported-styles' returns
On Thu, Jul 8, 2021 at 8:48 AM Eric S Fraga wrote:
> ... I have lost track of what is going on in the emacs-sphere
> when it comes to completion frameworks. I use ivy/counsel. Is there
> somewhere a good summary of the state of play? Would I wish to move to
> another framework?
You're not the
On Thu, Jul 8, 2021 at 7:46 AM Nicolas Goaziou wrote:
> In this situation, the function I want to encourage re-using is
> `org-cite-supported-styles'. `org-cite-basic--complete-style' is so
> trivial that I didn't bother exporting it.
OK, I'll take a closer look at that.
Bruce
On Wed, Jul 7, 2021 at 6:59 PM Nicolas Goaziou wrote:
> For a developer, there are now two ways to create an insert processor.
>
> 1. If you are happy with the global behaviour of "basic", but want to
>improve completion, I added the `org-cite-make-insert-processor'
>tool.
This was very
On Thu, Jul 8, 2021 at 6:26 AM Nicolas Goaziou wrote:
>
> Hello,
>
> Timothy writes:
>
> > Bruce D'Arcus writes:
> >
> >>> wip-cite-new deals with citing from bibliographies, but I don't think it
> >>> deals with within-document referencing
On Wed, Jul 7, 2021 at 11:48 PM Timothy wrote:
> wip-cite-new deals with citing from bibliographies, but I don't think it
> deals with within-document referencing --- should it?
It doesn't now.
I guess to break down the second question further:
1. Should it?
2. Can it? Could the design be
On Wed, Jul 7, 2021 at 6:59 PM Nicolas Goaziou wrote:
> For a developer, there are now two ways to create an insert processor.
>
> 1. If you are happy with the global behaviour of "basic", but want to
>improve completion, I added the `org-cite-make-insert-processor'
>tool.
Just a little
On Sat, Jul 3, 2021 at 3:58 AM Nicolas Goaziou wrote:
> Anyway, I'll try to provide something a little more useful out of the
> box, based on your comment and Bruce D'Arcus suggestion.
Nicolas - I saw you pushed some changes, per the discussion.
First, my initial thought is the be
On Sat, Jul 3, 2021 at 10:58 AM Eric S Fraga wrote:
> > Anyway, I'll try to provide something a little more useful out of the
> > box, based on your comment and Bruce D'Arcus suggestion.
>
> But that's partly why I mentioned ivy-bibtex: solutions already exist
> and there sh
On Sat, Jul 3, 2021 at 5:20 AM Nicolas Goaziou wrote:
> > First, after adding a style, I can't see how to subsequently remove it
> > using this interface, to just have "[cite:@key]". Is that possible?
>
> Of course. Just select the empty string instead of an entry. It is done
> with C-j on
On Fri, Jul 2, 2021 at 4:05 PM Nicolas Goaziou wrote:
> "Bruce D'Arcus" writes:
> > If I select that, "nil" is added to the citation, so that the result
> > is "[cite/nil:@key]".
>
> That's expected. "nil" is the name o
On Fri, Jul 2, 2021 at 5:21 PM Nicolas Goaziou wrote:
>
> Hello,
>
> John Kitchin writes:
>
> > I would not use a prefix arg here. you should just check what is at the
> > point, and if it is a citation then append it after the citation at point,
> > and if not insert a new one (maybe after
On Fri, Jul 2, 2021 at 6:33 PM Nicolas Goaziou wrote:
> The completion table, if required, and the completion mechanism belong
> to the insert function. So, you can plug anything you want.
You're right.
It is likely less work, with better results, for me to adapt what you
do with the basic
On Fri, Jul 2, 2021, 5:48 PM Nicolas Goaziou wrote:
> "Bruce D'Arcus" writes:
>
> > BTW, you may already be thinking this, but you may as well add completion
> > from the files registered with OC at this point. :-)
> >
> > Only having the completion tab
On Fri, Jul 2, 2021, 4:14 PM Nicolas Goaziou wrote:
> "Bruce D'Arcus" writes:
>
> > 1. I don't see a way to add a key to an existing citation. Editing an
> > existing key uses completing-read, rather than
> > completing-read-multiple (as for a new cit
Also:
1. I don't see a way to add a key to an existing citation. Editing an
existing key uses completing-read, rather than
completing-read-multiple (as for a new citation), and places point
after the existing key means the style editing UI will pop up.
2. If I use CRM to add multiple keys, for
Looking good Nicolas.
Just one small thing.
If I run on a citation, I get a list of styles, including "nil".
If I select that, "nil" is added to the citation, so that the result
is "[cite/nil:@key]".
On Fri, Jul 2, 2021 at 12:11 PM Nicolas Goaziou wrote:
>
> Hello,
>
> I just added an
Looks good, Bastien, and I think reflects the consensus of that thread.
But trying just now, I'm not able to apply the patch on my local repo
for whatever reason, so haven't tested it.
On Wed, Jun 30, 2021 at 6:48 AM Bastien wrote:
>
> Hi Bruce,
>
> "Bruce D'Arcus"
What's the status of this patch?
On Sun, Jun 6, 2021 at 12:55 PM Timothy wrote:
>
> Hey all,
>
> From the earlier discussion on this, I got feeling a consensus had
> reached that this is a good idea, as long as we check that latexmk is
> available first.
> As such, here is a patch changing the
On Mon, Jun 28, 2021 at 8:22 AM Eric S Fraga wrote:
>
> On Monday, 28 Jun 2021 at 08:09, Bruce D'Arcus wrote:
> > FWIW, I added a function to format org-cite here, which you can use
> > with ivy-bibtex also.
>
> Thank you. Very comprehensive. Mine is much simpler! B
On Mon, Jun 28, 2021 at 7:07 AM Eric S Fraga wrote:
> It would be nice to have this merged with master so that I can have the
> rest of my workflow at hand; e.g. I have ivy-bibtex inserting links to
> citations automatically but I have to change the format of what it
> inserts depending on which
IDK myself, as I don't use Windows. But this looks helpful?
https://emacs.stackexchange.com/questions/53957/how-to-fix-the-error-executable-zip-needed-for-creating-opendocument-files-w
On Sat, Jun 26, 2021 at 10:57 AM Brandon Taylor
wrote:
> Okay. Well, I’m running Emacs on (boo, hiss)
Oops; it does.
https://orgmode.org/manual/OpenDocument-Text-Export.html
On Sat, Jun 26, 2021, 10:54 AM Bruce D'Arcus wrote:
> MS Office supports OpenDocument, so that might be better path for org to
> support.
>
> I've wondered myself why it doesn't already support it.
>
> On
MS Office supports OpenDocument, so that might be better path for org to
support.
I've wondered myself why it doesn't already support it.
On Sat, Jun 26, 2021, 10:48 AM Brandon Taylor
wrote:
> I know we’re not supposed to really even TALK about proprietary software
> in FOSS communities like
Cool!
We should also get pandoc to support updated org-cite syntax.
https://github.com/jgm/pandoc/issues/7329
On Wed, Jun 23, 2021, 12:57 PM Anders Johansson
wrote:
> Hi all,
> I appreciate the work done on the cite functionality!
> I use zotero for managing my library and have previously
On Sat, Jun 5, 2021 at 12:13 PM Bruce D'Arcus wrote:
>
> I've been struggling with this for a while, and am a mediocre programmer, so
> thought I'd ask for help here.
I made progress on this, with one question, for Nicolas:
What's the best way to constrain the capf?
Idea is
On Sun, Jun 20, 2021 at 3:41 AM Nicolas Goaziou wrote:
...
> > The example you are highlighlighting here was why I was earlier
> > suggesting for a rule that would allow something like this input:
> >
> > "A quotation ending with a period." [cite: @hoel-71-whole].
> >
> > ... where the second
I recently switched to one-sentence-per-line + visual-line-mode.
On Fri, Jun 18, 2021 at 11:00 AM John Kitchin wrote:
>
> I use visual-line-mode. It almost always works fine for me.
>
> On Fri, Jun 18, 2021 at 10:38 AM Uwe Brauer wrote:
>>
>> >>> "ESF" == Eric S Fraga writes:
>>
>> > On
Missing word on the key sentence ...
On Mon, Jun 14, 2021 at 7:37 PM Bruce D'Arcus wrote:
> The example you are highlighlighting here was why I was earlier
> suggesting for a rule that would allow something like this input:
>
> "A quotation ending with a period."
On Mon, Jun 14, 2021 at 7:45 AM Denis Maier wrote:
>
> Below a few examples of what I mean.
>
> WDYT? Am I missing something?
>
> Denis
> ===
> #+cite_export: csl
> #+cite_export: csl
>
I'll let you two sort it out; I don't have a position.
On Sun, Jun 13, 2021, 3:23 PM Denis Maier wrote:
>
> Bruce D'Arcus hat am 14.06.2021 00:04 geschrieben:
>
>
> Nicolas explained the reverse is out of scope,
>
> IIRC, it was out of scope ATM.
>
> and gave a
Nicolas explained the reverse is out of scope, and gave a reasonable
explanation why (because much harder to reconstruct missing information
IIRC).
On Sun, Jun 13, 2021, 2:54 PM Denis Maier wrote:
> Am 12.06.2021 um 11:39 schrieb Nicolas Goaziou:
> > Hello,
> >
> > Denis Maier writes:
> >
> >>
On Sat, Jun 12, 2021 at 6:04 PM Nicolas Goaziou wrote:
> Of course, different punctuation marks exist, so characters are at least
> locale-dependant. But I don't know if the set is entirely determined by
> the locale or if it also depends on the "style" of the document.
It's a good question. I
I'm not able to test this closely ATM, but a few things ...
On Sat, Jun 12, 2021 at 5:39 AM Nicolas Goaziou wrote:
>
> Hello,
>
> Denis Maier writes:
>
> > Yes, good this is coming.
>
> As a step forward, I rebased wip-cite-new branch with more support for
> note numbers handling.
>
> I added
Good; I was wondering about that!
On Sat, Jun 12, 2021, 8:47 AM Timothy wrote:
>
> Update: I found the thread,
> https://orgmode.org/list/87lf90b5ey@gnu.org/
>
> Timothy writes:
>
> > Regarding the Emacs 24.3 requirement, I haven't got the thread on hand
> > but IIRC Bastien said that he
On Tue, Jun 8, 2021 at 4:25 PM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > On Tue, Jun 8, 2021 at 7:36 AM Bruce D'Arcus wrote:
> >
> >> (org-cite-register-processor 'bibtex
> >> :follow #'bibtex-completion-o
On Tue, Jun 8, 2021 at 4:25 PM Nicolas Goaziou
wrote:
> > Still, I'm confused why the basic font-locking doesn't work in this
case.
>
> I know it is not terribly useful but… it works here. For example, if no
> bibliography is defined, all cite keys are red (error face).
Actually that is useful;
On Tue, Jun 8, 2021 at 7:36 AM Bruce D'Arcus wrote:
> (org-cite-register-processor 'bibtex
> :follow #'bibtex-completion-open-any)
Actually, looking at the docstrings, I don't think this will work as
is, as the follow processor "accepts two arguments, the citation or
citatio
On Tue, Jun 8, 2021 at 5:33 AM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > So would it be so simple as doing something like this, to use the
> > bibtex-completion-open function instead?
> >
> > (org-cite-register-proces
On Mon, Jun 7, 2021 at 5:27 PM Bruce D'Arcus wrote:
> So would it be so simple as doing something like this, to use the
> bibtex-completion-open function instead?
>
> (org-cite-register-processor 'basic
> :follow #'bibtex-completion-open)
>
> As in, that just tells
On Mon, Jun 7, 2021 at 5:14 PM Nicolas Goaziou wrote:
> ... would be great do something
> > like:
> >
> > (setq org-cite-basic-open bibtex-completion-open-pdf)
>
> If you want to use a different "follow" capability, you need to provide
> a different processor instead of configuring this one.
On Mon, Jun 7, 2021 at 12:53 PM Bruce D'Arcus wrote:
> ... would be great do something
> like:
>
> (setq org-cite-basic-open bibtex-completion-open-pdf)
I guess that raises a question for me about what code goes where.
Maybe instead have it set in oc.el?
(setq org-cite-open 'bibte
I'm kind of losing track of details, but two things:
First, the current oc-basic has a "follow" function that if point is
over a citation-reference (key), and one does "M-x org-open-at-point",
the bibtex entry is opened.
Very cool!
Similar to my idea to have a configurable capf, could that
On Mon, Jun 7, 2021 at 3:02 AM Ypo wrote:
>
> I've been reading you about cites. Conversation is above my head, but just in
> case it could be helpful, I would like to address a frequent problem in the
> workflow of taking notes, that advanced users suffer too.
>
> When taking notes, it's usual
+1
On Sun, Jun 6, 2021, 2:19 PM Timothy wrote:
> Hi All,
>
> I've started doing some more cross-referencing in documents exported to
> LaTeX, and a hardcoded use of \ref has begun to stand out to me as a
> rather annoying thing. Hypperef provides \autoref for adding helpful
> prefixes (section,
simple thing in oc-basic?
If not, totally fine of course, but I thought I'd mention it as I'm
trying to figure this out.
Bruce
On Sat, Jun 5, 2021 at 5:14 PM Bruce D'Arcus wrote:
>
> Round 2, which should address the "regex" todo.
>
> --8<---cut
I believe he rebased it and modified the history? So same branch.
On Sun, Jun 6, 2021, 7:36 AM András Simonyi
wrote:
> Dear All,
>
> On Fri, 4 Jun 2021 at 23:06, Nicolas Goaziou
> wrote:
>
> > > I think some kind of disambiguation strategy should be implemented for
> > > the basic citation
On Sat, Jun 5, 2021 at 5:35 PM Nicolas Goaziou wrote:
> Getting back to this thread… I'd like to see it moving forward.
Yes. This is the last missing piece I see!
> You lost me here. Punctuation moving was implemented with notes cites in
> mind (much like Pandoc, I think).
Correct. And also
Round 2, which should address the "regex" todo.
--8<---cut here---start->8---
(defun bibtex-actions-complete-key-at-point-oc ()
"Complete org-cite citation key at point.
When inserting '@' in a buffer the capf UI will present user with
a list of entries,
I've been struggling with this for a while, and am a mediocre programmer,
so thought I'd ask for help here.
I started out writing this generate capf to insert citation keys, but have
decided to make it specific to org-cite.
Here's the commented function.
TIA.
Note the "candidates" variable
On Fri, Jun 4, 2021 at 9:28 AM Nicolas Goaziou wrote:
> OK. Fixed. Thank you.
Looks good; thanks!
Bruce
On Fri, Jun 4, 2021 at 8:51 AM Denis Maier wrote:
> > I still think it would be valuable to have the option to do something
> > like this, so it works across export backends.
> >
> > #+print_bibliography: :links nil
>
> Turns out, such an option already exists, at least for biblatex:
>
On Fri, Jun 4, 2021 at 8:18 AM Eric S Fraga wrote:
>
> On Friday, 4 Jun 2021 at 14:01, Denis Maier wrote:
> > Ok, I first thought you can just add the configuration to the
> > LATEX_HEADER keywords, but that won't work since everything in there
> > is loaded before hyperref.
>
> I am not sure
I see the processor has a org-cite-csl-link-cites defcustom to set
this globally, but can one set it at the document level?
Further explanation:
The default hyperref settings in latex export in general are too much,
with boxes everywhere and garish colors.
When coupled with a note style with
On Thu, Jun 3, 2021 at 5:13 PM András Simonyi wrote:
> I think some kind of disambiguation strategy should be implemented for
> the basic citation backend to be really usable with the author-year
> style. WDYT?
I hadn't tested that, but I agree.
As you know, disambiguation can get complicated,
In the approach taken by CSL implementations, and by biblatex
autocite, when dealing with note styles, you have two kinds of
citations in notes:
1. what we might call "automatically footnoted"; citations in the
running text that get converted on export to footnotes (or endnotes)
2. citations
On Wed, Jun 2, 2021 at 12:30 PM Colin Baxter wrote:
>
>
> I'm beginning to think this change of the default should not
> happen. From this thread it seems to be that the chances of it breaking
> existing work flow is high.
I don't see how that follows. Can you clarify?
> I really don't
On Wed, Jun 2, 2021 at 4:28 AM Tim Cross wrote:
> The more I think about it, I think the best solution would be to update
> the code which sets the default and have it check for latexmk. If it is
> found, set it as the default and if it is not found, set the existing
> default. This would have
On Tue, Jun 1, 2021 at 9:09 PM Scott Randby wrote:
> As a constant user of Org's LaTeX export capability, this change would break
> my ability to export to PDF, and it would be difficult for me to fix. I don't
> support this change.
Can you explain this, Scott? Why would anything "break'?
On Tue, Jun 1, 2021 at 5:25 PM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > It seems if I have only global bibliographies set, the oc-basic
> > blue/red flagging of citekeys will always be red, even if the keys are
> > correct
On Tue, Jun 1, 2021 at 1:03 PM Timothy wrote:
>
>
> Bruce D'Arcus writes:
>
> > Thanks Timothy.
> >
> > What's your view on modifying current default?
>
> I think latexmk is a pretty reasonable expectation, and your
> justification that it's more important
Thanks Timothy.
What's your view on modifying current default?
On Tue, Jun 1, 2021, 12:36 PM Timothy wrote:
>
> Hi Bruce,
>
> In case it's of interest, I've been quite happy with this:
> https://tecosaur.github.io/emacs-config/config.html#compiling
>
> Bruce D'Arcus
While testing org-cite a few weeks ago, I noticed by default bibtex
won't run with natbib export, or biblatex with biblatex export.
Since org has not had native citations, this is not surprising.
But with org-cite coming soon, this will change.
At the time I suggested changing default to use
It seems if I have only global bibliographies set, the oc-basic
blue/red flagging of citekeys will always be red, even if the keys are
correct.
Bruce
On Sun, May 30, 2021 at 4:20 PM Nicolas Goaziou wrote:
> > Would you have this nil by default, or is there a reasonable default
> > you could set?
>
> I wrote "oc-basic" to be a reasonable, albeit very limited, default.
> I just need to make it grow JSON support first.
It might not line up with
On Mon, May 31, 2021 at 2:11 PM András Simonyi wrote:
>
> Dear All,
>
> I think a useful default/baseline for handling the occurrence of
> multiple #+print_bibliography keywords would be to implement the
> "chapter use case", which, for each #+print_bibliography, would
> collect only the
On Mon, May 31, 2021 at 10:33 AM András Simonyi
wrote:
>
> Dear All,
>
> (what follows is a copy of my reply to the corresponding citeproc-el issue)
> I think I managed to track this down. First of all, the issue doesn't
> affect html and latex Org exports, which use the html and latex output
>
On Sun, May 30, 2021 at 5:24 PM András Simonyi wrote:
>
> Dear All,
>
> On Sun, 30 May 2021 at 22:38, Bruce D'Arcus wrote:
>
> > There is one thing I can't figure out. Here's the output I get:
> > I don't understand why that URL is included, as that entry has no URL.
On Sun, May 30, 2021 at 4:23 PM Bruce D'Arcus wrote:
>
> On Sun, May 30, 2021 at 4:12 PM Nicolas Goaziou
> wrote:
> >
> > Hello,
> >
> > "Bruce D'Arcus" writes:
> >
> > > 1. JSON input doesn't work for me:
> > > https://gith
On Sun, May 30, 2021 at 4:12 PM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > 1. JSON input doesn't work for me:
> > https://github.com/andras-simonyi/citeproc-el/issues/20
>
> I think I fixed this one. I cannot test it properly
On Sat, May 29, 2021 at 12:22 PM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > On Fri, May 28, 2021 at 4:31 PM András Simonyi
> > wrote:
> >
> >> Maybe instead of a full alist mapping backends to citation processors
&
For anyone here testing oc-csl, and to update Nicolas, I've reported
all the issues I've found either here, or on the citeproc-el issue
tracker.
For the latter:
1. JSON input doesn't work for me:
https://github.com/andras-simonyi/citeproc-el/issues/20
2. suppress author improvements:
On Sat, May 29, 2021 at 1:25 PM Bruce D'Arcus wrote:
>
> On Sat, May 29, 2021 at 12:34 PM Nicolas Goaziou
> wrote:
> > We dropped variant inheritance some time ago already, when the suggested
> > syntax was style/variant/subvariant... Now, "bare" and "bare-
On Sat, May 29, 2021 at 12:34 PM Nicolas Goaziou wrote:
>
> "Bruce D'Arcus" writes:
>
> > Right now, citeproc-el, and hence also oc-csl, only supports the "bare"
> > variant.
> >
> > Would it be feasible, and make sense, to fall back
On Sat, May 29, 2021 at 11:15 AM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> >> Bibliography is printed using "\printbibliography" command. Additional
> >> options may be passed to it through a property list at
201 - 300 of 483 matches
Mail list logo
