all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ergus <spacibba@aol.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: Drew Adams <drew.adams@oracle.com>, emacs-devel@gnu.org
Subject: Re: Why fido, icycles, ido, icomplete
Date: Thu, 7 Nov 2019 16:00:54 +0100	[thread overview]
Message-ID: <20191107150054.oykoqmea4vxsx25v@Ergus> (raw)
In-Reply-To: <87pni4q8b3.fsf@gmail.com>

On Thu, Nov 07, 2019 at 10:39:44AM +0000, Jo?o T?vora wrote:
>Ergus <spacibba@aol.com> writes:
>
>>>movie theater where there are only classics playing.  Lots of grainy
>>>footage but all movies are superb.
>> Yes, but nobody feels impressed by the special effects in the first Star
>> Wars today, in spite of they were amazing in their moment and required
>> much more effort than newer movies.
>
>I'm glad I made the analogy, then.  I am more interested in cinema than
>special effects.  Metaphoricaly, of course.  (but also literally).
>

>>>And I found icomplete.el, which is already in Emacs.
>> ivy is also based on icomplete actually.
>
>Oh.  What do you mean "based".  Does it share some of the implementation
>(i.e. does it 'require' icomplete as a library).  Or is it more of "a
>derived work"?
>
It is a derived work. Look: https://github.com/abo-abo/swiper/issues/2321

>>>You are miscommunicating: the "gap" is whatever doesn't quite work in
>>>icomplete-mode to make it work just like ido-mode.  It's the behaviour
>>>of RET, C-k, C-d and some other things.
>> Could you add at least the cycle with arrows as in ido?
>
>Of course, and so can you.  Have you got a FSF copyright assignment?
>
Yes, I have one... but I prefer to deal with the C side of emacs... ;-).

>Jo?o
>
>
Ergus



  reply	other threads:[~2019-11-07 15:00 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191106212018.cnddqzlo5rpdhi6s.ref@Ergus>
2019-11-06 21:20 ` Why fido, icycles, ido, icomplete Ergus
2019-11-06 21:30   ` Daniele Nicolodi
2019-11-06 22:27     ` Ergus
2019-11-06 22:03   ` João Távora
2019-11-06 22:39     ` Óscar Fuentes
2019-11-06 22:57       ` João Távora
2019-11-06 23:07         ` Óscar Fuentes
2019-11-07  0:36           ` João Távora
2019-11-07  1:07             ` Óscar Fuentes
2019-11-07  1:21               ` Ergus
2019-11-07  1:51                 ` Óscar Fuentes
2019-11-07 10:09               ` João Távora
2019-11-07 18:50                 ` Óscar Fuentes
2019-11-06 23:21     ` Ergus
2019-11-06 23:59       ` Óscar Fuentes
2019-11-07  0:47         ` Ergus
2019-11-07  2:20           ` Óscar Fuentes
2019-11-07  4:59             ` Ergus
2019-11-07 18:26               ` Óscar Fuentes
2019-11-07 14:09             ` Stefan Monnier
2019-11-07 20:35               ` Óscar Fuentes
2019-11-07 21:11                 ` Stefan Monnier
2019-11-07 22:18                   ` Óscar Fuentes
2019-11-07 22:30                     ` Stefan Monnier
2019-11-07 22:34                     ` João Távora
2019-11-07  0:27       ` João Távora
2019-11-07  1:09         ` Ergus
2019-11-07 10:39           ` João Távora
2019-11-07 15:00             ` Ergus [this message]
2019-11-08 17:54     ` Filipp Gunbin
2019-11-08 18:10       ` Óscar Fuentes
2019-11-08 18:45       ` Nicolas Semrau
2019-11-08 19:12       ` Eli Zaretskii
2019-11-08 21:31         ` Juanma Barranquero
2019-11-08 22:54           ` João Távora
2019-11-08 23:11             ` Ergus

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=20191107150054.oykoqmea4vxsx25v@Ergus \
    --to=spacibba@aol.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    /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/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.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.