From: "Bruce D'Arcus" <email@example.com> To: Org Mode List <firstname.lastname@example.org> Subject: Re: [wip-cite-new] New natbib processor Date: Wed, 5 May 2021 11:20:31 -0400 [thread overview] Message-ID: <CAF-FPGN2OVgFwZG5T1VmjyL6Ev+D-t6d94yAKsHCsh2email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Wed, May 5, 2021 at 10:53 AM Nicolas Goaziou <email@example.com> wrote: > Another thread! Yay! We should be close to the finish line! > I just added a new `natbib' processor in "wip-cite-new" branch, in the > file "oc-natbib.el" Awesome! > However, I'm not convinced by them [sub-styles]. > > On the bright side, sub-styles can be put in any order, so we're > avoiding combinatorial explosion of commands. > > However, they do not play well with shortcuts. For example, if shortcut > for "caps" is "C" and "full" is "F", > > [cite/text/caps/full:...] is equivalent to [cite/t/C/f:...] > > which is not great. I'm just going to focus on these points. 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 to include them because otherwise you end up with an insanely long list of styles, which won't map well onto different kinds of output formats. E.g. biblatex users will want like 20 commands available, which won't all work with other formats. Also consider that for processors, they're going to have to map those internally to something like styles+sub-styles anyway. So I think sub-styles are good for users and developers alike. Syntax? I see your point on short-cuts; maybe your previous idea would work better; a plus-separated list? [cite:t/a+f+c] ... and the full names: [cite:text/alt+full+caps] Even if not perfect, I think it's a small price to pay for the benefits. Bruce
next prev parent reply other threads:[~2021-05-05 15:22 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-05 14:53 Nicolas Goaziou 2021-05-05 15:20 ` Bruce D'Arcus [this message] 2021-05-05 15:32 ` Bastien 2021-05-06 12:29 ` Nicolas Goaziou 2021-05-06 12:56 ` Bruce D'Arcus 2021-05-05 18:08 ` Bruce D'Arcus 2021-05-05 21:25 ` Bruce D'Arcus 2021-05-05 21:40 ` Bruce D'Arcus 2021-05-05 22:32 ` Bruce D'Arcus 2021-05-06 7:36 ` Denis Maier 2021-05-06 10:06 ` Bruce D'Arcus 2021-05-06 11:22 ` Bruce D'Arcus 2021-05-06 12:05 ` Nicolas Goaziou 2021-05-06 13:09 ` Bruce D'Arcus 2021-05-06 14:12 ` Nicolas Goaziou 2021-05-06 14:23 ` Bruce D'Arcus 2021-05-06 16:20 ` Nicolas Goaziou 2021-05-06 16:59 ` Bruce D'Arcus 2021-05-06 8:47 ` Bruce D'Arcus 2021-05-06 12:11 ` Nicolas Goaziou 2021-05-06 12:37 ` Bruce D'Arcus 2021-05-07 11:37 ` Bruce D'Arcus 2021-05-08 13:51 ` Bruce D'Arcus 2021-05-09 8:57 ` Nicolas Goaziou 2021-05-09 13:49 ` Bruce D'Arcus 2021-05-09 20:25 ` Nicolas Goaziou 2021-05-09 22:01 ` Bruce D'Arcus 2021-05-10 17:07 ` Bruce D'Arcus 2021-05-10 20:22 ` Nicolas Goaziou 2021-05-10 20:52 ` Bruce D'Arcus 2021-05-15 21:29 ` Nicolas Goaziou 2021-05-15 21:54 ` Bruce D'Arcus 2021-05-16 9:47 ` Nicolas Goaziou 2021-05-11 12:13 ` Eric S Fraga
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: https://www.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAF-FPGN2OVgFwZG5T1VmjyL6Ev+D-t6d94yAKsHCsh2firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [wip-cite-new] New natbib processor' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.git This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).