From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "E. Jay Berkenbilt" <ejb@ql.org>, zsh-workers@sunsite.auc.dk
Subject: Re: trivial patch to _rlogin to make rcp complete more like scp
Date: Sat, 18 Nov 2000 16:50:24 +0000 [thread overview]
Message-ID: <1001118165024.ZM8012@candle.brasslantern.com> (raw)
In-Reply-To: <200011181537.KAA06383@soup.ql.org>
On Nov 18, 10:37am, E. Jay Berkenbilt wrote:
}
} scp file hostTAB
}
} where host is something that unambiguously completes to a host, scp
} adds a colon to the end of the host. If you then hit space, the colon
} stays.
}
} If you do the same with rcp, the colon disappears after a space. The
} same thing goes with user@.
}
} I think that keeping the colon is the Right Thing (TM) since it
} actually means something.
}
} I'm not convinced that this is the right behavior with the @.
I'm pretty sure it's not the right behavior with @.
} The only way I could figure this out was to do a careful comparison
} between the _rlogin and _ssh code. The -q flag to _alternative seems
} to be either missing from the documentation or very well hidden.
Look closely:
} _alternative \
} 'files:: _files' \
} - 'hosts:: _rlogin_all_hosts -qS:' \
} - 'users:: _rlogin_users -qS@' && ret=0
} + 'hosts:: _rlogin_all_hosts -S:' \
} + 'users:: _rlogin_users -S@' && ret=0
The -q and -S flags are inside quotation marks; they're not flags to
_alternative, they're flags to _rlogin_all_hosts and _rlogin_users,
which eventually pass them to _combination which passes them to compadd.
This is documented in info, but the comment at the top of _combination
is wildly out of date, particularly with respect to what it says about
how _telnet calls _combination.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
prev parent reply other threads:[~2000-11-18 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-18 15:37 E. Jay Berkenbilt
2000-11-18 16:50 ` 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=1001118165024.ZM8012@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=ejb@ql.org \
--cc=zsh-workers@sunsite.auc.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).