Re: Ex-bash script for optimisation

Re: Ex-bash script for optimisation

[Meino Christian Cramer]

Hi,

 I checked the zshall manpage, but I fear to have overlocked the
 specific line which explains, for what I am using for.

 I want to limit the expand function (that one called when pressing
 TAB after entering for example "cd") to file of the current working
 directory or in other words I want to switch off the global search for
 expansion possibilities...

 How can I achieve this?

 Thank you very much for any help and hints in advance ! :)
 Keep zsh'ing! ;)
 Meino

Re: Ex-bash script for optimisation

[Bart Schaefer]

On Mar 10,  7:42pm, Meino Christian Cramer wrote:
} Subject: Re: Ex-bash script for optimisation

Please start a new message with a new subject if you're asking a new
question, rather than replying to an unrelated discussion re-using a
misleading subject.  Thank you.

}  I want to limit the expand function (that one called when pressing
}  TAB after entering for example "cd")

It's important to know whether you really mean "expansion" or whether
(as I suspect) you're asking about "completion".

"Expansion" means you have something like a glob pattern, for example
a*e, and you want the shell to replace it with file names that match
the pattern, for example ankle apple argue.  In general, expansion is
not context-sensitive.

"Completion" means you've typed part of a word -- usually a prefix --
and you want the shell to supply the rest of the word in a way that
fits the context where the word appears.  For example, directory names
in the arguments of cd.

}  to file of the current working directory or in other words I want to
}  switch off the global search for expansion possibilities...

This question is a bit mystifying because there normally is no "global
search."  One possibility is that you need to "unset cdpath", but it
would help if you explained more about (1) whether you use "compinit"
to set up completion or are using the built-in defaults, and (2) what
happens when you press TAB that makes you think a "global" search is
being done.

TAB-expansion problems

[Meino Christian Cramer]

From: Bart Schaefer <schaefer@brasslantern.com>
Subject: Re: Ex-bash script for optimisation
Date: Fri, 11 Mar 2005 05:14:17 +0000

Hi,


> On Mar 10,  7:42pm, Meino Christian Cramer wrote:
> } Subject: Re: Ex-bash script for optimisation
> 
> Please start a new message with a new subject if you're asking a new
> question, rather than replying to an unrelated discussion re-using a
> misleading subject.  Thank you.

  Oh, damn! Sorry...my fault...
 
> }  I want to limit the expand function (that one called when pressing
> }  TAB after entering for example "cd")
> 
> It's important to know whether you really mean "expansion" or whether
> (as I suspect) you're asking about "completion".

  As a zsh-newbie I better describe what happens and what I want to
  switch off.

  Suppose I am at my $HOME/tmp/. directory. Furthermore there is only
  ONE additional directory called "TheLonelyOne" there. And I want to
  to change into that directory. As a lazy person now I would type on
  the commandline 

	  cd <TAB>

  and want to get 

      cd TheLonelyOne

  then instead all worldwide reachable directories as a suggestion.

  From my current point of knowledge I didn't neither know the correct
  naming for that behaviour (otherwise I may have already found the
  solution in the docs...) nor whether there are similiar conditions
  with possible other commands, which lead to such "I suggest you now
  everything worldwide possible"-behaviour of zsh (this by far no
  complainment against zsh or any critism !!! :) 

  Or with lesser words: If I would have a name of my problem I may not
  have that problem anymore... ;)

  My compinit-related stuff (as far as I am able to identfy it...) is:
  (from $HOME/.zshrc)


    # Search path for the cd command
    cdpath=(.. ~ ~/src ~/zsh)
    
    setopt   notify globdots nocorrect pushdtohome cdablevars autolist
    setopt   autocd recexact longlistjobs
    setopt   autoresume histignoredups pushdsilent noclobber
    setopt   autopushd pushdminus extendedglob rcquotes mailwarning
    unsetopt bgnice autoparamslash
    setopt   nobeep multios monitor
    
    ### completion stuff
    zstyle ':completion:*' verbose yes
    zstyle ':completion:*:descriptions' format '%B%d%b'
    zstyle ':completion:*:messages' format '%d'
    zstyle ':completion:*:warnings' format 'No matches for: %d'
    zstyle ':completion:*' group-name ''
    
    # ----------------------------------------------------------------------
    xhost local:root 2>&1 > /dev/null
    # The following lines were added by compinstall
    
    zstyle :compinstall filename '/home/mccramer/.zshrc'
    
    autoload -Uz compinit
    compinit
    # End of lines added by compinstall
 

  
  
  


