From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-users@sunsite.auc.dk
Subject: Re: PATCH: colors (was: Re: ever-expanding ZLS_COLORS and Tags vs. groups, and ZLS_COLORS)
Date: Mon, 19 Jun 2000 18:51:29 +0000 [thread overview]
Message-ID: <1000619185129.ZM28159@candle.brasslantern.com> (raw)
In-Reply-To: <200006190845.KAA19206@beta.informatik.hu-berlin.de>
On Jun 19, 10:45am, Sven Wischnowsky wrote:
} Subject: PATCH: colors (was: Re: ever-expanding ZLS_COLORS and Tags vs. gr
}
} And now everyone can easily have a look at the problem that made me
} withhold this (simple) patch:
}
} zstyle '*:hosts' list-colors '=a*=33'
} zstyle '*' users ich du er alfred
} zstyle '*' hosts alpha beta gamma
}
} Now try `ssh <TAB>'. `alfred' is coloured.
}
} Is this still better than the previous state?
In some respects, yes.
The first style above now means "color yellow those words beginning with
`a' any time hosts are listed among the completions." Previously it meant
"... only when hosts are listed in the completion group named `hosts'."
The issue of course being that what one would rather have is "color yellow
those *hosts* beginning with `a' ...", but completion can't differentiate
what is a host except by what group it is in.
It's much easier now to see (in _setup) what you meant when you discussed
looking up the style by group name rather than by tag name.
Anyway, I think this new situation is easier to document, and makes more
sense than the old way when the tag name is wildcarded.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
prev parent reply other threads:[~2000-06-19 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-19 8:45 Sven Wischnowsky
2000-06-19 18:51 ` Bart Schaefer [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=1000619185129.ZM28159@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-users@sunsite.auc.dk \
/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).