zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>,
	zsh-workers@sunsite.dk
Subject: Re: Using _values with ->state transitions?
Date: Mon, 7 May 2001 15:08:29 +0000	[thread overview]
Message-ID: <1010507150830.ZM27726@candle.brasslantern.com> (raw)
In-Reply-To: <200105070806.KAA01447@beta.informatik.hu-berlin.de>

On May 7, 10:06am, Sven Wischnowsky wrote:
} Subject: Re: Using _values with ->state transitions?
}
} Bart Schaefer wrote:
} 
} > This is supposed to work, isn't it?  There appears to be code for it in
} > _values, but there aren't any examples of it in the existing completion
} > system. I can't get it to do anything sensible in several attempts.
} 
} Hm, the simple test:
} 
}   _values test 'a:arg:->foo' b c
} 
}   if [[ -n $state ]]; then compadd foo bar; fi
} 
} works for me.  How does this fail for you?

OK, that does work for me.  However, it sometimes ignores the -s option.
To wit:

schaefer[505] _tv() {
function> _values -s ':' test 'a:arg:->foo' b c
function> if [[ -n $state ]]; then compadd $state; fi
function> }
schaefer[506] compdef _tv :
schaefer[507] : a<TAB>
schaefer[507] : a=<TAB>
schaefer[508] : a=foo 
                      ^cursor here -- why did that space get added?
		      I expected `a=foo:'.

It would also be nice if there were a way to specify that something other
than an `=' comes between the value and its argument.
 
} > The zsh/computil documentation needs some improvement.
} 
} I always think of computil as something too deeply hidden for ca. 99
} percent of all users and programmers.

Well, then, it's the doc for _values that needs improvement.  The SPECS
for _values are no longer the same as those for _arguments (at best, they
now are a subset).

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  reply	other threads:[~2001-05-07 15:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-05 17:20 Bart Schaefer
2001-05-07  8:06 ` Sven Wischnowsky
2001-05-07 15:08   ` Bart Schaefer [this message]
2001-05-08 12:21     ` Sven Wischnowsky
2001-05-08 15:27       ` Bart Schaefer
2001-05-09  8:53         ` PATCH: " Sven Wischnowsky

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=1010507150830.ZM27726@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.dk \
    /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).