You're probably using the CSL export processor then.
On Fri, Apr 14, 2023, 9:47 AM Durham Smith wrote:
> When inserting a link a reference using org-cite (e.g
> `[cite:@name_of_ref_in_bib_file]`) and generating the latex instead of
> generating code like `\cite{name_of_ref_in_bib_file}` what
This is really cool, but doesn't there really need to be a single repo for
distribution, issue reporting, etc.?
Do you have a plan for which fork would become primary?
On Sat, Mar 11, 2023, 11:35 PM Peter Mao wrote:
> Dear Org maintainers:
>
> I don't think org-noter is part of any official
On Sat, Feb 25, 2023 at 7:31 AM M. ‘quintus’ Gülker
wrote:
> is there a way to visually hide citations in the org buffer, much like
> links are hidden?
Not exactly what you're asking for, but have you seen this activate processor?
https://github.com/andras-simonyi/org-cite-csl-activate
Bruce
On Wed, Feb 22, 2023 at 7:23 AM Ihor Radchenko wrote:
>
> Timothy writes:
>
> > Here is a list of terms which I’d feel comfortable applying to the system:
> > ⁃ export features
> > ⁃ export capabilities
> > ⁃ export snippets
>
> I am looking at the concept again, and I feel that we may be
For citar support/bugs, you should report on the github issue tracker.
But my guess: you need to install citar-embark, as a while ago, we
moved the embark-related functionality into a separate package. If
it's been a few months since you've updated, that would likely explain
it.
On Tue, Oct 25,
I'm not sure what I think about this. I can't ever recall having a
practical issue with this example (I'd expect it's more common for
people with very long cite keys?), though in the past I have had
issues with whitespace when moving around citation-references
programmatically (as, for example,
On Tue, Sep 27, 2022 at 2:25 PM Tim Cross wrote:
> Discourse is not free - either you have to pay or you have to self host.
IIRC, it is for open source projects.
Yes:
https://blog.discourse.org/2018/11/free-hosting-for-open-source-v2/
Bruce
Yes, but there are some tricky performance issues with large org files
that change a lot, since currently citar will reload the file(s)
whenever they change, but an org file that mixes notes and bib data
may change a lot even if the bib data doesn't. If you have everything
in one file, that
Yes please; and thanks for volunteering!
On Sat, Aug 13, 2022, 8:47 AM András Simonyi
wrote:
> Dear All,
>
> I'd like to volunteer to maintain oc-csl.el, which currently doesn't
> have an official maintainer as far as I can tell. As the author and
> maintainer of citeproc-el and the author of
On Sat, Aug 13, 2022 at 8:30 AM András Simonyi wrote:
>
> Dear All,
>
> On Tue, 9 Aug 2022 at 17:38, Rudolf Adamkovič wrote:
>
> > THANK YOU for working on this! I have tried the "locators" style, and
> > it works great. At last, we can write in the APA style with no hacks!
>
> thanks for your
You need to use whatever keybinding exits.
On Fri, Aug 12, 2022, 8:53 PM Tyler Grinn wrote:
>
> I need help inserting a citation with fido-mode (icomplete) enabled. I
> call org-cite-insert, select the citation I want, and press return, and
> it asks for another citation to add, filling the
On Tue, Aug 2, 2022 at 7:14 AM András Simonyi wrote:
> the attached patch adds support for three new citation styles which
> recently got supported by citeproc-el:
>
> - cite/title or cite/ti to cite only the title of an item,
> - cite/locators or cite/l to cite only the locators, and
> -
On Mon, Jul 25, 2022 at 2:26 PM András Simonyi wrote:
>
> Dear All,
>
> On Sun, 24 Jul 2022 at 09:41, Ihor Radchenko wrote:
> >
> > Thanks!
> >
> > I have made some changes to the patch, mostly fixing grammar issues (the
> > ones I can notice). I also changed the sub-section from "Bibliography
>
On Tue, Jul 19, 2022 at 4:37 PM Joost Kremers wrote:
>
>
> On Sun, Jul 17 2022, Ihor Radchenko wrote:
> > alain.coch...@unistra.fr writes:
> >
> >> My .bib file is
> >>
> >>@string{jgr="J. Geophys. Res."}
> >>@ARTICLE{chouet88,
> >>journal=jgr,
> >>author={Chouet, B.},
On Sat, Jul 9, 2022 at 2:10 AM wrote:
> I take the opportunity to say that I think that the simple
> self-contained example
>
>#+bibliography: references.bib
>[cite:@key]
>#+print_bibliography:
>
> should be part of the manual, especially since the
> 2021-07-31-citations post does
Today, I think the only advantage pdftex has is speed; it's a lot
faster to compile documents than luatex.
And maybe some advanced microtypography features, though I haven't tracked that.
Bruce
On Fri, Jul 8, 2022 at 7:25 AM wrote:
> As I do not know which of these alternatives
>
>- it is normal, this feature should not be there,
>- it is an oversight,
>- this feature is not implemented yet,
I believe this is the answer, and it's arguable (I have no opinion,
and could see
On Tue, Jul 5, 2022 at 3:28 PM Bruce D'Arcus wrote:
> > Except, and I'm not sure if I'm misunderstanding some org detail, but
> > this doesn't suppress the global bibliography. Should it?
>
> Yes, and it does in oc-biblatex.
Sorry for the noise; disregard.
It was somethi
On Tue, Jul 5, 2022 at 3:17 PM Bruce D'Arcus wrote:
>
> On Mon, Jul 4, 2022 at 7:54 AM Ihor Radchenko wrote:
>
> > Since the fontification part appears to be unrelated to this particular
> > patch, I'd like to ask people who use CSL to test the patch.
>
> I j
On Mon, Jul 4, 2022 at 7:54 AM Ihor Radchenko wrote:
> Since the fontification part appears to be unrelated to this particular
> patch, I'd like to ask people who use CSL to test the patch.
I just tested it, and it works as expected.
Except, and I'm not sure if I'm misunderstanding some org
On Thu, Jun 9, 2022 at 12:00 PM Fraga, Eric wrote:
>
> On Thursday, 9 Jun 2022 at 10:34, Bruce D'Arcus wrote:
> > It should take another few days of development and testing before I'm
> > ready to merge it, but it pretty much works now, and any help with
> > code rev
On Mon, Jul 4, 2022 at 8:57 AM András Simonyi wrote:
> It seems to me that "*" as a key is sophisticated enough that if we have to
> make a decision
> about the default fontification then it is better to err on the side
> of supposing that a user using it knows what they are doing,
+1
Bruce
I don't know the internals, I just know it works from org, though I'm not
near a computer ATM.
On Sun, Jul 3, 2022, 8:34 AM Ihor Radchenko wrote:
> "Bruce D'Arcus" writes:
>
> > Ihor - on *, he is bringing oc-csl in line with the oc-natbib and
> > oc-biblatex proce
Ihor - on *, he is bringing oc-csl in line with the oc-natbib and
oc-biblatex processors.
On Sun, Jul 3, 2022, 7:57 AM Ihor Radchenko wrote:
> András Simonyi writes:
>
> >> By "*", do you mean something like [cite/n:@*]?
> >> If so, will it be correctly fontified as an existing citation?
> >
>
On Wed, Jun 29, 2022 at 10:23 AM Timothy wrote:
>
> Hi Ihor and Stefan,
>
> >> Sure. Just trying to clarify my confusion. The inconsistency with some
> >> defcustoms using :version and some not is bugging me.
> >
> > Agreed. It would be better to be consistent with this.
>
> Given that org-mode
On Tue, Jun 28, 2022 at 10:10 AM M. Pger wrote:
> A last question though: is it possible to set the 'round' option without
> having to insert the latex header
> ```
> #+LATEX_HEADER: \usepackage[round]{natbib}
> ```
> ?
I haven't used it, but I believe the ~org-cite-natbib-options~
defcustom
On Mon, Jun 27, 2022 at 1:13 AM M. Pger wrote:
> I've recently tried to switch to org-cite, but I still have some problems
> with the basics.
First, org-cite is a framework for citations. When reporting issues
related to it, you really need to identify what processor(s) you are
seeing the
On Mon, Jun 20, 2022 at 10:13 AM David Lukeš wrote:
...
> > it's likely we'll change the date property to prefer an
> > EDTF string
>
> Will that be stored in the `raw` or `literal` field? In that case, the
> current implementation should work with (not too wild) EDTF strings.
> If not, code
On Mon, Jun 20, 2022 at 8:04 AM Ihor Radchenko wrote:
>
> "Bruce D'Arcus" writes:
>
> > I created CSL, and have helped develop the data schema.
> >
> > BTW, just to look forward, it's likely we'll change the date property
> > to prefer an EDTF string; s
On Sat, Jun 18, 2022 at 11:31 PM David Lukeš wrote:
>
> > I suspect that multiple json formats may be available in the wild. Some
> > parsed as a list of strings and some parsed as a list of numbers.
>
> > The JSON schema allows either:
>
> Ah, thanks for looking this up!
I created CSL, and have
On Sat, Jun 18, 2022 at 9:43 PM Ihor Radchenko wrote:
>
> David Lukeš writes:
>
> > I recently started to get errors like the following:
> >
> > Error during redisplay: (jit-lock-function 544) signaled
> > (wrong-type-argument "Argument is not a string or a secondary string:
> > 2007")
> >
> >
and related files, which get complicated,
and subject to further user variety; and the UI needs to keep this in
sync with the bib data
I think we understand the problem better now, however.
On Thu, Jun 9, 2022 at 12:00 PM Fraga, Eric wrote:
>
> On Thursday, 9 Jun 2022 at 10:34, Bruce D'Arcus
On Thu, Jun 9, 2022 at 10:19 AM Fraga, Eric wrote:
>
> On Thursday, 26 May 2022 at 18:24, Ihor Radchenko wrote:
> > The relevant function is org-cite-basic--parse-bibliography.
>
> To finally follow up on this, the problem is not with org-cite but
> appears to be due to my use of citar. Citar
On Sun, Jun 5, 2022 at 6:48 PM Alan Tyree wrote:
> I need some help with a debugging problem:
>
> I'm using
>
> #+cite_export: csl ~/Templates/csl/AGLC-intext.csl
>
> where AGLC-intext.csl is a custom csl file.
I'm not sure if citeproc-el checks validity before running, but have
you confirmed
On Wed, May 25, 2022 at 12:47 PM Max Nikulin wrote:
> I have had a quick glance into the code I have an additional question
> why `browse-url' is not used for `citar-file-open-external'.
The "external" here means opening files external to emacs.
The typical use case is someone wanting to use a
l.
>
> Use at least `shell-quote-argument' instead of adding double quotes.
>
> Depending on your OS I suggest to have a look at the implementation of
> `browse-url-xdg-open', `browse-url-default-macosx-browser',
> `browse-url-default-windows-browser' for an example how to start
> externa
Just curious:
I'm not familiar with Sioyek (though it looks cool!); why do you need
a lambda there?
On Wed, May 25, 2022 at 10:10 AM Alessandro Bertulli
wrote:
>
> Thanks! Precise as always.
>
> I'm not sure if it's the best way to do so, but it worked for me by
> using a lambda:
>
> (setq
On Wed, May 25, 2022 at 6:53 AM Alessandro Bertulli
wrote:
> How can I make Org open the PDF file of a resource, using an external
> application?
>
> Let me explain: with the point on a org-cite link, pressing C-c C-o asks
> me for the resource to open. Selecting the PDF file opens it with
>
On Thu, Apr 21, 2022 at 4:06 AM Nicolas Goaziou wrote:
> If there's no objection, I'll add asterisk character to the list of
> allowed characters in citation style.
It's been a month without objection. Could we please add this then?
Bruce
On Fri, May 13, 2022 at 9:32 AM Alessandro Bertulli
wrote:
> Last thing: I heard that the citation part of the manual is still
> undocumented. Is this right? If so, do you think what we discovered
> (especially about manually requiring libraries) may be useful? May I
> help?
It's not
On Fri, May 13, 2022 at 9:15 AM Alessandro Bertulli
wrote:
...
> So, shall we conclude that latexmk has an issue with correctly
> recognizing natbib and calling bibtex?
Yes!
I just tried it now, and see the same thing. It's weird, because I
don't recall seeing that before.
I'd call that a
On Fri, May 13, 2022 at 6:54 AM Eric S Fraga wrote:
>
> On Friday, 13 May 2022 at 11:55, Alessandro Bertulli wrote:
> >> Check out org-latex-pdf-process maybe?
> >
> > I don't know the library so in depth, but I'll try, thank you!
>
> I have the following in my init file:
>
> (setq
On Thu, May 12, 2022 at 2:31 PM Alessandro Bertulli
wrote:
>
> Hi Bruce,
> thank you for your help. Indeed, loading both functionalities
> (require 'oc-biblatex)
> (require 'oc-natbib)
> did the trick. That's strange, though: my version of Org (get from M-x
> org-version) is Org mode version
On Thu, May 12, 2022 at 10:48 AM Alessandro Bertulli
wrote:
>
> Hi again.
>
> After fixing org-ref, I was exploring org-cite and citar. Again, I'm not
> sure how to make everything work. When I try to export to a LaTeX pdf
> file, I got the error "user-error: Unknown processor natbib", despite
>
On Thu, May 12, 2022 at 7:11 AM Juan Manuel Macías
wrote:
> I'm not sufficiently familiar (at the moment) with org-cite, but I share
> the news here in case this new LaTeX package could have some kind of use
> for org-cite export options.
I've played with it a bit, and it does look promising.
This is an aside, but I recently learned about citeproc-lua, which adds CSL
processing directly to tex and latex.
https://github.com/zepinglee/citeproc-lua
Now included in texlive 2022.
As that evolves more (there are still missing features), it could be
another viable alternative.
On Wed, May
On Wed, May 11, 2022 at 9:55 AM Ihor Radchenko wrote:
>
> "Bruce D'Arcus" writes:
>
> >> Emm. org-cite-export-processors?
> >
> > So I recognize I don't fully understand the org export system, but
> > that sets global defaults.
> >
>
On Wed, May 11, 2022 at 9:21 AM Ihor Radchenko wrote:
>
> "Bruce D'Arcus" writes:
>
> > I just saw a post on reddit that reminded me of this issue.
> >
> > User wants to use the oc-biblatex export processor for latex export,
> > but otherwise use
On Wed, May 11, 2022 at 6:43 AM Andreas Leha
wrote:
>
> "Bruce D'Arcus" writes:
>
> > On Tue, May 10, 2022, 11:20 PM Andreas Leha
> > wrote:
> >>
> >> Hi all,
> >>
> >> how can I use the (rather) new citation engine with the b
On Tue, May 10, 2022, 11:20 PM Andreas Leha
wrote:
>
> Hi all,
>
> how can I use the (rather) new citation engine with the biblatex backend
> to export to \fullcite ?
We should add a style for this that maps to biblatex fullcite and
natbib bibentry, and which ultimately would work as well in
I just saw a post on reddit that reminded me of this issue.
User wants to use the oc-biblatex export processor for latex export,
but otherwise use oc-csl.
They want to specify styles for each.
This isn't possible currently; one has to modify the org source file
for each export target.
Is there
report it to that project?
On Wed, May 4, 2022 at 8:45 PM Alan Tyree wrote:
>
> I'm not sure.
>
> citeproc-0.9
> citeproc-org-0.2.4
>
> On Thu, 5 May 2022 at 10:34, Bruce D'Arcus wrote:
>>
>> It seems this should have been fixed late in citeproc-el in 2021:
>&g
It seems this should have been fixed late in citeproc-el in 2021:
https://github.com/andras-simonyi/citeproc-el/issues/72
Are you using the most up-to-date code?
On Wed, May 4, 2022, 8:19 PM Alan Tyree wrote:
> G'day,
> I have a citation problem. The bibtex entry is:
>
at 8:55 PM Bruce D'Arcus wrote:
>
> On Sun, Apr 3, 2022 at 7:46 PM John Kitchin wrote:
> ...
>
> > When I put my cursor on the org-cite line and press spc, I see a message
> > box pop up, and the @key has a tooltip of "BARE LINK".
>
>
>
> > D
On Thu, Apr 21, 2022 at 4:06 AM Nicolas Goaziou wrote:
> If there's no objection, I'll add asterisk character to the list of
> allowed characters in citation style.
>
> More generally, what other characters should be allowed ?
This request is to accommodate latex command names, and the only
On Wed, Apr 20, 2022 at 8:28 AM Ihor Radchenko wrote:
>
> There is an edge case triggering infinite loop in oc-basic.
>
> It is caused by bibtex-map-entries (used in
> org-cite-basic--parse-bibtex) when ran on a malformed bibtex buffer [1].
>
> The proposed patch validates the bibtex buffer
> Department of Chemical Engineering
> Carnegie Mellon University
> Pittsburgh, PA 15213
> 412-268-7803
> @johnkitchin
> http://kitchingroup.cheme.cmu.edu
>
>
>
> On Mon, Mar 21, 2022 at 8:42 AM Bruce D'Arcus wrote:
>>
>> On Mon, Mar 21, 2022 at 8:23 AM John Kitchin wrote
On Mon, Apr 18, 2022, 5:08 AM Ihor Radchenko wrote:
> John Kitchin writes:
>
> >> In contrast, [cite/citet*:@key] is likely to be used fairly frequently
> >> and has much higher chance to break things.
> >
> >
> > We have had a citet*:key link (and all the other * variants) for a long
> > time
On Thu, Apr 7, 2022 at 7:30 AM John Kitchin wrote:
> On Thu, Apr 7, 2022 at 12:17 AM Ihor Radchenko wrote:
>
>> "Bruce D'Arcus" writes:
>>
>> > On Sun, Apr 3, 2022 at 5:07 PM John Kitchin
>> wrote:
>> >>
>> >>
On Fri, Apr 8, 2022 at 3:51 PM Rick Lupton wrote:
>
> I also found this recently. The reason is that BibTeX-dialect is set by
> org-cite-basic--parse-bibliography in oc-basic.el based on the file
> extension. Renaming your bibliography file to end in “.bibtex” instead of
> “.bib” should make
On Tue, Apr 5, 2022 at 12:11 PM John Kitchin wrote:
>
> Would you find it suitable to use [cite/command:pre @key post] in general?
I think it's a reasonable approach that would appeal to some users who
would treat org as a front-end to LaTeX primarily, and obviously
previous org-ref users, and
On Sun, Apr 3, 2022 at 5:07 PM John Kitchin wrote:
>
> I was looking into using latex commands as styles in org-cite, e.g.
>
> [cite/citet:@key]. That example works fine, but [cite/citet*:@key] is not
> allowed. Could that be allowed?
I have no insight into the restriction, but I hope it can be
On Sun, Apr 3, 2022 at 7:46 PM John Kitchin wrote:
...
> When I put my cursor on the org-cite line and press spc, I see a message box
> pop up, and the @key has a tooltip of "BARE LINK".
> Does anyone else see this?
Yes; I see the same thing with your example.
Bruce
On Sat, Apr 2, 2022 at 10:50 AM Max Nikulin wrote:
> I am unsure to what degree it is Org issue, it may be partially
> citeproc.el or CSL style issues.
One quick way to narrow this down is to run it through pandoc, which
supports org-cite.
It uses a different, haskell-based, CSL processor.
On Thu, Mar 31, 2022 at 11:27 AM Max Nikulin wrote:
> >> Emphasis and bold markers may appear in plain text export. Behavior of
> >> styles is
> >> not uniform in respect to adding (unbreakable?) space before citation.
> >
> > Sorry; not following here again. Isn't the space before a
e code discards ones
> inconsistent with provided criteria. E.g. (:bare t :author nil :noauthor
> t :full nil) for \citeyear, :caps does not matter.
>
> As at was suggested earlier, /year modifier existing in oc-csl should be
> implemented for oc-natbib.
>
> [cite/author/noauthor:...] should genera
On Tue, Mar 29, 2022 at 11:23 AM Max Nikulin wrote:
...
> >> You even have managed to convince me that, besides adding missing style
> >> names, some existing ones should be adjusted. noauthor/bare for citeyear
> >> example makes for me much more sense ...
> >
> > This does need some attention,
On Mon, Mar 28, 2022 at 8:37 AM Max Nikulin wrote:
>
> On 28/03/2022 02:40, John Kitchin wrote:
> > Max Nikulin writes:
> >> On 21/03/2022 18:51, John Kitchin wrote:
> >
> > Rather than rehash a lot of experiences, I really encourage you to try
> > writing a processor that can support this. Or
On Sun, Mar 27, 2022 at 12:00 PM John Kitchin wrote:
>
>
> Nicolas Goaziou writes:
>
> > Hello,
> >
> > Max Nikulin writes:
> >
> >> Nicolas, concerning a new thread, I have an impression that you are
> >> busy with over activities since you are participating in discussions
> >> not so
On Sun, Mar 27, 2022 at 3:41 PM John Kitchin wrote:
...
> Regarding that org-cite adds an abstraction layer, how else could one
> interpret this (from
> https://blog.tecosaur.com/tmio/2021-07-31-citations.html#cite-syntax)
> other than abstraction:
>
> [cite/na/b:@key] or
I obviously can't speak for John, but on this:
On Fri, Mar 25, 2022 at 1:11 PM Max Nikulin wrote:
>
> On 21/03/2022 18:51, John Kitchin wrote:
> >
> > citenum and bibentry are the only two I am not sure have a CSL analog.
As I said in an earlier message, it's no problem to add these. Someone
On Fri, Mar 25, 2022 at 8:55 AM John Kitchin
wrote:
> I think this kind of preview is well-suited for external packages.
You may be right.
> There is a subtle point I ran into with this preview approach though,
> and that is what is the backend export you want to see? People expect
> one
On Thu, Mar 24, 2022 at 12:33 PM Vikas Rawal wrote:
>> So I'm just wondering how best to dynamically generate those previews,
>> perhaps even just using a pre-selected reference*, and if maybe oc
>> could make that easier?
>>
>
> Some kind of overlay that shows citations as they would (at least
This is an idea related to an issue John Kitchin and I were trying to
sort out a few months back, that he mentioned in another thread.
https://lists.gnu.org/archive/html/emacs-orgmode/2022-03/msg00274.html
The question is how to help users understand the relation between oc
styles and target
On Wed, Mar 23, 2022 at 7:10 AM Ihor Radchenko wrote:
>
> Dear all,
>
> There were several people who came to the last meetup looking for
> information about debugging Org mode. The last meetup was rather
> unhelpful in this regard since we dove into a specific use-case.
>
> I plan to try once
On Wed, Mar 23, 2022 at 1:19 PM Max Nikulin wrote:
> My point was that it should not be unconsciously ignored. Since the
> message was long enough, this particular complain may remain unnoticed.
> I can not say that I fully agree with your decision, but I respect it. I
> had no intention to
On Wed, Mar 23, 2022 at 6:04 PM Nicolas Goaziou wrote:
>
> Hello,
>
> "Bruce D'Arcus" writes:
>
> > On Wed, Mar 23, 2022 at 5:27 PM Nicolas Goaziou
> > wrote:
>
> >> I can add it, but "full" is already the name of a variant, so
On Wed, Mar 23, 2022 at 5:27 PM Nicolas Goaziou wrote:
>
> Hello,
>
> Dominik Schrempf writes:
>
> > (add-to-list ’org-cite-biblatex-styles ’(“full” nil “fullcite” nil nil))
> >
> > (This or something similar should be added upstream).
>
> I can add it, but "full" is already the name of a
On Wed, Mar 23, 2022 at 8:52 AM Max Nikulin wrote:
>
> On 23/03/2022 00:20, Bruce D'Arcus wrote:
> > On Tue, Mar 22, 2022 at 10:42 AM Max Nikulin wrote:
> >>
> >> John Kitchin, this thread, Sun, 20 Mar 2022 20:31:29 -0400.
> >> https://list.orgmode.org/m2sf
On Tue, Mar 22, 2022 at 10:42 AM Max Nikulin wrote:
>
> On 21/03/2022 22:19, Bruce D'Arcus wrote:
> > On Mon, Mar 21, 2022 at 10:41 AM Max Nikulin wrote:
> >
> >> A bit of routine work will alleviate some user issues:
> >> - add missed styles
> >
>
On Mon, Mar 21, 2022 at 10:41 AM Max Nikulin wrote:
...
> A bit of routine work will alleviate some user issues:
> - add missed styles
The initial list of style-command mappings was pretty comprehensive,
but we left out some of the more obscure biblatex commands because
unsure if they were
There are restrictions on where citations are allowed, and this is one of them.
Citar, and I think the oc-basic, insert processors won't allow you to
insert citations in those places.
Usually there are technical reasons for the restrictions (IIRC having
to do with fontification?), but sometimes
On Mon, Mar 21, 2022 at 9:13 AM Dominik Schrempf
wrote:
>
> “Bruce D’Arcus” writes:
>
> > On Mon, Mar 21, 2022 at 8:41 AM Dominik Schrempf
> > wrote:
> >>
> >> Thank you, I can use `citar-insert-edit` to perform this action.
> >
> > You can actually just use org-cite-insert, which is context
On Mon, Mar 21, 2022 at 8:41 AM Dominik Schrempf
wrote:
>
> Thank you, I can use `citar-insert-edit` to perform this action.
You can actually just use org-cite-insert, which is context aware.
> Now, I failed to create a full citation in the text. This corresponds to the
> `\fullcite{}' command
On Mon, Mar 21, 2022 at 8:23 AM John Kitchin wrote:
>> A package could be created, say `org-cite-literal-biblatex' which is just a
>> copy
>> of `oc-biblatex.el' with a different default `org-cite-biblatex-styles' and
>> `org-cite-biblatex-style-shortcuts' (or just sets those variables in
>>
On Mon, Mar 21, 2022 at 4:24 AM Dominik Schrempf
wrote:
> I am trying out `org-cite' right now. It works much better than the last time
> (I
> am using the `biblatex' backend right now). However, I can not find any
> documentation about the available /styles/.
>
> They are mentioned here:
On Sun, Mar 20, 2022 at 4:21 PM Dominik Schrempf
wrote:
> For what it’s worth, I use `org-ref` because fine-grained citation export with
> LaTeX (using BibTeX or BibLaTeX) only works with `org-ref`, and not with
> `org-cite`.
Part of the challenge is this isn't an apples-apples comparison;
On Sun, Mar 20, 2022 at 9:42 AM Ihor Radchenko wrote:
> For citar, why not simply using ivy-bibtex? It supports org-cite, AFAIK.
Not really; or rather minimally.
Ivy-bibtex supports, for example, inserting of org-cite citations, but
not via org-cite-insert.
So there are currently no org-cite
On Sun, Mar 20, 2022 at 10:08 AM Vikas Rawal wrote:
>>
>> > What is the general view of the community about this?
>>
>> I don't know about the general view of the community, but, as a data
>> point, I find it very sad.
>
>
> Exactly how I feel. Particularly so because org-cite was indeed inspired
On Sun, Mar 20, 2022 at 8:09 AM Vikas Rawal wrote:
> What is the general view of the community about this? Is there a
> comprehensive discussion of pros and cons of each?
Not really, but there's John's summary here:
https://github.com/jkitchin/org-ref#what-about-org-cite
The high-level
Thanks for posting this!
For Nicolas et al, my more general question about performance with
oc-basic was related to this, so you can ignore that.
On Tue, Mar 15, 2022 at 1:01 PM Jamie Matthews wrote:
>
> # Issue
> Starting emacs with emacs -Q, then navigating to a minimal example org file
>
sure why
scrolling would be impacted.
On Sun, Mar 13, 2022 at 7:28 PM Bruce D'Arcus wrote:
>
> I've seen a number of people note how slow loading of BibTeX files is in
> oc-basic.
>
> Just wondering: do we know why, and whether there are opportunities to
> improve it?
>
>
I've seen a number of people note how slow loading of BibTeX files is in
oc-basic.
Just wondering: do we know why, and whether there are opportunities to
improve it?
For comparison, parsebib (which I use in citar) is much faster.
Bruce
On Wed, Jan 12, 2022 at 11:42 AM juh wrote:
>
> On 12.01.22 15:53, Nicolas Goaziou wrote:
> > Note that Org Cite and Org Ref are, unfortunately, incompatible
> > projects. Org Cite defines citations as a new kind of object, whereas
> > Org Ref extends links to create citations. In short, you
John MacFarlane merged initial support for org-cite to the pandoc org
reader and writer.
Only available in master ATM, but could use real-world testing,
including of the org-ref -> org-cite conversion, which you can get by
using org as both input and output format.
Bruce
On Wed, Dec 8, 2021 at 8:17 AM Daniel Nemenyi wrote:
> > With Selectrum, ... (don't know what the keybinding here is)
>
> Just installed Selectrum to find out. C-j (selectrum-submit-exact-input) does
> the trick.
If you like Selectrum (Vertico is another recent, similar,
alternative), you
On Mon, Dec 6, 2021 at 9:33 AM Daniel Nemenyi wrote:
> Apologies, I did ('Thanks org-ref I'm done...'), slip of the tongue.
Oh, I missed that; sorry John.
> Could have a go though if someone could give me a pointer? But if this is
> left to the user, perhaps we should include a line in the
On Mon, Dec 6, 2021 at 8:51 AM John Kitchin wrote:
> org-ref should not get any credit for this.
Certainly not, but I don't believe anyone mentioned org-ref in this thread?
Bruce
On Mon, Dec 6, 2021 at 8:09 AM Bruce D'Arcus wrote:
> Perhaps you could customize the keybinding for exiting to get the
> behavior you want?
Or perhaps a better solution is for someone to write an
insert-processor for helm-bibtex.
It's not hard to write them.
Bruce
Presumably you're using the default "basic" org-cite-insert-processor?
If yes, that's just how it's designed, using completing-read.
Perhaps you could customize the keybinding for exiting to get the
behavior you want?
On Mon, Dec 6, 2021 at 7:56 AM Daniel Nemenyi wrote:
>
>
> Hello,
>
> I'm
1 - 100 of 483 matches
Mail list logo
