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
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
1 - 100 of 444 matches
Mail list logo
