zsh-users
 help / color / mirror / code / Atom feed
From: Sweth Chandramouli <sweth@astaroth.nit.gwu.edu>
To: zsh-users@math.gatech.edu
Subject: Re: Re: zsh - new user with questions
Date: Wed, 19 Aug 1998 16:33:31 -0400	[thread overview]
Message-ID: <19980819163331.A5738@astaroth.nit.gwu.edu> (raw)
In-Reply-To: <19980819215829.A13376@cs.uni-magdeburg.de>

On Wed, Aug 19, 1998 at 09:58:29PM +0200, Roland Jesse wrote:
> Bart Schaefer wrote:
> 
> > The actual _access_ to the file still has to use its "real" name.
> 
> Now it's getting confusing. If the completion tells me a different file
> name than the one acutally stored in the file system, I can easily imagine
> cases in which I am not sure what the command, the completion is used for,
> is going to do.
	
	but no one ever suggested that completion tell you a different name.  
what people have been discussing is completion _recognizing_ a different name, 
and completing it to the "correct" name.  basically, zsh would no longer look 
for exact matches when searching for possible completions, but would instead use 
some set of algorithms for the search.  in theory, i don't see why this would 
cause any problems, as bart shows in his example:
	
> zsh% ls STRASSE<TAB>
> 
> then zsh would complete case-insensitively and you'd see
> 
> zsh% ls Straße

	the completion tells you _exactly_ the file name that is stored in the 
system, despite your asking for the wrong one.  so long as the algorithms used 
were based on some standard translation (and so long as they were used just for 
completion--as someone else pointed out, using it for general globbing could be 
problematic), then the absolute worst result that could happen is that 
completion would, as it does now, simply not find the file for which you are 
searching--if i were using some different lang set, where ß was not considered 
the lowercase version of "SS", then the session would look like this:

zsh% ls STRASSE<TAB>
<beep>
zsh% ls STRASSE

	at which point i could slap my head, realize i was using the 
western-bulgarian charset, and try to figure out what the real spelling of the 
file was myself.
	
	(actually, that would be what would happen for iso_8859_1, in addition 
to western-bulgarian, which sees the uppercase version of ß as À (at least 
according to 

zsh% echo 'ß' | tr "[:lower:]" "[:upper:]"

	.  so, is there some easy way to view the character tables (and maybe 
even the ascii sequences that map to them) for a given language charset, from 
the command line?  how about to view the upper<->lower translation tables, or 
does it simply increment/decrement the ascii value by a certain amount and use 
whatever is returned by the new value?
	
	-- sweth.
	
-- 
Sweth Chandramouli
IS Coordinator, The George Washington University
<sweth@gwu.edu> / (202) 994 - 8521 (V) / (202) 994 - 0458 (F)
<a href="http://astaroth.nit.gwu.edu/~sweth/disc.html">*</a>


  reply	other threads:[~1998-08-19 20:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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-19 20:33       ` Sweth Chandramouli [this message]
1998-08-19 21:19         ` Roland Jesse
1998-08-20  9:47       ` Andrej Borsenkow
1998-08-19 17:53 ` Case insensitive completion (Re: zsh - new user with questions) Bart Schaefer

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=19980819163331.A5738@astaroth.nit.gwu.edu \
    --to=sweth@astaroth.nit.gwu.edu \
    --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).