zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: <zsh-users@zsh.org>
Subject: Re: completion of filenames
Date: Fri, 13 Dec 2019 16:24:03 +0000	[thread overview]
Message-ID: <1576254243.5214.21.camel@samsung.com> (raw)
In-Reply-To: <a57f9aca-c7a1-6527-8f31-c9be6f00b3f0@eastlink.ca>

On Fri, 2019-12-13 at 07:59 -0800, Ray Andrews wrote:
> On 2019-12-10 8:59 a.m., Ray Andrews wrote:
> > 
> > On 2019-12-10 8:30 a.m., Peter Stephenson wrote:
> > > 
> > > 
> > > Suffix aliases are already handled.  So if it's a file in the current 
> > > directory,
> > > you should find typing ./<tab> completes files with a suffix alias 
> > > defined.
> > > 
> > > pws
> > > 
> > Doesn't work.  This could be something I've botched up myself. Here's 
> > what I think is relevant:
> > 
> If no one has any ideas about this, I'm tempted to try to tinker with it 
> myself.

[Haven't be been here before...?]

Well, you're welcome to do that, of course, but I can't help thinking
you're shooting yourself in the foot.  The system is designed to work
out of the box; while you can make it do other things, obviously that
implies you need some understanding of how it works before you can build
it up yourself.  Your questions don't tend to suggest that's currently
the case.  Background reading (such as Oliver's chapters in From Bash To
Z Shell) and studying the documentation and the shell code itself are
the first steps to getting there.  Questions here that are going to get
useful answers are probably going to be along the lines of "I read about
X but I don't understand Y" rather than "I don't know what to do but
maybe it's got something to do with Z".  (This is supposed to be
practical --- what I think people will respond to --- not normative ---
I'm not telling you to shut up.)

If you're trying to get completion for suffix aliases going, the normal
way to do this would be to assure yourself they work with a vanilla set
up, then see what configuration of yours is stopping it working.  In my
experience, this is generally more effective that telling people that
what you've currently got doesn't work.

pws


  reply	other threads:[~2019-12-13 16:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20191210161919epcas1p2c60b547299b6425434345c4f26071643@epcas1p2.samsung.com>
2019-12-10 16:17 ` Ray Andrews
2019-12-10 16:30   ` Peter Stephenson
2019-12-10 16:59     ` Ray Andrews
2019-12-10 17:16       ` Peter Stephenson
2019-12-10 17:45         ` Ray Andrews
2019-12-13 15:59       ` Ray Andrews
2019-12-13 16:24         ` Peter Stephenson [this message]
2019-12-13 17:06           ` Ray Andrews
2019-12-13 19:46             ` Bart Schaefer
2019-12-13 21:10               ` Ray Andrews

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=1576254243.5214.21.camel@samsung.com \
    --to=p.stephenson@samsung.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).