Re: Notes about citations in Org (part 3)

On Thu, Apr 29, 2021 at 10:06 AM Nicolas Goaziou wrote: > ... at this point, I would suggest to spend energy porting "citeproc-org" or > "org-ref" to > this API instead. +1 Thanks for the update, and the work, Nicolas! I agree any remaining details are best worked out in the process of

Re: wip-cite status question and feedback

On Tue, Apr 27, 2021 at 9:58 AM Denis Maier wrote: > > Your example fails on 1 because it suggests the citation attaches to > > (starts) the following sentence. > > Only if you mentally parse it as a parenthetical author-date citation. I don't think so. A period is a way we delimit sentences;

Re: wip-cite status question and feedback

On Tue, Apr 27, 2021 at 7:44 AM Denis Maier wrote: > Regarding simpler ways, why not just: > > "A simple quote." [cite: @doe p. 45] No, that's worse ;-) Let's review basic requirements: 1. a plain text document really should be readable and its semantics clear 2. a user should be able to

Re: (Not so) Short note about citations in Org

On Mon, Apr 26, 2021 at 4:02 PM Nicolas Goaziou wrote: > "Bruce D'Arcus" writes: > > Nicolas: I get that you need more code to do this, but are there other > > practical consequences of allowing more than plain-text? > > The code I need to write does not count

Re: wip-cite status question and feedback

On Mon, Apr 26, 2021 at 4:35 PM Denis Maier wrote: > Regarding the proposal: I think that could go in the right direction, > but in the current form it has the downside that you can't use the > prefix anymore, right? Not sure why you would need a prefix for this case, but org-cite has two

Re: org-cite: make 'suppress-author' a citation 'style'

On Tue, Apr 27, 2021 at 3:52 AM Denis Maier wrote: > I think Bruce's point was that author suppresion list items other than > the first lies in the jurisdiction of the citeproc, and has to be > handled depending on citation style. (I.e., user input does /not/ matter > here.) Yes, thank you;

Re: [PATCH] ox-md.el export code blocks using grave accents.

On Sat, Jan 30, 2021, 6:29 PM Tim Cross wrote: > There are no precise standards for markdown, but org states in the > manual that the version of markdown it supports is that defined at > http://daringfireball.net/projects/markdown Perhaps at some point it would make sense to change to this,

Re: (Not so) Short note about citations in Org

On Sun, Apr 25, 2021 at 5:20 PM Denis Maier wrote: > > Hi everyone, > > great to see that there's been so much progress since this issue has > last been discussed! Looks really impressive so far. > > Two comments/questions: > > - I think it should be possible to use some markup in prefixes and

Re: wip-cite status question and feedback

I had an idea on this, though it may not be a good one ... On Sat, Apr 24, 2021 at 2:39 PM Bruce D'Arcus wrote: > > On Sat, Apr 24, 2021 at 1:47 PM Nicolas Goaziou > wrote: > > > > Hello, > > > > "Bruce D'Arcus" writes: > > > >

Re: org-cite: make 'suppress-author' a citation 'style'

