From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: collist v2.0
Date: Tue, 22 Jun 1999 17:06:54 +0000 [thread overview]
Message-ID: <990622170654.ZM30321@candle.brasslantern.com> (raw)
In-Reply-To: <199906220825.KAA23802@beta.informatik.hu-berlin.de>
In-Reply-To: <9906220851.AA23188@ibmth.df.unipi.it>
On Jun 22, 10:25am, Sven Wischnowsky wrote:
} Subject: PATCH: collist v2.0
}
} - Keys used:
} - accept-line and send-break will leave selection. There is visual
} feedback because then there is no highlighted match any more.
This is probably what was confusing me -- I tried accept-line but the
hightlight was still in the listing so I didn't realize I'd escaped.
} [...] Could someone who actually uses coulured lists
} please check if the default values are correct? (They look very bad.)
I agree that they're pretty icky. Here's what I get (no LS_COLORS set,
ZLS_COLORS set but empty):
ls --color Zsh
---------- ----------
blue green directories
green magenta executables
cyan cyan symlinks
magenta goldenrod? sockets
yellow reverse-blue devices
I get this even if I move /etc/DIR_COLORS out of the way.
} - If you read the manual or the collist.c file you'll notice that I've
} changed `collist' to `complist'
I changed collistmatches() to complistmatches() as well.
(Aren't you glad that I didn't let you use the name "complist" before?)
} > Finally, I wanted to mention that I got it into a state where the highlight
} > was not visible -- I could only tell where I was because the word on the
} > command line kept changing as I pressed the arrow keys. Eventually I think
} > I crossed back over the word that had been offered as the initial choice
} > (which was in the middle of the list somewhere -- I think it restarted an
} > old menu completion after I thought I'd broken out) and then the hightlight
} > came back.
}
} Maybe part of this is: when you start a normal menu completion and then
} invoke menu-select and then leave it again, you are in menu completion
} again. That's intentional. Otherwise I haven't seen such a behavior,
} could you try with the patch?
No, I never started a normal menu-completion. As best I recall, I started
a menu-select, left it somehow without selecting anything (possibly by ^G)
and then immediately attempted the same menu-select again.
I just rebuilt with all the latest patches, and now I can't get menu-select
to start. I did
bindkey \\t menu-select
and confirmed with bindkey -L that tab was indeed re-bound, but when I try
zsh% ls <TAB>
it simply starts normal menu completion. Oh, I see -- menu-select depends
on ZLS_COLORS being set! That seems odd.
Anyway, at the moment I can't manage to repeat the highlighting problem.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-06-22 17:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 8:25 Sven Wischnowsky
1999-06-22 8:51 ` Peter Stephenson
1999-06-22 17:06 ` Bart Schaefer [this message]
1999-06-22 9:04 ` Peter Stephenson
1999-06-22 11:52 ` Andrej Borsenkow
1999-06-22 8:49 Sven Wischnowsky
1999-06-22 9:56 Sven Wischnowsky
1999-06-22 10:35 Sven Wischnowsky
1999-06-22 12:36 Sven Wischnowsky
1999-06-23 8:43 Sven Wischnowsky
1999-06-23 8:59 ` Andrej Borsenkow
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=990622170654.ZM30321@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@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).