From: Rocky Bernstein <rocky.bernstein@gmail.com>
To: zsh-users@zsh.org
Subject: custom command completion for a zshdb, a REPL
Date: Mon, 9 May 2011 09:09:32 -0400 [thread overview]
Message-ID: <BANLkTikMEjU+TaXXL4G=pehATUu7obrAEQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]
I would like to add debugger command completion to the zsh debugger, zshdb.
I have looked over the manual pages zshzle and zshcompsys and am still a
bit confused.
I would be grateful if someone could give a simple script as an example.
Suppose the list of REPL (read, print, loop) commands is in a
blank-delimited string variable "cmds", and that one of the commands is
"foo" which has the list of subcommands for it in string variable "subcmd".
For comparison here is the corresponding bash code:
typeset cmds; cmds='foo food woot' # My RLE commands
level0_complete_fn() {
if (( COMP_POINT > 0)) ; then
COMPREPLY=( $(compgen -W "$cmds" "$COMP_LINE") )
else
COMPREPLY=( $cmds )
fi
}
typeset subcmds; foo_subcmds='bar baz'
foo_subcmd_complete() {
COMPREPLY=( $foo_subcmds )
}
# Use a special version of bash read that handle's readline completion
enable -f /src/external-vcs/bashdb/builtin/readc readc
complete -D -F level0_complete_fn
complete -F foo_subcmd_complete foo
# Shell initialization
shopt -s progcomp
set -o emacs
bind 'set show-all-if-ambiguous on'
bind 'TAB:menu-complete'
readc -e -p 'huh? ' line
echo "you sez $line"
I would not like to have completion files the available commands and
sub-commands can be dynamic. For example, on the stack frame completion
might be a positive integer up to the number of stack frames. And this
changes in the course of execution.
Thanks.
next reply other threads:[~2011-05-09 13:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 13:09 Rocky Bernstein [this message]
2011-05-10 9:59 ` Peter Stephenson
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='BANLkTikMEjU+TaXXL4G=pehATUu7obrAEQ@mail.gmail.com' \
--to=rocky.bernstein@gmail.com \
--cc=zsh-users@zsh.org \
/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).