From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-users@sunsite.dk
Cc: Will Yardley <william@hq.newdream.net>
Subject: Re: comptctl help
Date: Mon, 30 Jul 2001 09:29:53 +0200 (MET DST) [thread overview]
Message-ID: <200107300729.JAA27146@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <20010727113716.A10777@hq.newdream.net>
Will Yardley wrote:
> ...
>
> this works too. _except_ it puts a space after completing the directory name
> still ie:
> scp ju<tab>
> completes to
> scp junk/[space]
> instead of scp junk/[wait for filename completion still]
Err, right. Add -S '' to the compctl-line. But that leaves the cursor
directly after normal files, too. If you want to fix this, the easiest
solution would probably be to use two different functions...
> i suppose that sometimes you might want to copy a whole directory (and it
> would be really fancy to take a directory arg if you did scp -r but a
> filename only if you just did scp)
> don't know if it's possible to do this.
>
> > This isn't enough information to enable to help you. No way to get
> > newer versions running there?
>
> ok here's one example:
> vader% scp williargv=(willi '')
> am@
Get rid of the loacl-declaration of `argv', it's automatically local anyway.
> it completes it but does this (this is the same .compctl as on the other
> machine).
>
> this also messes up my spacing - if i hit control-u i still have:
> vader% scp williargv=(willi '')
> vader% echo $ZSH_VERSION
> 3.0.7
>
> this isn't really such a big deal since it's only one machine - i may just
> ignore certain completions based on ZSH_VERSION
>
> my personal machines are all 4.0.1, but the majority of the machines i use
> for work are 3.1.9-dev-6 - the stable debian package. aside from building a
> package myself or adapting the unstable package and building it on stable not
> really going to happen (ie there are 110 machines or so and i'm not going to
> install it from source on all of them :>)
Given that, I'd strongly suggest you use the new completion system on
all those 3.1.9 and 4.0.1 machines.
> an example from one of these machines:
>
> yakko% kill -Bad syntax, perhaps a bogus '-'?
> Bad syntax, perhaps a bogus '-'?
>
> ...
>
> or is there just something in here that needs to be different between linux /
> BSD? my personal machines are all freebsd so it's possible that that's the
> difference. anyway i hardly ever use this completion anyway so it's not a
> huge deal - just annoying when i try to use it.
>
> compctl -j -P '%' + -s '`ps -x | tail +2 | cut -c1-5`' + \
> -x 's[-] p[1]' -k "($signals[1,-3])" -- kill
>
> thanks for the help!
One of them has problems with `ps -x', I guess.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
prev parent reply other threads:[~2001-07-30 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 23:52 Will Yardley
2001-07-27 13:42 ` Sven Wischnowsky
2001-07-27 18:37 ` Will Yardley
2001-07-30 7:29 ` Sven Wischnowsky [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=200107300729.JAA27146@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=william@hq.newdream.net \
--cc=zsh-users@sunsite.dk \
/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).