> "Expansion" means you have something like a glob pattern, for example
> a*e, and you want the shell to replace it with file names that match
> the pattern, for example ankle apple argue.  In general, expansion is
> not context-sensitive.
> 
> "Completion" means you've typed part of a word -- usually a prefix --
> and you want the shell to supply the rest of the word in a way that
> fits the context where the word appears.  For example, directory names
> in the arguments of cd.
> 
> }  to file of the current working directory or in other words I want to
> }  switch off the global search for expansion possibilities...
> 
> This question is a bit mystifying because there normally is no "global
> search."  One possibility is that you need to "unset cdpath", but it
> would help if you explained more about (1) whether you use "compinit"
> to set up completion or are using the built-in defaults, and (2) what
> happens when you press TAB that makes you think a "global" search is
> being done.
> 

Re: TAB-expansion problems

[Tim Kruse]

* On 11.03.2005 Meino Christian Cramer wrote:

>   Suppose I am at my $HOME/tmp/. directory. Furthermore there is only
>   ONE additional directory called "TheLonelyOne" there. And I want to
>   to change into that directory. As a lazy person now I would type on
>   the commandline
>
> 	  cd <TAB>
>
>   and want to get
>
>       cd TheLonelyOne
>
>   then instead all worldwide reachable directories as a suggestion.

 Oh, I think you don't get 'all worldwide reachable' dirs. It
depends on the cdpath entry in your .zshrc:

>     # Search path for the cd command
>     cdpath=(.. ~ ~/src ~/zsh)

 The completion system looks in all here mentioned path's for
dirs to complete.

 So long,
tkr

PS: I'm new to this group and posting through gmane.org. So if
    the Reply-To header is wrong I'll don't set it in further
    postings.

PPS: English is not my native language - so apologize any
     mistakes :-)

-- 
 Leela: I'm sorry, but if it's fun in any way it's not environmentalism. 
 Paul: Oh, really? How about blowing up dams?

Re: TAB-expansion problems

[Bart Schaefer]

On Mar 11,  7:37pm, Meino Christian Cramer wrote:
} 
}   Suppose I am at my $HOME/tmp/. directory. Furthermore there is only
}   ONE additional directory called "TheLonelyOne" there. And I want to
}   to change into that directory. As a lazy person now I would type on
}   the commandline 
} 
} 	  cd <TAB>
} 
}   and want to get 
} 
}       cd TheLonelyOne
} 
}   then instead all worldwide reachable directories as a suggestion.

As Tim Kruse has said, the likelyhood here is that zsh is suggesting
subdirectories of the directories listed in your cdpath.  If you add
the following style you'll get better information:

zstyle ':completion:*' format '%SCompleting %U%d%u%s'

After you've tried that, so you've seen what's going on, you can then
add this style:

zstyle :completion::complete:cd:: tag-order \
	local-directories path-directories

The tag-order style controls which sets of matches are displayed.  In
the example above, local-directories are preferred, and only when no
local directories are found are path-directories (those found along
your cdpath) shown.  The default is to display all sets of matches at
the same time.

}   From my current point of knowledge I didn't neither know the correct
}   naming for that behaviour

It's "completion".

Re: TAB-expansion problems

[Meino Christian Cramer]

From: Bart Schaefer <schaefer@brasslantern.com>
Subject: Re: TAB-expansion problems
Date: Sun, 13 Mar 2005 04:50:36 +0000

Hi Bart, hi list members!

 :)

 I see, I have to learn A LOT more about zsh!

 Ok, I "killed" cdpath and now my <TAB> does not report "everything
 ever seen" anymore.

 I included the first zstyle in my .$HOME/zshrc and got after entering
 
		cd <TAB>

 the additonal information, saying:

	    Completing local directory

 which is exactly what I want to have (currently, for the first... ;)

 An addtional I have:

 Suppose your are here:

		 $HOME/ThisDir/AnotherDir

 and in ./AnotherDir there is another dir called "WhereIWantToBe"

 Now I enter

	 cd <TAB>

 Does zsh think that there is no match since I didn't enter

     cd Whe<TAB>

 thus preferring to show me possibilities for completions from the
 path-directories OR does zsh "see" the one and only directoy
 "WhereIWantToBe" and gives me

	 cd WhereIWantToBe

 right after hitting <TAB>?

 Thanks a lot for all the friendly help !

 Keep hacking!
 Meino

