more interactive menu completion

more interactive menu completion

[Le Wang]

Hi,

I'm using menu completion now, and I absolutely love
it.  However I was just thinking that all of my
keyboard keys are unmapped during menu completion, so
wouldn't it be nice if I could press 'abc', and have
the selection go to the first file starting with an
'abc'?  This is very much like the way modern file
managers work (e.g. Explorer,  Konqueror, etc), except
they only match the first letter.

It would be great if this kind of widget can be
refined to do substring matching as well.  Does this
kind of completion scheme currently exist for Zsh?

--
Le

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca

RE: more interactive menu completion

[Borzenkov Andrey]

> 
> I'm using menu completion now, and I absolutely love
> it.  However I was just thinking that all of my
> keyboard keys are unmapped during menu completion, so
> wouldn't it be nice if I could press 'abc', and have
> the selection go to the first file starting with an
> 'abc'?  This is very much like the way modern file
> managers work (e.g. Explorer,  Konqueror, etc), except
> they only match the first letter.
> 
> It would be great if this kind of widget can be
> refined to do substring matching as well.  Does this
> kind of completion scheme currently exist for Zsh?
> 

There is incremental-complete-word widget that does what you want. I do not
know if it is widely used, so your comments would be welcome.

incremental-complete-word
     This allows incremental completion of a word.  After starting this
     command, a list of completion choices can be shown after every
     character you type, which you can delete with ^H or DEL.  Pressing
     return accepts the completion so far and returns you to normal
     editing (that is, the command line is _not_ immediately executed).
     You can hit TAB to do normal completion, ^G to abort back to the
     state when you started, and ^D to list the matches.

     This works only with the new function based completion system.

          bindkey '^Xi' incremental-complete-word


You'll need

fpath=($fpath /path/to/zsh/functions/Zle)
autoload incremental-complete-word

(unless done already).

It did not work for me after quick test :(

-andrey

RE: more interactive menu completion

[Le Wang]

 --- Borzenkov Andrey <Andrey.Borzenkov@siemens.com>
wrote: > 
> > Here is an extension of the problem.  Say I have a
> > bunch of functions that operate on $PATH, how
> would I
> > generalize it so that it works with any $PATH like
> > variable?
> > 
> 
> Hmm ... have you noticed that every your question
> needs at least one reply
> that requests clarification what you really mean? No
> offence intended :)

None taken.  I will strive to refine my problem
descriptions.  

My problem is as follows:

I currently have:

addToPath () {...}

and I use it as:

addToPath ~/bin/scripts

I would like to have

addToPathVar () {...}

and use it as:

addToPathVar CLASSPATH ~/java/lib

--
Le

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca

Re: more interactive menu completion

[Peter Stephenson]

Le Wang wrote:
> My problem is as follows:
> 
> I currently have:
> 
> addToPath () {...}
> 
> and I use it as:
> 
> addToPath ~/bin/scripts
> 
> I would like to have
> 
> addToPathVar () {...}
> 
> and use it as:
> 
> addToPathVar CLASSPATH ~/java/lib

Here's my current solution to this particular problem; it goes back a
few versions of zsh hence it doesn't use all the latest features.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070

## cut
# addpath()  # -*-ksh-*-

# Replace or delete a value in a PATH-type variable.
# The first argument is the variable name (not its value, i.e. no $).
# The second is the component to add.
#
# Options:  there are two sets of mutually exclusive options (i.e.
# the options inside the set are mutually exclusive, one from each
# set may be used):
#   The first set applies if the component is currently in the path.
#	-k	Keep it where it is (default).
#	-r	Replace it as given by the -a/-p option.
#	-d	Delete it from the path.
#   If it was not already in the path, or if -r was given, then:
#	-a	Append the value to the end of the variable (default).
#	-p	Prepend the value to the beginning of the variable.

local var add before after varnam
local where=-a mode=-k

# We don't want substituted text from parameters to be used as patterns.
[[ -n $ZSH_VERSION ]] && setopt localoptions
unsetopt globsubst

Usage() {
  echo 'Usage: addpath [-k|r|d] [-a|p] variable value'
  echo '-k|r|d: keep (default), replace or delete'
  echo '-a|p: append (default) or prepend'
}

Doadd() {
  # Uses $varnam, $var and $add from main function
  local result
  case "$where" in
  -a)
    result="${var}:${add}"
    ;;
  *)
    result="${add}:${var}"
    ;;
  esac
  eval "$varnam=\"$result\""
}

while [[ $1 = -* && $1 != '-' ]]
do
  case "$1" in
  -[ap])
    where=$1
    shift
    ;;
  -[krd])
    mode=$1
    shift
    ;;
  *)
    Usage
    return 1
    ;;
  esac
