From: Sebastian Stark <seb@biskalar.de>
To: Peter Stephenson <Peter.Stephenson@csr.com>
Cc: zsh-users@zsh.org
Subject: Re: _screen calls non-existent program
Date: Tue, 19 Oct 2010 15:52:25 +0200 [thread overview]
Message-ID: <2D499F17-875D-4BD9-80D9-2700A504ED8D@biskalar.de> (raw)
In-Reply-To: <20101019135822.0082a9e6@pwslap01u.europe.root.pri>
Am 19.10.2010 um 14:58 schrieb Peter Stephenson:
> "screen-sessions" is just the name to use in the completion context.
> The command should be in $words[1], which should be "screen". "screen
> -ls" does the right thing.
>
> The real problem is the completion system hasn't actually been told to
> complete a session here. The _arguments specification is:
>
> '-S[name this session <pid>.sockname instead of <pid>.<tty>.<host>]:session name'
>
> which simply outputs "session name", but doesn't try to complete
> anything. This is presumably because it's a new session, so completing
> exactly an existing session isn't useful. However, I can see that
> completing an existing session might help you create a new name with
> minimal typing. If you change that line (around 84) to
>
> '-S[name this session <pid>.sockname instead of <pid>.<tty>.<host>]:session name:->any-sessions'
Thank you, this works for me.
> you'll get that effect. It could be a style, I suppose.
I think it should be default, at least in the -X case, because in this case -S is used to choose from existing sessions. (see my other email).
Sebastian
next prev parent reply other threads:[~2010-10-19 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 12:21 Sebastian Stark
2010-10-19 12:51 ` Frank Terbeck
2010-10-19 13:00 ` Sebastian Stark
2010-10-19 13:07 ` Mikael Magnusson
2010-10-19 13:48 ` Sebastian Stark
2010-10-19 12:58 ` Peter Stephenson
2010-10-19 13:52 ` Sebastian Stark [this message]
2010-10-19 14:13 ` Peter Stephenson
2010-10-19 23:11 ` Phil Pennock
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=2D499F17-875D-4BD9-80D9-2700A504ED8D@biskalar.de \
--to=seb@biskalar.de \
--cc=Peter.Stephenson@csr.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).