> On Mar 11,  7:37pm, Meino Christian Cramer wrote:
> } 
> }   Suppose I am at my $HOME/tmp/. directory. Furthermore there is only
> }   ONE additional directory called "TheLonelyOne" there. And I want to
> }   to change into that directory. As a lazy person now I would type on
> }   the commandline 
> } 
> } 	  cd <TAB>
> } 
> }   and want to get 
> } 
> }       cd TheLonelyOne
> } 
> }   then instead all worldwide reachable directories as a suggestion.
> 
> As Tim Kruse has said, the likelyhood here is that zsh is suggesting
> subdirectories of the directories listed in your cdpath.  If you add
> the following style you'll get better information:
> 
> zstyle ':completion:*' format '%SCompleting %U%d%u%s'
> 
> After you've tried that, so you've seen what's going on, you can then
> add this style:
> 
> zstyle :completion::complete:cd:: tag-order \
> 	local-directories path-directories
> 
> The tag-order style controls which sets of matches are displayed.  In
> the example above, local-directories are preferred, and only when no
> local directories are found are path-directories (those found along
> your cdpath) shown.  The default is to display all sets of matches at
> the same time.
> 
> }   From my current point of knowledge I didn't neither know the correct
> }   naming for that behaviour
> 
> It's "completion".
> 

Re: TAB-expansion problems

[Bart Schaefer]

On Mar 13,  9:54am, Meino Christian Cramer wrote:
}
}  Ok, I "killed" cdpath and now my <TAB> does not report "everything
}  ever seen" anymore.

The tag-order style that I suggested would achieve this without having
to kill cdpath, just in case you find cdpath useful in other cases.
 
}  Suppose your are here:
} 
} 		 $HOME/ThisDir/AnotherDir
} 
}  and in ./AnotherDir there is another dir called "WhereIWantToBe"
} 
}  [...] does zsh "see" the one and only directoy
}  "WhereIWantToBe" and gives me
} 
} 	 cd WhereIWantToBe
} 
}  right after hitting <TAB>?

Yes.

ESC-Question

[Meino Christian Cramer]

Hi,

 again a beginner's question:  ;)

 From bash I am used to hit ESC when a completion will fit my needs
 (and still others are possible from the point of view of the shell)
 and wnat to take it (while the cursor is in the middle of the
 suggested word).

 This seems not to work with zsh and my current configuration. My
 workaround currently is to use CTRL-E (cursor to end of line -- I am
 using the Emacs kbd-settings)).

 Is there a way to emulate this ESC-behaviour without removing other
 features...

 And another question:

 Suppose I am builing up a short """""script""""" on the commandline:
 A simple loop over filenames for example.

 After first run of the script I want to add another line to that
 script.

 Scrolling back in history gives me the whole script nicely printed in
 several lines (NOT on a loooooong one-liner! What a nice zshish
 feature!).

 With EMACS-related keys I easily can step through the lines...BUT how
 can I open a NEW line? My workaround is a way really hurtung an
 EMACS-freak like me (at this point of the text of my mail there is a
 BIG HUGH SMILEY!):

 I hit ALT-x (execute) and enter the command 

   vi-open-line-above (...-below)

 because the simple <RETURN> at the and of the line will execute the
 script again....

 Is there a Emacs-keybinding or Emacs-related command to open a line ?
 

 Thank you very much for any help in advance !

 Keep zshing!
 Meino

Re: ESC-Question

[Philippe Troin]

Meino Christian Cramer <Meino.Cramer@gmx.de> writes:

>  Suppose I am builing up a short """""script""""" on the commandline:
>  A simple loop over filenames for example.
> 
>  After first run of the script I want to add another line to that
>  script.
> 
>  Scrolling back in history gives me the whole script nicely printed in
>  several lines (NOT on a loooooong one-liner! What a nice zshish
>  feature!).
> 
>  With EMACS-related keys I easily can step through the lines...BUT how
>  can I open a NEW line? My workaround is a way really hurtung an
>  EMACS-freak like me (at this point of the text of my mail there is a
>  BIG HUGH SMILEY!):
> 
>  I hit ALT-x (execute) and enter the command 
> 
>    vi-open-line-above (...-below)
>
>  because the simple <RETURN> at the and of the line will execute the
>  script again....
> 
>  Is there a Emacs-keybinding or Emacs-related command to open a line ?

  C-v C-j

