all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] emacs: Use "r" key for 'cran' action in 'import' popup.
Date: Wed, 02 Sep 2015 22:22:04 +0200	[thread overview]
Message-ID: <87mvx4607n.fsf@gnu.org> (raw)
In-Reply-To: <87613szpdc.fsf@gmail.com> (Alex Kost's message of "Wed, 02 Sep 2015 20:45:51 +0300")

Alex Kost <alezost@gmail.com> skribis:

> Ludovic Courtès (2015-09-02 16:10 +0300) wrote:
>
>> Alex Kost <alezost@gmail.com> skribis:
>>
>>> From 1cc6871abf3d53ad5702fde5570df8a61a945010 Mon Sep 17 00:00:00 2001
>>> From: Alex Kost <alezost@gmail.com>
>>> Date: Tue, 1 Sep 2015 13:10:41 +0300
>>> Subject: [PATCH] emacs: Use "r" key for 'cran' action in 'import' popup.
>>>
>>> * emacs/guix-command.el (guix-command-improve-import-argument): New
>>>   variable and function.
>>>   (guix-command-argument-improvers): Add it.
>>
>> Definitely.
>>
>> Should there be some sort of automatic disambiguation mechanism?
>
> Automatic?  I think it should be defined by a human what key to assign.
> How can it be automatically decided what key should be used for "cpan"
> and what for "cran"?  Currently the key is just defined by the first
> letter and I think it is the maximal automatization that should be done.
> If it's not enough, than we should solve disambiguation manually, don't
> you agree?

Yes, you’re right.  Doing things automatically would have the advantage
of not missing collisions, but doing it sensibly may prove to be hard,
as you note.

Ludo’.

      reply	other threads:[~2015-09-02 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 10:18 [PATCH] emacs: Use "r" key for 'cran' action in 'import' popup Alex Kost
2015-09-02 13:10 ` Ludovic Courtès
2015-09-02 17:45   ` Alex Kost
2015-09-02 20:22     ` Ludovic Courtès [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

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

  git send-email \
    --in-reply-to=87mvx4607n.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=guix-devel@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.