On Mon, Apr 26, 2021 at 5:56 AM Joost Kremers wrote: ... > IOW it seems that in biblatex, suppress-author (obtained by the asterisk > following the command) is a property of the citation command, even if it > includes multiple citations. OTOH there are real cases (I have written > references

Re: org-cite: make 'suppress-author' a citation 'style'

On Mon, Apr 26, 2021 at 3:51 AM Richard Lawrence wrote: ... > That said, here is a possible use case for this: suppose you are > referencing multiple works from a given author and want to avoid > printing the author's name multiple times, but also want to include a > further reference to a work

Re: org-cite: make 'suppress-author' a citation 'style'

On Sun, Apr 25, 2021 at 3:48 PM András Simonyi wrote: > > Dear All, > > On Sun, 25 Apr 2021 at 14:50, Bruce D'Arcus wrote: > > How would you deal with these? > > > > #+begin_example > > [cite/-:@doe20; @doe21] > > [cite/-:@doe20; see also @smith19

Re: org-cite: make 'suppress-author' a citation 'style'

On Sun, Apr 25, 2021 at 1:55 AM András Simonyi wrote: > > Dear All, > > my 2c on this issue: citeproc-el supports per cite author suppression > under the hood, but citeproc-org always maps "suppress author" mode > citations to suppressing only the first cite, because my impression > was also that

Re: org-cite: make 'suppress-author' a citation 'style'

On Sat, Apr 24, 2021 at 4:09 PM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > I also came across this post from 2018 from Andras ... > > > > https://orgmode.org/list/87in8jaywk@all.hu/ > > > > ... which inc

Re: org-cite: make 'suppress-author' a citation 'style'

I also came across this post from 2018 from Andras ... https://orgmode.org/list/87in8jaywk@all.hu/ ... which includes a link to his proposal on what we now call styles, but there he calls (a la the TeX world) commands:

Re: wip-cite status question and feedback

On Sat, Apr 24, 2021 at 1:47 PM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > Some sentence with a concluding citation [cite:@key]. > > > > ... that should end up like this: > > > > Some sentence with a concluding c

Re: org-cite: make 'suppress-author' a citation 'style'

On Sat, Apr 24, 2021, 1:08 PM Nicolas Goaziou wrote: > Hello, > > "Bruce D'Arcus" writes: > > > This distinction is wrong, and we should treat "suppress-author" as a > > citation style instead. > > > > The result would be: > >

Re: org-cite: make 'suppress-author' a citation 'style'

Correction, though it doesn't change the conclusion. On Sat, Apr 24, 2021 at 6:52 AM Bruce D'Arcus wrote: > So to get "Doe (2019) argues" you would need to write "Doe [@doe19]" > in pandoc, for example. Incorrect: the pandoc syntax for citet-like rendering is: @doe1

Re: (Not so) Short note about citations in Org

On Sat, Apr 24, 2021 at 3:53 AM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > Nicolas, > > > > Quick syntax question: > > > > On Wed, Apr 21, 2021 at 7:34 PM Nicolas Goaziou > > wrote: > > > >&g

org-cite: make 'suppress-author' a citation 'style'

Hi Nicolas, As I was working on adding a function to generate the new cite syntax, an idea occurred to me that I'd like to raise, that would simplify this model and syntax. I ran the idea by the pandoc list just to confirm my thinking was reasonable, since that has a lot of experience using

Re: (Not so) Short note about citations in Org

Nicolas, Quick syntax question: On Wed, Apr 21, 2021 at 7:34 PM Nicolas Goaziou wrote: > As a reminder, the full citation syntax is > > [cite/style:common prefix ;prefix -@key suffix; ... ; common suffix] Is the space you have here before the semi-colon significant as part of the delimiter,

Re: wip-cite status question and feedback

On Fri, Apr 23, 2021 at 9:24 AM Bruce D'Arcus wrote: > Aside: looking through the CSL spec, it doesn't seem this is > documented. It obviously should be. > > And I don't remember if that convention is locale-specific; e.g. if > while that's the standard in English, it cou

Re: wip-cite status question and feedback

On Fri, Apr 23, 2021 at 9:10 AM Bruce D'Arcus wrote: > I also forgot to mention this detail, and agree it's important to be > able to do: to modify punctuation around such "footnoted-citations". While I'm on it, one other related detail: It can be that not only does the s

Re: wip-cite status question and feedback

On Fri, Apr 23, 2021 at 8:56 AM András Simonyi wrote: > Thank you, this is very promising! I've checked the behaviour of > citeproc-org with and without a note style now and there is only one > additional minor difference which I forgot to mention, I don't know > how difficult would it be to

Re: (Not so) Short note about citations in Org

FYI, I started to implement a function to format the org-cite syntax here: https://github.com/bdarcus/bibtex-actions/pull/113 When finished, and org-cite merged, I plan to submit it for inclusion in bibtex-completion. Bruce

Re: (Not so) Short note about citations in Org

On Thu, Apr 22, 2021 at 9:14 AM Nicolas Goaziou wrote: > Now, I hope to see some work towards "oc-citeproc.el" (or any other > processor). We need it to push the limits of "oc.el", e.g., to decide if > it should provide more tools, or more breadth in its API. > > As stated already, I will be

Re: wip-cite status question and feedback

On Wed, Apr 21, 2021 at 10:47 PM Timothy wrote: > I think what would be ideal, would be if common citation styles could > define a method which produces a display string, like "Goaziou et al. > (2021)". If nothing is defined, then no overlay should be produced. Make sense, but with a caveat:

Re: (Not so) Short note about citations in Org

On Wed, Apr 21, 2021, 7:34 PM Nicolas Goaziou wrote: > `:export-bibliography' > > Function rendering a bibliography. It is called with five arguments: a > list > of citations, a list of bibliography files, the style, as a string or > nil, > the export back-end, as a

Re: (Not so) Short note about citations in Org

On Wed, Apr 21, 2021 at 8:35 PM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > Great! > > > > I just pulled down the branch. > > > > This is my first time trying to run off a development branch. > > > > I ran

Re: (Not so) Short note about citations in Org

On Wed, Apr 21, 2021 at 7:34 PM Nicolas Goaziou wrote: > I just rebased "wip-cite-new" branch, which now includes citation > syntax, and an interface between external citation processors and the > rest of Org. I'll throw in a demo at the end of this message. TL;DR: > search for "Demo time".

Re: wip-cite status question and feedback

On Wed, Apr 21, 2021 at 7:51 PM Nicolas Goaziou wrote: > > Hello, > > András Simonyi writes: > > > This is a crucial point: when a note CSL style is used, the export has > > to generate footnotes "around" those citations which are not already > > in a footnote. > > Since citeproc-org generates

Re: wip-cite status question and feedback

A big +1 to everything John said. On this: On Wed, Apr 21, 2021 at 4:26 PM John Kitchin wrote: > 4. I tend to have my follow function launch a hydra menu, which provides > many action choices. I think this is easier than trying to remember a lot of > different commands that also work at the

Re: wip-cite status question and feedback

On Wed, Apr 21, 2021 at 3:57 PM John Kitchin wrote: > I guess that the actions I use most often when "opening" a citation are, > opening the pdf, going to the webpage for it, and then opening the > bibtex entry (usually to fix capitalization or something). In org-ref > though, there are a whole

Re: wip-cite status question and feedback

On Wed, Apr 21, 2021 at 1:08 PM Nicolas Goaziou wrote: > I will take care about the default back-end (hopefully before the end of > the week but don't hold your breath), but can only provide guidance for > the conversion part. I hope there is enough motivated people to give it > a try. My lisp

Re: Concerns about community contributor support

I've been thinking about this general issue over the past year, as it's a common problem regardless of project, hosting platform, etc. I do agree in general that situations where submission of ideas and patches languish without attention are a problem. But while I don't think there are any easy

Re: wip-cite status question and feedback

On Sun, Apr 18, 2021 at 9:31 AM Ihor Radchenko wrote: > > Nicolas Goaziou writes: > > > In my mind, "opening" leads to the bibliography reference, not to the > > original document. IIUC, in this situation, the location does not matter > > much, does it? > > > > In any case, Org has no clue about

Re: wip-cite status question and feedback

On Fri, Apr 16, 2021 at 1:06 PM András Simonyi wrote: > The Emacs world is currently rather BibTeX > centered, but biblatex is an important (and rather different) > alternative, and there is CSL as well which I expect to become more > and more relevant (it's citeproc-el's native format).

Re: wip-cite status question and feedback

Maybe since Nicolas has been around lately, he can weigh in? On Wed, Mar 24, 2021 at 2:28 PM M. ‘quintus’ Gülker wrote: > > Am 24. März 2021 um 09:22 Uhr -0400 schrieb Bruce D'Arcus: > > Anyone know anything else? > > Not really. I would just like to say that I am eagerly watc

Re: wip-cite status question and feedback

? On Wed, Jun 3, 2020 at 10:53 AM Bruce D'Arcus wrote: > On Wed, Jun 3, 2020 at 10:40 AM Bastien wrote: > > > Hi all, > > > > just a quick word in this thread to say that we are in feature freeze > > for Org core features (ie. everything in org*.el files, + ob.el

Re: Citations with page numbers using helm-bibtex and org-ref

On Sat, Feb 20, 2021 at 10:31 PM Adam Sneller wrote: > I currently use org-ref and helm-bibtex to manage my database of academic > sources, with one notes file per source. A lot of my sources are books. So > note typically grow over time, as I add multiple headers (each pertaining to > a

Re: wip-cite status question and feedback

Could Nicholas or Bastien please update on where this stands at this point? On Wed, Jun 3, 2020 at 10:53 AM Bruce D'Arcus wrote: > > On Wed, Jun 3, 2020 at 10:40 AM Bastien wrote: > > > Hi all, > > > > just a quick word in this thread to say that we are in feat

Re: Website revamp?

Right; shrink the banner. I meant to say "smaller" rather than "small". On Tue, Aug 4, 2020 at 12:26 PM TEC wrote: > > > Bruce D'Arcus writes: > > > On a large monitor, there's so much space that I think the features > > content would best fit unde

Re: Website revamp?

On a large monitor, there's so much space that I think the features content would best fit underneath a small banner. On Tue, Aug 4, 2020 at 12:12 PM TEC wrote: > > > Thanks for the feedback! > > Maxim Nikulin writes: > > > 03.08.2020 12:11, TEC wrote: > >> > >> To see how orgmode.org currently

Re: Website revamp?

On Tue, Aug 4, 2020 at 11:50 AM Maxim Nikulin wrote: > It seems that new variant is too mobile-centric. On a 24in monitor I > expect something more than just a banner. I agree; it looked odd when I opened it on this 27-inch monitor.

Re: Website revamp?

FWIW, I think this is a great idea! On Thu, Jul 30, 2020, 10:45 AM TEC wrote: > > Hello Russell, Amin, > > Thanks for giving me your thoughts on the idea :) > Your responses have lead me to think that this may lead somewhere. > > Russell Adams writes: > > > My feedback is that personally I

Re: wip-cite status question and feedback

On Wed, Jun 3, 2020 at 10:40 AM Bastien wrote: > Hi all, > > just a quick word in this thread to say that we are in feature freeze > for Org core features (ie. everything in org*.el files, + ob.el/ol.el). > > So let's take the time to discuss this in details for 9.5 (or later, > when it's

Re: wip-cite status question and feedback

One thing on a detail: On Fri, May 29, 2020 at 6:00 PM András Simonyi wrote: ... > From the citeproc-el (and CSL) perspective, the list of bibliography database > files, the place where the bibliography should be placed (if it's specified) > ... Particularly if citeproc.el gets incorporated

Re: wip-cite status question and feedback

On Fri, May 29, 2020 at 6:00 PM András Simonyi wrote: > > Hi, > > apologies for reacting that late (it seems that I messed up my email filtering > royally) ... I wondered what happened to you; glad you sorted it out though! ... > (i) Default ("built in") citation processor in Org > > I think

Re: wip-cite status question and feedback

Hi Bastian, On Sun, May 24, 2020 at 8:12 AM Bastien wrote: > > Hi Bruce, > > "Bruce D'Arcus" writes: > > > I'm not sure of the value of this sort of question thrown in the > > middle of a long-running, many year, conversation. You seem to assume

Re: issue tracker?

On Thu, May 21, 2020 at 4:11 AM Nicolas Goaziou wrote: ... > - Debbugs has a nice, modern, front end, too: Mumi > (). See for > example . That'd be a nice improvement. Bruce

Re: issue tracker?

Regardless, doing issue tracking, discussion, and patch submission on a ML in 2020 is pretty odd and inefficient. I would have submitted feedback here 6-12 months earlier than I did if org had a proper issue tracker. On Tue, May 19, 2020, 3:35 AM wrote: > On Mon, May 18, 2020 at 06:13:38PM

Re: (Feature to Potentially Upstream) extending org-plot.el: some work done, more to go

I don't have any specific comments, but it looks great in general, and I'd use it!

Re: wip-cite status question and feedback

On Sat, May 2, 2020 at 9:13 AM Nicolas Goaziou wrote: > I suggested to support at least "cite", "cite/text" and "cite/paren", > but it sounds like "cite/paren" is not possible with Citeproc. This > doesn't matter much, we can limit the supported set to "cite" and > "cite/text" in Citeproc. Just

Re: wip-cite status question and feedback

On Sat, May 2, 2020 at 5:51 AM Nicolas Goaziou wrote: ... > > Does that mean you'll be able to have the same or different processors > > for different backends? (Like biblatex for latex and citeproc-el for > > ODT/HTML/etc.; or when you need identical output you can use > > citeproc-el even for

Re: wip-cite status question and feedback

On Fri, May 1, 2020 at 1:38 PM Richard Lawrence wrote: > > "Bruce D'Arcus" writes: > > >> > My understanding, though, is that org "cite" would default to your > >> > last example I quote above (in natibib, citep); that there's no need > &g

Re: wip-cite status question and feedback

On Sat, Apr 25, 2020 at 4:03 PM Nicolas Goaziou wrote: ... > > My understanding, though, is that org "cite" would default to your > > last example I quote above (in natibib, citep); that there's no need > > for a dedicated "cite/paren" command, either reserved or not. > > Not necessarily.

Re: wip-cite status question and feedback

First, thanks for your work on this Nicolas; really awesome to see the progress! I'm just going to address your syntax/cite command question. I don't have concerns about the other details, and I think others are better positioned to comment on those ... On Sat, Apr 25, 2020 at 12:20 PM Nicolas

Re: adding paragraph folding to visibility cycling?

On Tue, Apr 21, 2020 at 1:51 PM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > Right now, I just keybindings for origami-toggle-all-nodes > > origami-toggle-node. > > > > But I was thinking to have this folding as a step be

Re: wip-cite status question and feedback

But ... On Sat, Apr 18, 2020 at 9:17 AM Bruce D'Arcus wrote: ... > I can't see that it's necessary to have a fourth, because I think the > result of that would be this, which doesn't make any sense. > > 4. "Doe blah blah {2017}"/"Doe blah blah {[3]}" -&g

Re: wip-cite status question and feedback

On Sat, Apr 18, 2020 at 8:48 AM Richard Lawrence wrote: > > Hi Bruce and all, > > "Bruce D'Arcus" writes: > > > Just to align what you're saying and what I'm saying: > > > > I see three commands in the pandoc syntax: standard/parenthetical, > > au

Re: adding paragraph folding to visibility cycling?

Hi Nicolas, On Sat, Apr 18, 2020 at 4:03 AM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > One feature I have always found helpful when working on long documents > > is paragraph folding; where paragraphs are folded to display just the

Re: wip-cite status question and feedback

Just one question, Richard ... On Sat, Apr 18, 2020 at 5:50 AM Richard Lawrence wrote: [...] > I think it is worth pointing out to Bib(La)TeX users that it is useful > to avoid a proliferation of citation commands in Org syntax. The syntax > discussed so far achieves this by "factoring out"

adding paragraph folding to visibility cycling?

One feature I have always found helpful when working on long documents is paragraph folding; where paragraphs are folded to display just the first line. MS Word had this very early on in its outline view, for example. I can get paragraph folding and unfolding in org using packages like origami

Re: wip-cite status question and feedback

On Mon, Apr 13, 2020 at 8:05 AM Gustav Wikström wrote: > I'm curious. So take this for what it is; I.e. curiosity. What /exactly/ is > meant with a citation here? Is it a new general concept in Org mode, or is it > something more narrow, as an extension for some specific third party >

Re: wip-cite status question and feedback

On Mon, Apr 13, 2020 at 4:34 AM Stefan Nobis wrote: > [Placing bibliography with "#+bibliography: here"] > > It is smart, but I'm not sure I like using the same keyword for two > > different things. OTOH, I don't have a better idea. > > I personally also dislike one keyword for completely

Re: wip-cite status question and feedback

On Sun, Apr 12, 2020 at 6:19 PM Nicolas Goaziou wrote: > denis.maier.li...@mailbox.org writes: > > > Just one question concerning typed citations. citeX is good and > > concise, but why limit this to only one character? > > Because… it is good and concise? ;) > > > What about allowing something

Re: wip-cite status question and feedback

On Sun, Apr 12, 2020 at 11:58 AM Nicolas Goaziou wrote: > > "Bruce D'Arcus" writes: > > > In that case, since it was a typo, I would do as pandoc does: treat it > > as a string. > > Do you mean: keep all spaces wherever they may be? No, I thought your point about auto-filling was a good one.

Re: wip-cite status question and feedback

On Sun, Apr 12, 2020 at 11:32 AM Nicolas Goaziou wrote: > > "Bruce D'Arcus" writes: ... > > So in other words, the value of an affix would be a trimmed string? > > That was a typo. But that's a good question anyway. > > Generally speaking, I'd rather avo

Re: wip-cite status question and feedback

I'm going to split off the syntax part of your email, Nicholas, for quick comment. I need to think more about the other questions. On Sun, Apr 12, 2020 at 10:02 AM Nicolas Goaziou wrote: > > Finally, what does the above example look like when, say, there are > > two cites (say @doe2020 and

Re: wip-cite status question and feedback

Hi, On Sun, Apr 12, 2020 at 6:38 AM Nicolas Goaziou wrote: > Anyway, Org cite syntax should: > - fully support CSL, > - allow changing globally style of cites, > - be extensible enough to support « advanced » citation markup (NatBib, > Biblatex…), > - degrade gracefully when using less

Re: wip-cite status question and feedback

On Sat, Apr 11, 2020 at 5:43 PM wrote: ... > Well, that depends on your target. If you aim for CSL than that's already > fairly complete. (Even it's more than complete since the current CSL > specification only knows normal citations. Suppressing authors is done by > calling applications, and

Re: wip-cite status question and feedback

On Wed, Apr 8, 2020, 5:32 AM Nicolas Goaziou wrote: [snip] > Sounds like a plan. Let me summarize it a bit : > > 1. [ ] Finalize Org citation syntax. It is mostly good, but we need to >decide about the following points: > >- [ ] Should it include both "(cite):" and "cite:", i.e., does

Re: wip-cite status question and feedback

On Fri, Apr 10, 2020 at 5:30 AM wrote: ... > [Para [Cite [Citation {citationId = "doe", citationPrefix = [], > citationSuffix = [], citationMode = NormalCitation, citationNoteNum = 0, > citationHash = 0}] [Str "[@doe]"]] I just wanted to add a quick note on this, in case anyone is wondering:

Re: wip-cite status question and feedback

On Thu, Apr 9, 2020 at 7:17 PM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > Another question on the syntax. > > > > Does it support something like this in the pandoc syntax? > > > > Doe [-@doe19] argues ... >

Re: wip-cite status question and feedback

Another question on the syntax. Does it support something like this in the pandoc syntax? Doe [-@doe19] argues ... The minus sign signals to suppress the author rendering, so that you end up with: Doe (2019) ... instead of: Doe (Doe, 2019) I know latex works differently, but this is simple,

Re: wip-cite status question and feedback

On Thu, Apr 9, 2020 at 5:30 AM Bruce D'Arcus wrote: ... > FWIW, I asked about this on the CSL developers subforum, and got a > very helpful reply from Denis Maier, first discussing the pandoc > citation model and parsing, and then the org citation syntax and > global affixes

Re: wip-cite status question and feedback

On Thu, Apr 9, 2020 at 3:38 AM Albert Krewinkel wrote: > > Hello, > > Bruce D'Arcus writes: > > > On Wed, Apr 8, 2020 at 5:32 AM Nicolas Goaziou > > wrote: > >> "Bruce D'Arcus" writes: > >> > >> > Note that in CSL processors,

Re: wip-cite status question and feedback

On Wed, Apr 8, 2020 at 9:39 AM John Kitchin wrote: > If I were to dream, each cite would have text-properties that include the key > (so it is easy to get the key at point and do something with info in the > corresponding database), and a help-echo function that could be user-defined, > a

Re: wip-cite status question and feedback

On Wed, Apr 8, 2020 at 5:32 AM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > Note that in CSL processors, the locators are meaningful key-values, > > basically; not plain text strings. > > OK, but it is enough for Org to

Re: wip-cite status question and feedback

On Tue, Apr 7, 2020 at 5:13 PM Joost Kremers wrote: > On Tue, Apr 07 2020, Bruce D'Arcus wrote: > > While I of course can't speak for John, I would hope and expect > > org > > ref to support the new syntax. > > > > I would hope and expect the same of other pack

Re: wip-cite status question and feedback

Sorry for the typos, and also a more important mistake: a didn't mean citeproc-hs, but citeproc-rs. https://github.com/cormacrelf/citeproc-rs On Tue, Apr 7, 2020 at 2:27 PM Bruce D'Arcus wrote: > > Thank you for this thorough reply, Nicholas! > > See below. > > On Tue, Apr

Re: wip-cite status question and feedback

Thank you for this thorough reply, Nicholas! See below. On Tue, Apr 7, 2020 at 1:51 PM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > Hi everyone; first post. > > Welcome! > > > I see from the archive there was an en

wip-cite status question and feedback

Hi everyone; first post. >From what I can tell, there was a lot of activity here a few years back to define org citation link support, which was reflected in what seems to be a fairly developed wip-cite branch of the git repo. But that stalled somewhere, and we still have diverse tools, using

<    1   2   3   4   5