Or substitute whichever character is your tty's lnext char (as can
been seen from stty -a).

Alternately, M-Enter always creates a new line without submitting the
input for processing.

Phil.

Re: ESC-Question

[Meino Christian Cramer]

From: Philippe Troin <phil@fifi.org>
Subject: Re: ESC-Question
Date: 13 Mar 2005 23:44:56 -0800

Hi Phil !

 Thanks a lot for the hint...gives me a whole lotta more of space (new
 lines) for nice zshish code ! :)
 
 Sometimes (often!) just the simple things are makeing life so much
 easier ! ;O)))))))

 Keep zshing!
 Meino

 PS: Just cause I am a little curious... :)
     Under Emacs each keycode is bound to a named function like
	 forward-search-regexp and such...what is the corresponding
	 function in zsh? insert-line ? Or what is its name ?

> Meino Christian Cramer <Meino.Cramer@gmx.de> writes:
> 
> >  Suppose I am builing up a short """""script""""" on the commandline:
> >  A simple loop over filenames for example.
> > 
> >  After first run of the script I want to add another line to that
> >  script.
> > 
> >  Scrolling back in history gives me the whole script nicely printed in
> >  several lines (NOT on a loooooong one-liner! What a nice zshish
> >  feature!).
> > 
> >  With EMACS-related keys I easily can step through the lines...BUT how
> >  can I open a NEW line? My workaround is a way really hurtung an
> >  EMACS-freak like me (at this point of the text of my mail there is a
> >  BIG HUGH SMILEY!):
> > 
> >  I hit ALT-x (execute) and enter the command 
> > 
> >    vi-open-line-above (...-below)
> >
> >  because the simple <RETURN> at the and of the line will execute the
> >  script again....
> > 
> >  Is there a Emacs-keybinding or Emacs-related command to open a line ?
> 
>   C-v C-j
> 
> Or substitute whichever character is your tty's lnext char (as can
> been seen from stty -a).
> 
> Alternately, M-Enter always creates a new line without submitting the
> input for processing.
> 
> Phil.
> 

Re: ESC-Question

[Peter Stephenson]

Meino Christian Cramer wrote:
>  PS: Just cause I am a little curious... :)
>      Under Emacs each keycode is bound to a named function like
> 	 forward-search-regexp and such...what is the corresponding
> 	 function in zsh? insert-line ? Or what is its name ?

Reading the zshzle manual page should help, particularly the entry for
"bindkey".  To find out the mapping between keys and commands, run
"bindkey", or "bindkey -L" to see it in the form that can be used to
restore each binding in future.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************

Re: ESC-Question

[Meino Christian Cramer]

From: Peter Stephenson <pws@csr.com>
Subject: Re: ESC-Question 
Date: Mon, 14 Mar 2005 17:09:55 +0000

Hi,

 Oh...uuuhhh....I think I need a brain-update...  :)

 I thought ZLE was somehow obsoleted or outdated and was replaced by
 something """internal""" or did I get something wrong or confused
 here ?

 Or was it the completion system...oh damn...I think less coffee and
 more sleep would be a good idea...though times currently...sorry.

 Ok, a good hint...I will inhale the ZLE related manual! 

 Thanks a lot for all your patience ! If I have finished my move
 straight through germany to my new working place and new home I hope
 I will be able to ask more reasonable questions ;) :O)

 Keep zshing!
 Meino

> Meino Christian Cramer wrote:
> >  PS: Just cause I am a little curious... :)
> >      Under Emacs each keycode is bound to a named function like
> > 	 forward-search-regexp and such...what is the corresponding
> > 	 function in zsh? insert-line ? Or what is its name ?
> 
> Reading the zshzle manual page should help, particularly the entry for
> "bindkey".  To find out the mapping between keys and commands, run
> "bindkey", or "bindkey -L" to see it in the form that can be used to
> restore each binding in future.
> 
> -- 
> Peter Stephenson <pws@csr.com>                  Software Engineer
> CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
> Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070
> 
> 
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
> 
> **********************************************************************
> 

Re: ESC-Question

[Philippe Troin]

Peter Stephenson <pws@csr.com> writes:

> Meino Christian Cramer wrote:
> >  PS: Just cause I am a little curious... :)
> >      Under Emacs each keycode is bound to a named function like
> > 	 forward-search-regexp and such...what is the corresponding
> > 	 function in zsh? insert-line ? Or what is its name ?
> 
> Reading the zshzle manual page should help, particularly the entry for
> "bindkey".  To find out the mapping between keys and commands, run
> "bindkey", or "bindkey -L" to see it in the form that can be used to
> restore each binding in future.

Or M-x describe-key-briefly <ENTER> <keypress>.

The reverse: M-x where-is <ENTER> <widget name> <ENTER>
                                    ^--- <TAB> autocompletes

Phil.

Re: ESC-Question

[Sami Samhuri]

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

* On Mon Mar-14-2005 at 05:37:46 AM +0100, Meino Christian Cramer said:
> Hi,
[...]
>  I hit ALT-x (execute) and enter the command 
> 
>    vi-open-line-above (...-below)
> 
>  because the simple <RETURN> at the and of the line will execute the
>  script again....
> 
>  Is there a Emacs-keybinding or Emacs-related command to open a line ?

Not as visually appealing, but you can separate commands using the
semi-colon. So when you hit C-p and want to add another command just
type a ; first and then continue with the next command.

Another way to do it is using zsh's history expansion[1].
!! recalls the previous command so you can type:

    % !! ; <next command line to execute>

I know this is not what you asked for, but I hope this helps a bit.

[1] I don't want to rant because I'm really fond of history expn, but
you should look into them further at:
http://zsh.sunsite.dk/Doc/Release/zsh_13.html#SEC48

-- 
Sami Samhuri

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Ex-bash script for optimisation

[zzapper]

Hi
Q1) Is there a better way to generate the array filelst
Q2) the line "for x in *$1*" fails is no match, how can i "catch" this

#!/bin/zsh
# v
# description : vi all files containing $1 in name
#               but excluding non-text files
set +x

filebad=''
filelst=()
filenum='1'
for x in *$1*
do
   if [[ "$x" == *.(aux|toc|dvi|aux|exe|obj|zip|pdf|mdb|xls|bak|swp|log|jpg|gif|tiff|jpeg|bmp) ]]
   then
      let filebad=1
   else 
      if [ -f $x ]
      then
      filelst[$filenum]=$x
      let filenum=filenum+1
      fi
   fi
done

if (( ${#filelst} ))
then
echo "file list : " $filelst
gvim.exe ${filelst[*]} &
else
echo "sorry no file matched *$1*"
fi

Re: Ex-bash script for optimisation

[Peter Miller]

zzapper wrote:
> Hi
> Q1) Is there a better way to generate the array filelst
> Q2) the line "for x in *$1*" fails is no match, how can i "catch" this

I use "for x in *$1*(N)" to get null glob semantics (remove pattern with no
matches).

I don't know if it is better, but you can use something like

filelst[$(($#filelst+1))]=$x

Re: Ex-bash script for optimisation

[Bart Schaefer]

Comments on script style:

None of the variables is declared (with "declare" or "local") so this is
probably not suitable for use as an autoloaded shell function.

"filebad" is set but not used, and there's no reason to use "let" syntax
if you're not doing arithmetic (in the assignment of 1 to filebad).

On Mar 10,  4:43pm, zzapper wrote:
} Subject: Ex-bash script for optimisation
}
} Q1) Is there a better way to generate the array filelst

Sure.  You don't need the loop, just do a glob with an extended pattern.

#--- snip ---
setopt local_options extended_glob null_glob
filelst=( *$1*~*.(aux|toc|dvi|aux|exe|obj|zip|pdf|mdb|xls|bak|swp|log|jpg|gif|tiff|jpeg|bmp) )
#--- snip ---

If you want to allow $1 to be a pattern rather than a fixed string, you
need *${~1}* instead.

If you want to allow multiple arguments to the script, you need *${^*}*
or for multiple patterns *${^~*}*

In the event that you really need to loop, zsh 4.2+ supports array append
with the syntax:	filelst+=($x)

} Q2) the line "for x in *$1*" fails is no match, how can i "catch" this

Peter Miller's *$1*(N) suggestion is equivalent to the "null_glob"
setting in my example above.

Re: Ex-bash script for optimisation

[zzapper]

On Fri, 11 Mar 2005 04:48:46 +0000,  wrote:

>Comments on script style:
>
>None of the variables is declared (with "declare" or "local") so this is
>probably not suitable for use as an autoloaded shell function.
>
>"filebad" is set but not used, and there's no reason to use "let" syntax
>if you're not doing arithmetic (in the assignment of 1 to filebad).
>
>On Mar 10,  4:43pm, zzapper wrote:
>} Subject: Ex-bash script for optimisation
>}
>} Q1) Is there a better way to generate the array filelst
>
>Sure.  You don't need the loop, just do a glob with an extended pattern.
>
>#--- snip ---
>setopt local_options extended_glob null_glob
>filelst=( *$1*~*.(aux|toc|dvi|aux|exe|obj|zip|pdf|mdb|xls|bak|swp|log|jpg|gif|tiff|jpeg|bmp) )
>#--- snip ---
>
>If you want to allow $1 to be a pattern rather than a fixed string, you
>need *${~1}* instead.
>
>If you want to allow multiple arguments to the script, you need *${^*}*
>or for multiple patterns *${^~*}*
>
>In the event that you really need to loop, zsh 4.2+ supports array append
>with the syntax:	filelst+=($x)
>
>} Q2) the line "for x in *$1*" fails is no match, how can i "catch" this
>
>Peter Miller's *$1*(N) suggestion is equivalent to the "null_glob"
>setting in my example above.
Oh gosh!

Re: Ex-bash script for optimisation

[zzapper]

On Fri, 11 Mar 2005 04:48:46 +0000,  wrote:


>
>#--- snip ---
>setopt local_options extended_glob null_glob
>filelst=( *$1*~*.(aux|toc|dvi|aux|exe|obj|zip|pdf|mdb|xls|bak|swp|log|jpg|gif|tiff|jpeg|bmp) )
>#--- snip ---
>
>If you want to allow $1 to be a pattern rather than a fixed string, you
>need *${~1}* instead.
>
>If you want to allow multiple arguments to the script, you need *${^*}*
>or for multiple patterns *${^~*}*
>
Bart
Only the first example worked for me, but I found $1 could be a pattern, and i could set a second
parameter w/o problem

setopt local_options extended_glob null_glob
filelst=( *$1*~*.(aux|toc|dvi|aux|exe|obj|zip|pdf|mdb|xls|bak|swp|log|jpg|gif|tiff|jpeg|bmp) )

if (( ${#filelst} ))
then
echo "file list : " $filelst
gvim.exe ${filelst[*]} &
else
echo "Sorry no file matched *$1*"
fi

Re: Ex-bash script for optimisation

[Bart Schaefer]

On Mar 13,  6:46pm, zzapper wrote:
} Subject: Re: Ex-bash script for optimisation
}
} Only the first example worked for me, but I found $1 could be a pattern

I think you're misunderstanding what happens.

I don't know what the name of your script/function is, so I'll "vit" for
purposes of example (short for "vim text").  Suppose there is a directory
containing the files

	file.aux	file.exe	file.gif	file.txt

(1) If you give the command

	vit file*

then zsh will first expand the pattern to

	vit file.aux file.exe file.gif file.txt

and next call the function "vit" which will do (shortened for simplicity)

	filelst=( *file.aux*~*.(aux|gif|exe) )

and will eventually print "Sorry no file matched *file.aux*".  Note that
vit did nothing with file.exe file.gif file.txt, which are $2 $3 $4.

(2) If instead you tried

	vit f*t

the result is

	vit file.txt

and thus

	filelst=( *file.txt*~*.(aux|gif|exe) )

(3) If you quote the pattern

	vit 'file*'

then vit does

	filelst=( *file\**~*.(aux|gif|exe) )

and you get "Sorry no file matched *file**" which might be confusing.

What I meant about allowing $1 to be a pattern is, with ${~1} in the
filelst assignment expression you can pass the pattern quoted as in (3),
and internally to vit the pattern is expanded and you'd find file.txt
as desired.

What I meant about multiple arguments to the script is, with ${^*} in
the filelst assignment, example (1) becomes

	filelst=( *file.aux*~*.(aux|gif|exe)
		  *file.exe*~*.(aux|gif|exe)
		  *file.gif*~*.(aux|gif|exe)
		  *file.txt*~*.(aux|gif|exe) )

which again finds file.txt as desired.

I'm hoping you can extrapolate from there to what I meant by "multiple
patterns".

} and i could set a second parameter w/o problem

I'm afraid I don't understand what you mean by that.  "Set" how?  And
is anything useful done with the "second parameter"?  If so, what?  Or
is it just silently ignored?