done
[[ $1 = '-' ]] && shift

(( $# != 2)) && Usage && return 1

eval var=\"\$$1\"
varnam=$1
shift
add=$1
shift

case "$var" in
*:$add:*|*:$add|$add:*|$add)
  case "$mode" in
    -k)	# do nothing
	;;
    *)
       # Remove the old value.
       local found=true
       while [[ $found = true ]]; do
	 case "$var" in
	   *:$add:*) var="${var%%:$add:*}:${var#*:$add:}"
		     ;;
	   *:$add) var="${var%%:$add}"
		   ;;
	   $add:*) var="${var##$add:}"
		   ;;
	   *) found=false
	      ;;
	 esac
       done
       # and replace it if necessary
       if [[ $mode = -d ]]; then
	 eval "$varnam=\"$var\""
       else
	 Doadd
       fi
       ;;
  esac
  ;;
"")
  if [[ $mode != -d ]]; then
    eval "$varnam=\"$add\""
  fi 
  ;;
*)
   if [[ $mode != -d ]]; then
     Doadd
   fi
   ;;
esac

unfunction Usage Doadd
##cut


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************

RE: passing arrays

[Le Wang]

 --- Borzenkov Andrey <Andrey.Borzenkov@siemens.com>
wrote: > 
> > Here is an extension of the problem.  Say I have a
> > bunch of functions that operate on $PATH, how
> would I
> > generalize it so that it works with any $PATH like
> > variable?
> > 
> 
> Hmm ... have you noticed that every your question
> needs at least one reply
> that requests clarification what you really mean? No
> offence intended :)

None taken.  I will strive to refine my problem
descriptions.  

My problem is as follows:

I currently have:

addToPath () {...}

and I use it as:

addToPath ~/bin/scripts

I would like to have

addToPathVar () {...}

and use it as:

addToPathVar CLASSPATH ~/java/lib

--
Le

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca

RE: more interactive menu completion

[Sven Wischnowsky]

Borzenkov Andrey wrote:

> > 
> > I'm using menu completion now, and I absolutely love
> > it.  However I was just thinking that all of my
> > keyboard keys are unmapped during menu completion, so
> > wouldn't it be nice if I could press 'abc', and have
> > the selection go to the first file starting with an
> > 'abc'?  This is very much like the way modern file
> > managers work (e.g. Explorer,  Konqueror, etc), except
> > they only match the first letter.
> > 
> > It would be great if this kind of widget can be
> > refined to do substring matching as well.  Does this
> > kind of completion scheme currently exist for Zsh?
> > 
> 
> There is incremental-complete-word widget that does what you want. I do not
> know if it is widely used, so your comments would be welcome.

In the development version, there is also incremental mode of menu
selection, see the docs for the `complist' module and for the new
completion system (under the `menu' style).


Bye
  Sven

-- 
Sven Wischnowsky                          wischnow@berkom.de

RE: more interactive menu completion

[Borzenkov Andrey]

> In the development version, there is also incremental mode of menu
> selection, see the docs for the `complist' module and for the new
> completion system (under the `menu' style).
> 

Wow! It really works! May wonders never cease ...

For others, it refers to (quoting complist documentation):

viinsert
     this toggles between normal and interactive mode; in interactive
     mode the keys bound to self-insert and self-insert-unmeta insert
     into the command line as in normal editing mode but without leaving
     menu selection; after each character completion is tried again and
     the list changes to contain only the new matches; the completion
     widgets make the longest unambiguous string be inserted in the
     command line and undo and backward-delete-char go back to the
     previous set of matches

-andrey

Re: more interactive menu completion

[Peter Stephenson]

Borzenkov Andrey wrote:
> For others, it refers to (quoting complist documentation):
> 
> viinsert

except it's actually `vi-insert'.

Index: Doc/Zsh/mod_complist.yo
===================================================================
RCS file: /cvsroot/zsh/zsh/Doc/Zsh/mod_complist.yo,v
retrieving revision 1.16
diff -u -r1.16 mod_complist.yo
--- Doc/Zsh/mod_complist.yo	26 Jun 2002 11:07:46 -0000	1.16
+++ Doc/Zsh/mod_complist.yo	20 Jan 2003 16:05:40 -0000
@@ -332,7 +332,7 @@
 item(tt(reverse-menu-complete))(
 moves the mark to the previous match
 )
