From: Nicolas Goaziou <mail@nicolasgoaziou.fr> To: "András Simonyi" <andras.simonyi@gmail.com> Cc: Bastien <bzg@gnu.org>, tumashu <tumashu@163.com>, emacs-orgmode <emacs-orgmode@gnu.org>, John Kitchin <jkitchin@andrew.cmu.edu> Subject: Re: Should wip-cite branch be merged to master? Date: Sat, 28 Apr 2018 01:34:56 +0200 [thread overview] Message-ID: <87a7tote8v.fsf@nicolasgoaziou.fr> (raw) In-Reply-To: <87in8cl5o4.fsf@gmail.com> (=?utf-8?Q?=22Andr=C3=A1s?= Simonyi"'s message of "Fri, 27 Apr 2018 23:07:23 +0200") Hello, András Simonyi <andras.simonyi@gmail.com> writes: > > [cite:author @Jones2018] > > > Again, maybe it's worth having some shortcuts here for the common cases, > > but I think in general we want to try to avoid proliferation of basic > > citation commands. So for that reason I think we should just stick with > > the 'cite'/'(cite)' distinction as the two basic commands, perhaps with > > a more extensible/compositional syntax in each case for expressing the > > variations on these two basic types of citation. > > Again, I very much agree with the general direction of these proposals, > but doesn't this mean that the citation element should have an attribute > to represent which parts of an 'in text' citation are meant to be in the > main text? (I think currently the only citation-specific attributes in > the wip-cite branch are 'prefix', 'suffix' and 'parenthetical'.) IIRC, in the proposal above was, i.e., [cite:foo: @Jones2018], "foo" would be a well-defined style. IOW, it could cover much more than a simple "author". > I'd like to add that I don't consider the choice of the two citation > commands a crucial one, 'cite' as 'in main text' and '(cite)' as > 'parenthetical' could also be a perfectly usable syntax/semantics, > especially if -- as Richard suggests -- we provide extension points to > cover more complex use cases. The syntax above might be such an extension point. It requires, however, to find a way to associate a style definition to a given key. Thank you to the answers of everyone involved so far. It's nice to see this moving forward. Regards, -- Nicolas Goaziou
prev parent reply other threads:[~2018-04-27 23:35 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-20 23:01 tumashu 2018-04-21 7:26 ` Nicolas Goaziou 2018-04-21 8:43 ` Christian Moe 2018-04-22 18:17 ` András Simonyi 2018-04-23 19:42 ` John Kitchin 2018-04-25 19:19 ` Richard Lawrence 2018-04-26 23:34 ` Bastien 2018-04-27 21:07 ` András Simonyi 2018-04-27 23:34 ` Nicolas Goaziou [this message]
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=87a7tote8v.fsf@nicolasgoaziou.fr \ --to=mail@nicolasgoaziou.fr \ --cc=andras.simonyi@gmail.com \ --cc=bzg@gnu.org \ --cc=emacs-orgmode@gnu.org \ --cc=jkitchin@andrew.cmu.edu \ --cc=tumashu@163.com \ --subject='Re: Should wip-cite branch be merged to master?' \ /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).