"Bruce D'Arcus" writes:
> 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.
Thanks!
Applied onto main
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 something with my testing
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 just tested it, and it works as
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 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
Dear All,
On Mon, 4 Jul 2022 at 14:27, Ihor Radchenko wrote:
> András Simonyi writes:
> I do not agree.
> If someone sets up natbib for latex export and basic for other formats,
> "*" will not be correctly exported in those other formats (because basic
> does not support @* syntax) -
András Simonyi writes:
> I think that the problem with simply adding one or more new activation
> processors with different fontification for the "*" key is that Org
> has no way of knowing (at least for sure) which export processor will
> be used for a exporting a certain Org buffer, since it
András Simonyi writes:
> Thanks, I have tried to address your comments in the attached new
> version of the patch.
> Note that the quotes around "csl" follow the manual's "Citation
> handling" chapter.
Since the fontification part appears to be unrelated to this particular
patch, I'd like to
Dear All,
On Sun, 3 Jul 2022 at 15:09, Ihor Radchenko wrote:
> Then, oc-natbib, oc-biblatex, and oc-csl should be modified to provide
> an alternative activation function that will not highlight @* as
> non-existing key.
>
> Probably, we can even use an alternative "special" key face, not
>
John Kitchin writes:
> It is a special command. See
>
> https://texfaq.org/FAQ-nocitestar
>
> It is used to put all entries in a bibtex file in the bibliography.
>
> Here is a minimal example Tex file that should list all the entries in
> mybibliography.bib
>
> \documentstyle{article}
>
It is a special command. See
https://texfaq.org/FAQ-nocitestar
It is used to put all entries in a bibtex file in the bibliography.
Here is a minimal example Tex file that should list all the entries in
mybibliography.bib
\documentstyle{article}
\begin{document}
\nocite{*}
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 processors.
>
> I am sorry, but I
"Bruce D'Arcus" writes:
> Ihor - on *, he is bringing oc-csl in line with the oc-natbib and
> oc-biblatex processors.
I am sorry, but I still do not understand. AFAIK, \nocite{*} is not a
valid LaTeX command.
Best,
Ihor
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?
> >
>
András Simonyi writes:
>> By "*", do you mean something like [cite/n:@*]?
>> If so, will it be correctly fontified as an existing citation?
>
> ... As for fontification, this is a very good
> question! I've checked it now with the built-in "basic"
> activation processor and it shows the "*" with
Dear Ihor,
thanks a lot for your reply!
On Sat, 2 Jul 2022 at 06:37, Ihor Radchenko wrote:
> By "*", do you mean something like [cite/n:@*]?
> If so, will it be correctly fontified as an existing citation?
Yes I meant exactly that. As for fontification, this is a very good
question! I've
András Simonyi writes:
> the attached patch adds support for nocite citations in the csl
> org-cite export processor, including support for using the special key
> "*" to include all entries in the bibliography.
Thanks!
By "*", do you mean something like [cite/n:@*]?
If so, will it be correctly
Dear All,
the attached patch adds support for nocite citations in the csl
org-cite export processor, including support for using the special key
"*" to include all entries in the bibliography.
best wishes,
András
From 3e6514d2e2f4fa68462a02578880b126e3116739 Mon Sep 17 00:00:00 2001
From:
18 matches
Mail list logo
