zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Andrei Shevchuk <andrei@shevchuk.co>, zsh-workers@zsh.org
Subject: Re: PATCH: Improve Mosh completion
Date: Mon, 25 Dec 2017 20:06:49 +0000	[thread overview]
Message-ID: <1514232409.2739200.1215674320.1BF9C9E5@webmail.messagingengine.com> (raw)
In-Reply-To: <1510274104.17218.0@smtp.gmail.com>

Thanks for the ping on github.

Andrei Shevchuk wrote on Fri, 10 Nov 2017 03:35 +0300:
> This adds ~/.ssh/config based completion support (_ssh_hosts and 
> _ssh_users functions and userhost state handling taken without 
> modifications from ssh completion file),

Sorry, no.  https://en.wikipedia.org/wiki/Don%27t_repeat_yourself

If you really need to call those two functions, break them out of _ssh into
separate files:

    % head -n1 Completion/*/Type/_ssh_files
    #autoload
    % 

Or — depending on mosh's syntax — it might be better to simply invoke _ssh
(directly or via _normal or one of its friends).

> existing code was just wrapped into _mosh function without modifications
> (except userhost state handling mentioned above).

Please don't mix whitespace and functional changes: that makes the diff harder
to review.

> +++ b/Completion/Unix/Command/_mosh
> @@ -1,26 +1,84 @@
> +    '--port=[specify server-side port range]:port:_sequence -n 2 -s \: 
> _ports' \

As you can see, your MUA mangled the patch (hard line break).  You can avoid
this by sending patches as attachments named *.txt.

Let's continue the discussion on list; there are more eyes here.

Cheers,

Daniel


  reply	other threads:[~2017-12-25 20:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10  0:35 Andrei Shevchuk
2017-12-25 20:06 ` Daniel Shahaf [this message]
2018-01-20  7:23 ` Bart Schaefer
2018-03-22  1:09 ` Oliver Kiddle

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=1514232409.2739200.1215674320.1BF9C9E5@webmail.messagingengine.com \
    --to=d.s@daniel.shahaf.name \
    --cc=andrei@shevchuk.co \
    --cc=zsh-workers@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).