zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: greg@alphatech.com, zsh-workers@math.gatech.edu (Zsh list)
Subject: Re: quick question about user defined zle widgets
Date: Thu, 5 Nov 1998 10:32:36 -0800	[thread overview]
Message-ID: <981105103236.ZM29230@candle.brasslantern.com> (raw)
In-Reply-To: <13889.58788.469493.330819@catbus.alphatech.com>

On Nov 5, 12:51pm, Greg Klanderman wrote:
} Subject: quick question about user defined zle widgets
}
} Is it possible when defining a shell function as a user defined 
} widget to access the prefix argument?

I posted a patch to pass the prefix argument as a positional parameter,
but Zefram objects to using the positional parameters of widget functions
and so didn't include it in the release.

There are also several bugs (all of which I reported, search the archive)
involving widget functions that invoke others via the "zle" command, one
of which causes the prefix arg to get bizarre (usually very large) values.

} Also, is there any way when calling a builtin widget to figure out
} the status?  For example, I'd like to do "zle complete-word" in my
} widget and then determine if:
} 
}   - it completed something
}   - there were no completions
}   - choices were listed
}   - choices had already been listed and it did nothing

I believe my patch also arranges to return a sensible exit code from the
"zle" command based on the return of the widget that is called, but I
don't recall for certain and I think Zefram objected to this as well.

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


      reply	other threads:[~1998-11-05 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-05 17:51 Greg Klanderman
1998-11-05 18:32 ` Bart Schaefer [this message]

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=981105103236.ZM29230@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=greg@alphatech.com \
    --cc=zsh-workers@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).