-item(tt(viinsert))(
+item(tt(vi-insert))(
 this toggles between normal and interactive mode; in interactive mode
 the keys bound to tt(self-insert) and tt(self-insert-unmeta) insert
 into the command line as in normal editing mode but without leaving

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************

RE: more interactive menu completion

[Le Wang]

--- Sven Wischnowsky <wischnow@berkom.de> wrote:
> 
> Borzenkov Andrey wrote:
> 
> > > 
> > > I'm using menu completion now, and I absolutely
> love
> > > it.  However I was just thinking that all of my
> > > keyboard keys are unmapped during menu
> completion, so
> > > wouldn't it be nice if I could press 'abc', and
> have
> > > the selection go to the first file starting with
> an
> > > 'abc'?  This is very much like the way modern
> file
> > > managers work (e.g. Explorer,  Konqueror, etc),
> except
> > > they only match the first letter.
> > > 
> > > It would be great if this kind of widget can be
> > > refined to do substring matching as well.  Does
> this
> > > kind of completion scheme currently exist for
> Zsh?
> > > 
> > 
> > There is incremental-complete-word widget that
> does what you want. I do not
> > know if it is widely used, so your comments would
> be welcome.
> 
> In the development version, there is also
> incremental mode of menu
> selection, see the docs for the `complist' module
> and for the new
> completion system (under the `menu' style).


That is very nice.  The functionality is exactly what
I had in mind.  Once again, I'm very impressed with
Zsh! :)

One note about the user interface of this
"interactive" menu completion mode:  Why have a
'vi-insert' key binding at all?  I don't see any
reason for it.  IMHO "interactive" mode should be able
to be toggled on or off permanently (maybe throuth
styles).

cheers.

--
Le


______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca

RE: more interactive menu completion

[Borzenkov Andrey]

> >
> > In the development version, there is also
> > incremental mode of menu
> > selection, see the docs for the `complist' module
> > and for the new
> > completion system (under the `menu' style).
                       ^^^^^^^^^^^^^^^^^^^^^^
> 
> 
> That is very nice.  The functionality is exactly what
> I had in mind.  Once again, I'm very impressed with
> Zsh! :)
> 
> One note about the user interface of this
> "interactive" menu completion mode:  Why have a
> 'vi-insert' key binding at all?  I don't see any
> reason for it.  IMHO "interactive" mode should be able
> to be toggled on or off permanently (maybe throuth
> styles).
> 

You have not read carefully enough :)

menu
.....
     Finally, the two special modes of menu selection, namely
     interactive mode and incremental search can be pre-selected with
     this style. By including the word `interactive' in the value,
     interactive mode will be entered immediately when menu selection
     is started and the string `search' does the same for incremental
     search. To select backward incremental search, include the string
     `search-backward'.

It is not default because it is still experimental, it is slow (yes, it _is_
slow) and it is very different from usual way. I personally found that
hitting three times cursor key needs the same time as typing in three
characters of next match :))

-andrey

passing arrays

[Le Wang]

Hi all.

Is it possible to pass an array into a function and
have the function return an array?

--
Le

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca

Re: passing arrays

[Zefram]

Le Wang wrote:
>Is it possible to pass an array into a function and
>have the function return an array?

The arguments to a function are an array, accessible through the
$1/$@/$argv parameters.

A function directly returns only a numeric status.  To return any
other information, it must either assign to a parameter or generate
output (which can be captured using $(...)).  The parameter assignment
technique is usually to be preferred, because it doesn't need to make any
system calls and it's easier for handling arrays.  We already have some
mechanisms where the shell calls a user-defined function and receives
a string or array return code in the parameters $REPLY or $reply;
I suggest that where you need string or array returns you use these
parameter names to do it.

-zefram

Re: passing arrays

[Le Wang]

 --- Zefram <zefram@fysh.org> wrote: > Le Wang wrote:
> >Is it possible to pass an array into a function and
> >have the function return an array?
> 
> The arguments to a function are an array, accessible
> through the
> $1/$@/$argv parameters.

hmm.  I figured as much.

Here is an extension of the problem.  Say I have a
bunch of functions that operate on $PATH, how would I
generalize it so that it works with any $PATH like
variable?

--
le

______________________________________________________________________ 
Post your free ad now! http://personals.yahoo.ca

RE: passing arrays

[Borzenkov Andrey]

> Here is an extension of the problem.  Say I have a
> bunch of functions that operate on $PATH, how would I
> generalize it so that it works with any $PATH like
> variable?
> 

Hmm ... have you noticed that every your question needs at least one reply
that requests clarification what you really mean? No offence intended :)

Returning to your question - if 

foo "$path[@]"

does what you need I do not see any reason why

foo "$bar[@]"

does not. If the question is, how to get a pair of variables like path/PATH
- it is done with typeset,

typeset -T FOO foo

creates an array foo and "colon array" FOO.

-andrey