zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: [Pkg-zsh-devel] Bug#679824: zsh: Buggy perl completion with -e [origin: vincent@vinc17.net]
Date: Thu, 03 Jul 2014 17:11:07 +0100	[thread overview]
Message-ID: <20140703171107.23afc5db@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <9EFC1491-C1F9-407F-B0A7-BFCC51414D51@kba.biglobe.ne.jp>

On Fri, 04 Jul 2014 00:59:13 +0900
"Jun T." <takimoto-j@kba.biglobe.ne.jp> wrote:
> 2014/06/30 22:02, Jun T. <takimoto-j@kba.biglobe.ne.jp> wrote:
> >    python -c '...' <TAB>
> >    ruby -e '...' <TAB>
> > 
> > these will complete a command name, not a file name.
> 
> The following is a patch to fix this.
> 
> In the case of ruby, the current _ruby contains
>   '(-)1:script file:_files'
> This means all files (foo.rb, bar.py, junk.c, etc.) are
> offered as Ruby scripts, but I didn't change this in the
> patch. I have no experience with ruby and don't know
> what most ruby users expect here.

.rb is fairly standard but obviously not required; I don't think there's
any good reason for Ruby to be different from other scripting languages
here, though nobody's ever complained.

Probably the best compromise in general would be to have .pl, .py, .rb
and other files completed using separate tags, so you have the easily
configurable option of picking out the native suffix or all files.

I've a vague memory you can already tell _files to do clever things like
that in certain contexts but I'm too lazy to check.

pws


  reply	other threads:[~2014-07-03 16:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-28 14:20 Fwd: " Axel Beckert
2014-06-30 10:58 ` Jun T.
2014-06-30 13:02   ` Jun T.
2014-07-03 15:59     ` Jun T.
2014-07-03 16:11       ` Peter Stephenson [this message]
2014-07-03 16:42         ` Bart Schaefer
2014-07-06 21:58   ` Oliver Kiddle
2014-07-23 12:01     ` takimoto-j
2014-06-30 11:45 ` Jun T.
2014-06-30 19:09   ` Peter Stephenson

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=20140703171107.23afc5db@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.com \
    --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).