[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: zsh globbing



Hi,

* Johann Spies <jhspies@adept.co.za> [02-10-08 22:01]:
>In bash I can do this:
>
>js-21:57:41-~$dpkg -l zsh*
>Desired=Unknown/Install/Remove/Purge/Hold
>|
>Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
>|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
>uppercase=bad)
>||/ Name           Version        Description
>+++-==============-==============-============================================
>ii  zsh            4.0.4-33       A shell with lots of features.
>[...............]
>
>In zsh:
>
>zsh % dpkg -l zsh*
>zsh: no matches found: zsh*
>
>Why?

Good question. Assuming no files beginning with zsh are in pwd, the
bash shouldn't find anything. It's probably a matter of policy whether
you are warned or not. I like the zsh way, but considering the
Gazillion options of the zsh, I wouldn't be surprised if you could
change it.

If you want to to have useful completion of dpkg parameters, you
should look around for zsh's smart completion. I use a set from SuSE
and it really helps me a lot.


>While I can do 
>
>zsh % ls .z*
>.zcompdump  .zhistory  .zshrc  .zshrc~

Yup, you have these files, so they are expanded. Try this:
    ls .z*<tab>
and you will see what zsh thinks about the files you will get.



Reply to: