unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Edmondson <dme@dme.org>
To: Lele Gaifax <lele@metapensiero.it>, notmuch@notmuchmail.org
Subject: Re: Address completion in Emacs
Date: Fri, 12 Dec 2014 13:08:42 +0000	[thread overview]
Message-ID: <m21to5hv6t.fsf@heart-of-gold.hh.sledj.net> (raw)
In-Reply-To: <87vblh829w.fsf@nautilus.nautilus>

On Fri, Dec 12 2014, Lele Gaifax wrote:
> David Edmondson <dme@dme.org> writes:
>
>> On Fri, Dec 12 2014, Lele Gaifax wrote:
>>> Wouldn't it be more "correct" to pass the unchanged `options' list and
>>> the "real" `orig' text as `initial-input' to the customizable function
>>> instead?
>>
>> Would I then have to press TAB twice to get the first result?
>
> No, why? The customizable `notmuch-address-selection-function' would be
> free to pass (car options) as the initial-input of `completing-read', if
> needed. When using `ido-completing-read', the first option is
> pre-selected, so a RET confirms that.

Understood.

>>> I understand that it may be undesiderable to break existing
>>> configurations by rectifying the arguments in that way, and in such case
>>> could we change the `initial-input' argument name to better reflect the
>>> fact that it actually contains one possible candidate instead?
>>
>> From the perspective of `notmuch-address-selection-function', it _is_
>> the `initial-input', as that is what is presented to the user.
>
> IMHO no, it's not: what it receives as `initial-input' is not what the
> user actually wrote, but rather just the (somewhat arbitrary) first
> candidate address found by `notmuch-address-command'.

I think that we're at cross
purposes. `notmuch-address-selection-function' will use the
`initial-input' as the initial input of the completion, so that's what
it chooses to call the argument. It can't be blamed if whatever is
passed to it is not something that you would consider the initial input.

> thanks&bye, lele.
> -- 
> nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri
> real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia.
> lele@metapensiero.it  |                 -- Fortunato Depero, 1929.
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch

  reply	other threads:[~2014-12-12 13:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-12  8:22 Address completion in Emacs Lele Gaifax
2014-12-12 12:14 ` David Edmondson
2014-12-12 12:45   ` Lele Gaifax
2014-12-12 13:08     ` David Edmondson [this message]
2014-12-14 17:27 ` Tomi Ollila
  -- strict thread matches above, loose matches on Subject: below --
2023-12-08 13:26 Address Completion " David Wen Riccardi-Zhu
2023-12-08 16:40 ` Sandra Snan
2023-12-09  2:05   ` David Wen Riccardi-Zhu
2023-12-09  8:26     ` Keith Amidon

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://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m21to5hv6t.fsf@heart-of-gold.hh.sledj.net \
    --to=dme@dme.org \
    --cc=lele@metapensiero.it \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).