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 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

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

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 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 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

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

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"

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

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

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

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

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

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

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

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

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

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

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 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 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

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 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

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: 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: 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

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, 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 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: (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: 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: 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: 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: 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

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: 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?

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 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: 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: 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

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: [wip-cite-new] Adjust punctuation around citations

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 >

Re: [wip-cite-new] Adjust punctuation around citations

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."

Re: [org-cite, oc-basic] configurable open-at-point, font-locking when json?

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;

Re: Could a citation act as a link, or a link to be exported as a citation?

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

Re: [org-cite, oc-basic] configurable open-at-point, font-locking when json?

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

[org-cite, oc-basic] configurable open-at-point, font-locking when json?

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

Re: [org-cite, oc-basic] configurable open-at-point, font-locking when json?

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

Re: [org-cite, oc-basic] configurable open-at-point, font-locking when json?

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.

Re: [org-cite, oc-basic] configurable open-at-point, font-locking when json?

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

Re: [wip-cite-new] experimental citeproc-el based activation processor

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

Re: [wip-cite-new] Adjust punctuation around citations

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

Re: [wip-cite-new] Adjust punctuation around citations

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

Re: [wip-cite-new] Adjust punctuation around citations

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: > > > >>

Re: [wip-cite-new] Adjust punctuation around citations

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

Re: [wip-cite-new] Adjust punctuation around citations

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

Re: [org-cite] request for coding help on a capf to insert citation key

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

Re: [wip-cite-new] Exporting to pandoc md (and from there to zotero odt)

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

Re: [org-cite, oc-basic] configurable open-at-point, font-locking when json?

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

Re: [longlines] (was: example paper written in org completely)

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

Re: [org-cite, oc-basic] configurable open-at-point, font-locking when json?

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

Re: [wip-cite-new] New natbib processor

On Mon, May 10, 2021 at 4:22 PM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > Minor suggestion Nicolas: > > > > Currently, oc-natbib ignores global affixes. > > It is slightly more subtle. It ignores global affixes when ther

Re: [wip-cite-new] Adjust punctuation around citations

On Thu, May 13, 2021 at 5:33 PM Nicolas Goaziou wrote: > WDYT? Looks really good; thanks for this! But I get this error when I run the export to test. org-export-as: Wrong number of arguments: #, 1 Not sure what I'm doing wrong; I: 1. pulled the branch 2. ran make 3. evaled your

Re: [wip-cite-new] Adjust punctuation around citations

On Fri, May 14, 2021 at 6:26 AM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > But I get this error when I run the export to test. > > > > org-export-as: Wrong number of arguments: # > org-macro-initialize-templates>

Re: [wip-cite-new] Adjust punctuation around citations

On Fri, May 14, 2021 at 4:44 AM Denis Maier wrote: > These things are not only language dependent, but depend also on the > chosen citation style. E.g. with in-text styles you'll have (outside > outside before) in German, and American typography, in French likely as > well. > So, perhaps another

Re: [wip-cite-new] Initial implementation of `biblatex' citation processor

On Tue, May 18, 2021, 11:45 AM Nicolas Goaziou wrote: > In a rebased "wip-cite-new" branch, I made an modest attempt to write > a `biblatex' citation processor ... Looks a bit more than "modest"! I don't use biblatex either; hopefully some folks that do can test this. I'm not sure on

Re: [wip-cite-new] Initial implementation of `biblatex' citation processor

On Wed, May 19, 2021 at 6:05 AM Denis Maier wrote: > Is there a way to get a simple \cite? Hmm ... "cite/cite"? What does "cite" do that "autocite" doesn't? > Also, footcite should be there. Footcite is already there under the "note"/"fn" style. Bruce

Re: [wip-cite-new] New natbib processor

On Thu, May 6, 2021 at 8:37 AM Bruce D'Arcus wrote: > On Thu, May 6, 2021 at 8:11 AM Nicolas Goaziou wrote: > > Did I say I don't like sub-styles already? :) > > What about a middle-ground, which would be a flat list of sub-styles, like: Thinking about it more, some of

Re: CSL-JSON support for =parsebib=

On Fri, May 7, 2021 at 8:52 AM Titus von der Malsburg wrote: > It might be more elegant to have a higher-level API in parsebib. This API > could perhaps even abstract away from the underlying format (BibTeX, > CSL-JSON, or others in the future?). This would substantially simplify > matters

Re: CSL-JSON support for =parsebib=

On Fri, May 7, 2021 at 7:30 AM Joost Kremers wrote: > Now that Org is getting support for Citeproc, it could be useful to add > support > for the CSL-JSON format for bibliographic data to Emacs. Therefore, after a > friendly request from Denis Maier, I have added support for this format to the

Re: [wip-cite-new] New natbib processor

On Sun, May 9, 2021 at 4:25 PM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > To bottom line it, seems the decision comes down to something like > > these three choices: > > > > 1. no change; keep sub-styles as they are AT

Re: [wip-cite-new] New natbib processor

On Sun, May 9, 2021 at 4:57 AM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > On Fri, May 7, 2021 at 7:37 AM Bruce D'Arcus wrote: > >> Also not sure if additional are needed for the other styles; a "caps" > &

Re: [wip-cite-new] New natbib processor

On Wed, May 5, 2021 at 2:08 PM Bruce D'Arcus wrote: > I did some basic testing, and it seems to work well in general ... That was just looking at the citation output, of course. Now I did the real test: would LaTeX -> PDF work. Answer: not ATM. Here's my minimal document: [cit

Re: [wip-cite-new] New natbib processor

On Wed, May 5, 2021 at 5:25 PM Bruce D'Arcus wrote: > Now I did the real test: would LaTeX -> PDF work. > > Answer: not ATM. Probably user error, as I've not compiled bibtex + latex documents in a long time. But it doesn't appear the bib file specified in the org file gets passed

Re: [wip-cite-new] New natbib processor

BTW, if anyone else wants to test this but wasn't sure how, I put together this little gist with a minimal init and instructions. https://gist.github.com/bdarcus/2645f99363fc47ddab2aae24c5d9e66c Bruce

Re: [wip-cite-new] New natbib processor

On Thu, May 6, 2021 at 3:36 AM Denis Maier wrote: > Bruce has sent me his test files, and it turned out to be the bibstyle > (humannat), which apparently isn't included in current tex distributions. > Question: I can't see why this style should be used according to the > minimal example Bruce

Re: [wip-cite-new] New natbib processor

To come back to this On Wed, May 5, 2021, 10:53 AM Nicolas Goaziou wrote: Also it introduces ambiguities in style inheritance. > For example, if I add > > #+cite_export: natbib plainnat text > > would > > [cite//alt/caps:...] > > mean > > [cite/text/alt/caps:...] (i.e.,

Re: Need help using the dev version on windows

Not sure, but is this what you are looking for? https://orgmode.org/worg/org-tutorials/org4beginners.html#orgc1dbe4b On Thu, May 6, 2021 at 5:42 AM Denis Maier wrote: > > Hi, > > in order to test the new org-cite features I've tried installing orgmode > from the git repo. > > So, in my home

Re: [wip-cite-new] New natbib processor

On Thu, May 6, 2021 at 6:06 AM Bruce D'Arcus wrote: > If I add plainnat as style to the org file, I still get the undefined > citation error. So two things: 1. the bib file isn't include in the latex output 2. Denis noticed bibtex doesn't seem to run; maybe the pdf output option for

Re: Notes about citations in Org (part 3)

On Thu, May 6, 2021 at 7:37 AM Maxim Nikulin wrote: > > For example, do you get that with the default \cite command in latex, > > assuming the right bst file? > > Do you think something is wrong with such citations? No. I asked those questions because the focus now is on org-cite styles, and

Re: [wip-cite-new] New natbib processor

epackage{amssymb} \usepackage{capt-of} \usepackage{hyperref} \author{Bruce D'Arcus} \date{\today} \title{} \hypersetup{ pdfauthor={Bruce D'Arcus}, pdftitle={}, pdfkeywords={}, pdfsubject={}, pdfcreator={Emacs 27.2 (Org mode 9.4.5)}, pdflang={English}} \usepackage[]{natbib} \begin{document

Re: [wip-cite-new] New natbib processor

On Thu, May 6, 2021 at 10:12 AM Nicolas Goaziou wrote: > You're missing the colon at the end of the keyword. Note that `org-lint' > warns you about it. Ugh; sorry about that. I'm getting out of my depth, as I no longer use LaTeX much, but WYDT about using latexmk for export -> latex -> pdf, so

Re: [wip-cite-new] New natbib processor

Your other message, Nicolas, came in as I finished this, but I'll post this anyway. On Thu, May 6, 2021 at 8:11 AM Nicolas Goaziou wrote: > > I added the following to the wiki page, which I think addresses this: > > > > Note that `text/alt` would not make sense, as the sub-style in this case >

Re: [wip-cite-new] New natbib processor

On Thu, May 6, 2021 at 8:29 AM Nicolas Goaziou wrote: > > Hello, > > "Bruce D'Arcus" writes: > > > The question comes down to whether to support sub-styles or not, and > > if yes, what the syntax should be. > > > > I think it makes more sense

Re: Notes about citations in Org (part 3)

On Thu, May 6, 2021 at 12:05 PM Maxim Nikulin wrote: > There is might be some uncertainty concerning handling of prefixes and > suffixes. However my impression is that even e.g. \cite[p.~7]{key} is > quite rare. For completeness, keys without prefixes, suffixes could be > combined into single

Re: [wip-cite-new] New natbib processor

On Thu, May 6, 2021 at 12:20 PM Nicolas Goaziou wrote: > > I'm getting out of my depth, as I no longer use LaTeX much, but WDYT > > about using latexmk for export -> latex -> pdf, so that bibtex and > > such is properly run? > > This is controlled by `org-latex-pdf-process'; modifying it is out

Re: [wip-cite-new] Adjust punctuation around citations

On Sat, May 15, 2021 at 7:56 AM Nicolas Goaziou wrote: ... > At the moment, the `org-cite-adjust-punctuation' function is designed > with author-year to note conversion in mind, not the other way. I don't > have enough examples of the opposite transformation to even be sure the > current

Re: [wip-cite-new] New natbib processor

On Sat, May 15, 2021 at 5:29 PM Nicolas Goaziou wrote: ... > I pushed in "wip-cite-new" an attempt to parse styles as a pair (name . > variant). I also updated oc-natbib.el and oc-basic.el accordingly. Looks good to me, and seems a good balance. You mention it was "an attempt"; WDYT of the

Re: [wip-cite-new] Adjust punctuation around citations

On Sat, May 15, 2021 at 8:03 AM Bruce D'Arcus wrote: > > On Sat, May 15, 2021 at 7:56 AM Nicolas Goaziou > wrote: ... > > In any case, this explains why the docstring has a bias. I updated it to > > insist on the fact that these are rules for author-year to note > &

Re: [wip-cite-new] Initial implementation of `biblatex' citation processor

On Thu, May 20, 2021 at 6:37 PM Thomas S. Dye wrote: > > Interested lurker here. From the biblatex-chicago manual: > > "You can load the package via the usual \usepackage{biblatex}, > adding either style=chicago-notes or style=chicago-authordate" Alas, I get errors when I use that invocation.

Re: [wip-cite-new] Initial implementation of `biblatex' citation processor

On Tue, May 18, 2021 at 11:45 AM Nicolas Goaziou wrote: > I didn't test it much so it probably contains silly bugs. Sorry about > that. OK, a simple bug report. cite/bare -> \cite (currently is autocite) cite/bare-caps -> \Cite (currently is autocite) Also, not sure about the "full"

Re: [wip-cite-new] Initial implementation of `biblatex' citation processor

On Fri, May 21, 2021 at 9:13 AM Nicolas Goaziou wrote: > > Also, not sure about the "full" sub-styles. Do those have an > > equivalent in biblatex? > > This is not a bug report, but a suggestion for additional bindings, > isn't it? Yes; sorry :-) > In any case, it sounds fine to me, but Denis

Re: [wip-cite-new] Initial implementation of `biblatex' citation processor

On Thu, May 20, 2021 at 4:18 AM Denis Maier wrote: > Could be, but also [cite/text/bare] or cite/foot/bare or cite/super/bare > as they all are essentially just wrappers around the plain cite command > (textcite is a bit different, but parencite and footcite really have the > same definition as

Re: [wip-cite-new] Initial implementation of `biblatex' citation processor

On Thu, May 20, 2021 at 3:22 AM Rudolf Adamkovič wrote: > I could test this. I write multiple posts in APA style every week, all > with citations, and I cannot wait to use Org instead of LaTeX for all my > work. Is it possible to test this with use-package somehow? Note, I am > still fairly new

Re: [wip-cite-new] Initial implementation of `biblatex' citation processor

On Thu, May 20, 2021 at 7:56 AM Bruce D'Arcus wrote: > I take that summary to mean this basic question can be handled by a > combination of autocite and export config; autocite=inline (or > autocite=footnote) as default export, but of course configurable? An example of using the

Re: [wip-cite-new] Initial implementation of `biblatex' citation processor

So backing up a bit, as I was getting confused, here's [1] one summary of the different core biblatex commands. - \cite [autocite=plain]: Citations are typeset as-is; - \parencite [autocite=inline]: Citations are typeset in parentheses; - \footcite [autocite=footnote]: Citations are typeset as

[org-cite] citekey restrictions?

I was just interacting with one of the org-roam-bibtex developers about org-cite. He noted that citekeys can only start with an underscore or alpha character. Is that a necessary restriction? He, it turns out, mostly has keys of the form '2020-DOE-ABC". Bruce

Re: [org-cite] citekey restrictions?

On Sun, May 16, 2021 at 7:29 AM Nicolas Goaziou wrote: > > "Bruce D'Arcus" writes: > > > I was just interacting with one of the org-roam-bibtex developers about > > org-cite. > > > > He noted that citekeys can only start with an underscore or a

  1   2   3   4   5   >