zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: Oliver Kiddle <okiddle@yahoo.co.uk>
Cc: Zsh workers <zsh-workers@zsh.org>
Subject: Re: completer for file extensions
Date: Sat, 1 Mar 2014 23:54:22 +0100	[thread overview]
Message-ID: <CAHYJk3Rr4Jk_83J=LU4OuB5f2ROpsn95ZTArOmxaqCtifYQZqg@mail.gmail.com> (raw)
In-Reply-To: <626.1393625311@thecus.kiddle.eu>

On 28 February 2014 23:08, Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
> Mikael Magnusson wrote:
>> This - needs to be a .. or BRACE_CCL needs to be set locally. Even
>
> Thanks. It also needs to be .. to work for a number greater than 9.
>
>> with this fix, the completer does nothing for me. I tried printing
>> both $files and $mfiles and they contain more or less the correct list
>> of extensions, but nothing shows up through the completion system.
>
> I checked and it works for me starting from zsh -f.
> If even mfiles contains a list of more than one extension then I can't
> see why the compadd would fail to add matches. Have you got any matching
> controls specified? What's your full completer list?
>
> Oliver

Okay, my problem was just that I have a stupid
command_not_found_handler that tries to autoload and execute things,
and of course that is run in a subshell so no completions were added
in the parent shell. (eg, I forgot to rm .zcompdump).

I have a number of screenshots with . in the name and it causes these
completions to be added;
.00.png     .09.16.png  .13580      .16.png     .36.04.png  .58.png
   .letter     .wav
.04.png     .09.18.png  .14.png     .18.png     .36.45.png
.6.33.config  .log
.06.png     .09.20.png  .14460      .20.png     .37.04.png  .bin
   .log.13580
.09.11.png  .11.png     .14460-1    .27.00.png  .37.06.png  .cfg
   .log.14460
.09.12.png  .12.png     .14460-2    .32.18.png  .45.png     .conf
   .png
.09.14.png  .12863-1    .16.58.png  .33.config  .49.11.png  .config
   .tar

I guess you go for the first . to get stuff like .tar.gz? Tarballs
often have . in the name for version numbers so I have the same issue
in that directory;
.0.1.zip
.0.14.tar.gz
.0.16.tar.gz
.0.17-patches-0.1.tar.bz2
.0.2.tar.bz2
.0.2.tgz
.0.21.tgz


-- 
Mikael Magnusson


  reply	other threads:[~2014-03-01 22:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 13:34 Oliver Kiddle
2014-02-28 21:14 ` Mikael Magnusson
2014-02-28 22:08   ` Oliver Kiddle
2014-03-01 22:54     ` Mikael Magnusson [this message]
2014-03-03 15:33       ` 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='CAHYJk3Rr4Jk_83J=LU4OuB5f2ROpsn95ZTArOmxaqCtifYQZqg@mail.gmail.com' \
    --to=mikachu@gmail.com \
    --cc=okiddle@yahoo.co.uk \
    --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).