zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: completion within a function
Date: Tue, 29 Dec 2020 13:48:19 -0800	[thread overview]
Message-ID: <CAH+w=7bSbhdHGC89daK+8o0psLhdw969=GviC4s554t37_zrDw@mail.gmail.com> (raw)
In-Reply-To: <819ec6fe-5af2-2e97-c5bb-f434b1de86d7@eastlink.ca>

On Tue, Dec 29, 2020 at 1:04 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> func ()
> {
> code
>      cd $1 [TAB]
> code
> code
> }
>
> ... so that I can automatically execute a completion within a function.

Where does the TAB come from?

I think what you're actually asking is how to apply the contextual
completion "rules" defined for a command ("cd" in this case) to a
parameter expansion.  There really is not any way to do that
"automatically" because completion is tightly bound to having the ZLE
line editor active.  It could be done the way that the test suite
emulates completion, but that's exceptionally convoluted, especially
error handling.

> 'vared' is a variable editor no?  Does it do more than I think?

If you were to write

func()
{
  code
    vared 1
    cd $1
  code
  code
}

Then at the point vared is invoked, func would pause, wait for the
user to press TAB or whatever, and then after accept-line is executed,
continue with whatever result.

Yes, you actually can vared the positional parameters.

More in response to the next message.


  parent reply	other threads:[~2020-12-29 21:49 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 15:24 Ray Andrews
2020-12-29 18:52 ` Bart Schaefer
2020-12-29 19:36   ` Felipe Contreras
2020-12-29 19:41     ` Roman Perepelitsa
2020-12-29 21:04   ` Ray Andrews
2020-12-29 21:21     ` Ray Andrews
2020-12-29 22:03       ` Bart Schaefer
2020-12-29 21:48     ` Bart Schaefer [this message]
2020-12-30  0:31       ` Ray Andrews
2020-12-30  4:34         ` Roman Perepelitsa
2020-12-30 16:45           ` Ray Andrews
2020-12-30 17:21             ` Felipe Contreras
2020-12-30 20:43               ` Bart Schaefer
2020-12-30 20:46                 ` Bart Schaefer
2020-12-30 20:50                 ` Ray Andrews
2020-12-30 21:31                 ` Roman Perepelitsa
2020-12-30 22:05                   ` Bart Schaefer
2020-12-30 22:18                 ` Felipe Contreras
2020-12-30 23:47                   ` Bart Schaefer
2020-12-31  0:08                     ` Bart Schaefer
2020-12-31  0:12                     ` Felipe Contreras
2020-12-31  0:30                       ` Bart Schaefer
2020-12-31  0:39                         ` Bart Schaefer
2020-12-31  1:04                           ` Felipe Contreras
2020-12-31 21:25                             ` Bart Schaefer
2021-01-01  0:12                               ` Ray Andrews
2021-01-02  0:27                               ` Bart Schaefer
2021-01-02 22:24                                 ` Bart Schaefer
2021-01-03  0:28                                   ` Felipe Contreras
2021-01-03  0:53                                     ` Bart Schaefer
2021-01-03  1:20                                       ` Felipe Contreras
2021-01-03  2:21                                         ` Bart Schaefer
2021-01-03  2:47                                           ` Felipe Contreras
2021-01-03  3:30                                             ` Bart Schaefer
2021-01-03 23:16                                               ` Felipe Contreras
2021-01-05 19:57                                                 ` Bart Schaefer
2021-01-03 17:50                                             ` Bart Schaefer
2021-01-03  0:07                                 ` Felipe Contreras
2020-12-31  1:03                         ` Felipe Contreras
2020-12-30  6:45         ` Bart Schaefer

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='CAH+w=7bSbhdHGC89daK+8o0psLhdw969=GviC4s554t37_zrDw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=rayandrews@eastlink.ca \
    --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).