unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Jean Louis <bugs@gnu.support>
Cc: Emacs-Devel List <emacs-devel@gnu.org>
Subject: RE: Feature branches review please (ivy hello)
Date: Fri, 6 Nov 2020 11:27:55 -0800 (PST)	[thread overview]
Message-ID: <11ac533f-298d-4b7b-b72c-5c1b42d3b0a2@default> (raw)
In-Reply-To: <X6Web2tdWMNfIkkG@protected.rcdrun.com>

> > Icicles or library orderless.el provides such
> > behavior.
> 
> https://urldefense.com/v3/__https://www.emacswiki.org/emacs/DrewsElispLibrari
> es__;!!GqivPVa7Brio!PeXT38xLaZ0WLPhzhQoy50PH99rQt9z2shHRkvYnymiDP96UbGsrHqcRD
> 1EpQbPv$
> 
> Incremental search on that page does not give me: orderless.el - where
> is it?

It's not one of my libraries.  I mentioned it because,
like Icicles "progressive completion", it lets you get
matches of multiple patterns without respect to order.

Googling "orderless.el" tells me it's here:

https://github.com/oantolin/orderless



  reply	other threads:[~2020-11-06 19:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-06 16:30 Feature branches review please (ivy hello) Drew Adams
2020-11-06 19:05 ` Jean Louis
2020-11-06 19:27   ` Drew Adams [this message]
2020-11-08  9:52     ` orderless/bookmarks Jean Louis
  -- strict thread matches above, loose matches on Subject: below --
2020-11-05 10:05 Feature branches review please Jean Louis
2020-11-05 16:10 ` Gregory Heytings via Emacs development discussions.
2020-11-05 16:27   ` Manuel Uberti
2020-11-05 17:00     ` Gregory Heytings via Emacs development discussions.
2020-11-05 17:32       ` Jean Louis
2020-11-05 20:39         ` Gregory Heytings via Emacs development discussions.
2020-11-05 21:33           ` Jean Louis
2020-11-05 22:24             ` Gregory Heytings via Emacs development discussions.
2020-11-05 22:48               ` Jean Louis
2020-11-06  9:19                 ` Gregory Heytings via Emacs development discussions.
2020-11-06 10:51                   ` Feature branches review please (ivy hello) Jean Louis
2020-11-06 11:17                     ` Oleh Krehel
2020-11-06 11:42                       ` Jean Louis
2020-11-06 11:49                         ` Basil L. Contovounesios
2020-11-06 12:01                           ` Jean Louis
2020-11-06 21:12                             ` Basil L. Contovounesios
2020-11-06 13:56                         ` Stefan Monnier
2020-11-06 14:10                           ` Eli Zaretskii
2020-11-06 14:55                             ` Stefan Monnier
2020-11-06 15:24                           ` Jean Louis
2020-11-06 12:07                     ` Gregory Heytings via Emacs development discussions.
2020-11-06 14:02                       ` Stefan Monnier
2020-11-06 14:41                         ` Gregory Heytings via Emacs development discussions.
2020-11-06 19:23                       ` Jean Louis
2020-11-06 21:09                         ` Gregory Heytings via Emacs development discussions.

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=11ac533f-298d-4b7b-b72c-5c1b42d3b0a2@default \
    --to=drew.adams@oracle.com \
    --cc=bugs@gnu.support \
    --cc=emacs-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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.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).