zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: show-ambiguity style
Date: Sun, 12 Apr 2015 11:58:30 -0700	[thread overview]
Message-ID: <150412115830.ZM21859@torch.brasslantern.com> (raw)
In-Reply-To: <552A67C4.1080903@thregr.org>

On Apr 12,  2:40pm, Yuri D'Elia wrote:
} Subject: Re: show-ambiguity style
}
} On 04/11/2015 10:02 PM, Bart Schaefer wrote:
} > Completion gets screwed up if show-ambiguity is not an ANSI term color
} 
} I mentioned it in the page (and now that I look again, you actually
} responded to my first implementation ;)).

I'm not sure what this means ... the 20141010-zsh_show_ambiguity page has
not changed since I first looked at it.  Oh, you mean that I responded
on the users/18440 thread.  In any case there's nothing in either your
page or the docs to indicate that bad syntax in list-colors will garble
the completion display.

} The way the match is constructed (a nested glob expression - a great
} idea of Oliver Kiddle) is the neatest and weakest part IMHO. It makes
} the highlight work even with complete_in_word, but surely is not as
} efficient as post-processing the result *after* list coloring.

I don't know that it makes any difference to efficiency, but to have
the ambiguity disply overlaid on top of the other coloring would require
changes to the complist internals.

The main thing this is telling me is that we need more examples of how
to set list-colors.


  reply	other threads:[~2015-04-12 18:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-10 21:36 Yuri D'Elia
2015-04-11  2:21 ` lilydjwg
2015-04-11 16:33 ` Vadim Zeitlin
2015-04-11 20:02   ` Bart Schaefer
2015-04-12 12:40     ` Yuri D'Elia
2015-04-12 18:58       ` Bart Schaefer [this message]
2015-04-12 21:03         ` Yuri D'Elia
2015-04-13 11:00           ` Jesper Nygårds
2015-04-13 15:25             ` Bart Schaefer
2015-04-13 19:20               ` Jesper Nygårds
2015-04-12 12:40     ` Yuri D'Elia
2015-04-13 20:57     ` Daniel Shahaf
2015-04-13 20:21 ` zzapper
2015-04-15 19:56   ` Yuri D'Elia
2015-04-20 21:51     ` zzapper

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=150412115830.ZM21859@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).