zsh-users
 help / color / mirror / code / Atom feed
From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: completion is over thinking things.
Date: Sun, 29 Sep 2019 17:19:08 +0200	[thread overview]
Message-ID: <CAP+y1xBgezKOL2ToTrNz9g3yLkFLnuEWg4TfukQ42r-41a3PPw@mail.gmail.com> (raw)
In-Reply-To: <3894eb29-b17a-0bf3-21f9-f9c44cb37428@eastlink.ca>

[-- Attachment #1: Type: text/plain, Size: 1988 bytes --]

would it be enough a widget that does always filesystem completion
regardless of the command line so far, to be binded to a different-than-tab
shortcut?
that’s been my approach to the same problem, I also have special
only-directories and only-regular-files widgets too

Il giorno dom 29 set 2019 alle 17:12 Ray Andrews <rayandrews@eastlink.ca>
ha scritto:

> On 2019-09-29 6:09 a.m., Mikael Magnusson wrote:
> >
> > Claiming that completion not completing invalid arguments for your
> > command is an "issue" seems pretty far fetched to me. If you always
> > want to complete files, don't run compinit in your startup files.
> >
> I appreciate the sophistication of that, but there are times when I
> really do want to complete on a filename even if it might seem like an
> invalid argument superficially.  I thought that compinit was the entire
> completion system!  Commenting it out and restarting, just as you say, I
> get 'dumb' file completions just as wanted.  Can we have it both ways?
> That is, tweak compinit so that perhaps on a final press of the TAB key
> it  will fall back to dumb file completion even if a kosher match has
> not been found?  Or some sort of temporary fallback to dumb completion?
> Most of the time it seems that file completion is all that's happening
> and anyway this sort of issue is very rare here, but short of restarting
> it would be nice to have dumb completion 'override' when wanted.
> Perhaps if a final press of TAB was used then instead of this:
>
> Completing package
>
> ... we'd see:
>
> Fallback to completing file
>
> ... or something like that.
>
> I looked at zcompdump and there's nothing in there that looks
> promising.  I know that completion is the most inscrutable part of zsh,
> so I won't even attempt to understand it, and any tweak will be taken
> without question and on authority.  Or is there an approachable
> document?  Or some workaround?
>
>
>
> --
Pier Paolo Grassi

  reply	other threads:[~2019-09-29 15:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-28 17:05 Ray Andrews
2019-09-28 17:13 ` Roman Perepelitsa
2019-09-28 17:36   ` Ray Andrews
2019-09-29  4:47     ` dana
2019-09-29 15:29       ` Ray Andrews
2019-09-29 16:44         ` Bart Schaefer
2019-09-29 18:41           ` Ray Andrews
2019-09-29 19:06             ` Bart Schaefer
2019-09-29 19:35               ` Ray Andrews
2019-09-29 13:09     ` Mikael Magnusson
2019-09-29 15:11       ` Ray Andrews
2019-09-29 15:19         ` Pier Paolo Grassi [this message]
2019-09-28 17:14 ` gmail

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=CAP+y1xBgezKOL2ToTrNz9g3yLkFLnuEWg4TfukQ42r-41a3PPw@mail.gmail.com \
    --to=pierpaolog@gmail.com \
    --cc=rayandrews@eastlink.ca \
    --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).