From: Sebastian Stark <seb-zsh@biskalar.de>
To: Frank Terbeck <ft@bewatermyfriend.org>
Cc: zsh-users@zsh.org
Subject: Re: _screen calls non-existent program
Date: Tue, 19 Oct 2010 15:00:03 +0200 [thread overview]
Message-ID: <549B08AA-447B-4F16-AC26-BECE5C5F538F@biskalar.de> (raw)
In-Reply-To: <87zkuagxbq.fsf@ft.bewatermyfriend.org>
Am 19.10.2010 um 14:51 schrieb Frank Terbeck:
> Sebastian Stark wrote:
>> Looking at _screen I see that the list of existing sessions should come from
>>
>> _call_program screen-sessions $words[1] -ls
>>
>> Now I'm wondering what the screen-sessions command should look like,
>> it is not available on any of my machines. To me it looks a bit like
>> it is the same as screen itself, because of the -ls option. But than I
>> don't get the $words[1] part.
>
> `_call_program' enables you to actually *change* the used program via a
> style. `screen-session' is the tag used with the command
> style. "$words[1]" is the first word of the command the completion is
> run on. In other words "screen". Thus, the default program being run
> here is "screen -ls".
Thanks for explaining. .oO(must read manual page harder ...)
Anyway, it does not work for me:
% screen -ls
There is a screen on:
22789.ttys000.suck (Attached)
1 Socket in /var/folders/zz/zzzivhrRnAmviuee+++2I+++-3+/-Tmp-/.screen.
% screen -S <tab>
session name
No session is displayed in the "session name" menu by the completion system. I have no customisation regarding screen in my configuration ("zstyle -L | grep screen" is empty). I still must be doing something wrong here.
Sebastian
next prev parent reply other threads:[~2010-10-19 13:00 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 [this message]
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
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=549B08AA-447B-4F16-AC26-BECE5C5F538F@biskalar.de \
--to=seb-zsh@biskalar.de \
--cc=ft@bewatermyfriend.org \
--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).