zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: Ahmad Ismail <ismail783@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: how to use tags in zsh completion system
Date: Wed, 26 Aug 2020 13:01:42 +0100 (BST)	[thread overview]
Message-ID: <1531690126.1436177.1598443302340@mail2.virginmedia.com> (raw)
In-Reply-To: <CAHAhJw+-jWgOxeKp=94VXEJnRvj7G2NTWrUOVW_96UB8RXr=nA@mail.gmail.com>

> On 26 August 2020 at 12:28 Ahmad Ismail <ismail783@gmail.com> wrote:
> 
> Hi Peter Stephenson,
> 
> This is the first time I am using a mailing list. So, I am not sure whether
> I am doing it correctly or not.
> 
> Do I need to always refer to my previous mail or will you be able to figure
> out my previous mails?

Usually people quote the most relevant sections, but people won't
expect to be able to reconstruct the entire thread from a single email

> Do I need to view my email and its correspondence from
> https://www.zsh.org/mla/ or everything will be in the inbox?

If you're not on the list, people should copy you so you will see
everything (it's useful to mention if you're not on the list).

If you are on the list, you'll get everything anyway.

> Being said that, I tried:
>
> % scp hosts

You're missing the point here.  A tag is entirely an idea within the
completion system itself.  Most commands you can just type <TAB>
and it will complete for you.  Only very occasionally do you
need to configure it do something else.  When you do,
then you put commands involving tags in your intialisation file.
You never need to type them on the command line.

So at this point, the completion system already knows various things
are possible --- a host name, a file, a username --- depending how
you're going to build the command line.  The tags are just logical
names for these things.  (The completion system does a bit
of guesswork about where to find things that are specific to
the scp command, so occasionally it needs a bit of help there.)

If you're just starting from scratch with the completion system, i
suggest you just ignore tags for now.  The system is designed so
most of the time it should "just work".

If you find a case where you actually need to tell it to be cleverer,
that's the time to start thinking about tags.  That would be a
case where multiple completions are possible, but you decide you
need to complete only one type of thing.  That's a rather
advanced use.

Until then, I should just try using the system "out of the box"
and see how that works for you.

Cheers
pws


  reply	other threads:[~2020-08-26 12:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-26  8:59 Ahmad Ismail
2020-08-26 10:57 ` Peter Stephenson
2020-08-26 11:28   ` Ahmad Ismail
2020-08-26 12:01     ` Peter Stephenson [this message]
2020-08-26 12:39       ` Ahmad Ismail
2020-09-04 19:23   ` Daniel Shahaf
2020-09-05 11:29     ` Ahmad Ismail

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=1531690126.1436177.1598443302340@mail2.virginmedia.com \
    --to=p.w.stephenson@ntlworld.com \
    --cc=ismail783@gmail.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).