emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Bruce D'Arcus" <bdarcus@gmail.com>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: [wip-cite-new] Quick note about citation insertion
Date: Sat, 03 Jul 2021 11:20:43 +0200	[thread overview]
Message-ID: <87fswvsqhg.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAF-FPGNTXkyphCy=bd-89EGbWV8=5_a6BdqgE=EQwQH8V0kPow@mail.gmail.com> (Bruce D'Arcus's message of "Sat, 3 Jul 2021 04:45:46 -0400")

Hello,

"Bruce D'Arcus" <bdarcus@gmail.com> writes:

> On Fri, Jul 2, 2021 at 4:05 PM Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:

>> That's expected. "nil" is the name of the processor's fall-back style,
>> ignoring any inheritance. It is different from the empty style (""),
>> which takes into account inheritance.
>
> Two things:
>
> First, after adding a style, I can't see how to subsequently remove it
> using this interface, to just have "[cite:@key]". Is that possible?

Of course. Just select the empty string instead of an entry. It is done
with C-j on Selectrum and `completing-read-default'. I assume this is
the same on other completion frameworks.

> In my formatting function for OC, which is simpler than your's in some
> ways, I have a named "default" style, with that as the
> ido-completing-read "initial-value", which is then removed if
> selected.
>
> In practice, what that means is if the user is prompted for the style
> but hits return, they select "default", and hence the result is
> "[cite:@key]".

Your "default" is equivalent to my empty string. But one day, an export
processor may use "default" as a name for a different style. Who knows?
Moreover, "default" may be ambiguous: does it mean user's or processor's
default style?

More importantly, we have to deal with the empty string anyway; this is
a valid return value from `completing-read'.

> Second, the "nil" vs "empty" distinction was obviously not immediately
> intuitive to me. I don't have a better name for "nil" ATM though, so
> maybe it will be fine. Hopefully people won't have the need to use it
> much.

Both are necessary. At some point, this will have to be documented.

Regards,
-- 
Nicolas Goaziou


  reply	other threads:[~2021-07-03  9:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02 16:10 [wip-cite-new] Quick note about citation insertion Nicolas Goaziou
2021-07-02 19:21 ` Bruce D'Arcus
2021-07-02 20:05   ` Nicolas Goaziou
2021-07-03  8:45     ` Bruce D'Arcus
2021-07-03  9:20       ` Nicolas Goaziou [this message]
2021-07-03  9:56         ` Bruce D'Arcus
2021-07-02 19:47 ` Bruce D'Arcus
2021-07-02 20:14   ` Nicolas Goaziou
2021-07-02 20:58     ` Bruce D'Arcus
2021-07-02 21:05       ` John Kitchin
2021-07-02 21:21         ` Nicolas Goaziou
2021-07-03  0:21           ` Bruce D'Arcus
2021-07-02 21:48       ` Nicolas Goaziou
2021-07-02 21:57         ` Bruce D'Arcus
2021-07-02 22:33           ` Nicolas Goaziou
2021-07-02 23:59             ` Bruce D'Arcus
2021-07-03  7:28             ` Eric S Fraga
2021-07-03  7:58               ` Nicolas Goaziou
2021-07-03 14:57                 ` Eric S Fraga
2021-07-03 15:09                   ` Bruce D'Arcus
2021-07-05 13:29                     ` Eric S Fraga
2021-07-06 12:11                 ` Bruce D'Arcus
2021-07-07 22:59                   ` Nicolas Goaziou
2021-07-08  0:38                     ` Bruce D'Arcus
2021-07-08 11:46                       ` Nicolas Goaziou
2021-07-08 11:52                         ` Bruce D'Arcus
2021-07-08 13:19                         ` Bruce D'Arcus
2021-07-08 11:41                     ` Bruce D'Arcus
2021-07-08 11:44                       ` Nicolas Goaziou
2021-09-26 10:40                         ` Bastien
2021-07-08 12:48                       ` Eric S Fraga
2021-07-08 13:04                         ` Bruce D'Arcus
2021-07-08 15:34                           ` 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=87fswvsqhg.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=bdarcus@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public 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).