zsh-users
 help / color / mirror / code / Atom feed
From: "Stephen Riehm" <sr@pc-plus.de>
To: zsh-users@math.gatech.edu
Subject: Re: zsh - new user with questions
Date: Wed, 19 Aug 1998 14:34:20 +0200	[thread overview]
Message-ID: <C1256665.0042531C.00@bavaria3.pc-plus.de> (raw)




Hi Again,



firstly, thanks to all those who replied, some of the tips were exactly
what I was looking for.



The expand-or-complete-prefix tip however didn't work, as then the -list
function only works when you've

already typed something. ie:



     cd /usr/<tab>



doesn't complete, and doesn't produce a list - ( I don't like using the
menu stuff, by the time I've hit tab 50 times

I could have easily typed any name I might be searching for), first when
you type another character does it start

showing lists again, ie:



     cd /usr/l<tab>

     lib/ local/



The way I work at the moment, I used the expand-or-complete-or-list
functionality instead of

having to use 'ls' all the time - which works great with case-insensitive
completion and list-when-ambiguous.

(ie: I often provide support by phone, they tell me to cd to
/home/user/Dev/ProductTest-1.2 - spoken as

slash home user dev product test one point two. I'm sure you can see where
case insensitivity and list-when-ambiguous

comes in really handy here. in tcsh I'ld probably type
/home/user/dev<tab>prod.2<tab> and I'ld be there, or if there

was an ambiguity, I'ld imediately see what choices I had.)

I'm not really complaining, I just find these features extremely helpful,
and I miss them a lot :-)



If there's a wishlist or a todo list for zsh, I would really like to add
this feature to it! (I personally think the Amiga

dudes got it right back in '86 when they made the file names were only
stores case sensitive - but all operations

at OS level were case insensitive - thus it was impossible to have ReadMe
and README in the same directory.

I personally think this reduces possible confusion, (does make read
Makefile or makefile first?) and makes

case insensitive completion trivial. - just my 2cents)



Thanks again,



Steve



             reply	other threads:[~1998-08-19 12:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-08-19 12:34 Stephen Riehm [this message]
1998-08-19 13:53 ` Goran Larsson
1998-08-19 16:03 ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
1998-08-20 11:27 Stephen Riehm
1998-08-19 15:09 Stephen Riehm
1998-08-19 17:35 ` Goran Larsson
1998-08-19 19:18   ` Bart Schaefer
1998-08-19 19:58     ` Roland Jesse
1998-08-20  9:47       ` Andrej Borsenkow
1998-08-18 15:33 Stephen Riehm
1998-08-18 16:17 ` Matthew Lovell
1998-08-18 16:28 ` Peter Stephenson
1998-08-18 22:46   ` David Hedbor
1998-08-19  1:21     ` Bart Schaefer
1998-08-18 16:43 ` Zefram

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=C1256665.0042531C.00@bavaria3.pc-plus.de \
    --to=sr@pc-plus.de \
    --cc=zsh-users@math.gatech.edu \
    /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).