zsh-workers
 help / color / mirror / code / Atom feed
From: "Jun T." <takimoto-j@kba.biglobe.ne.jp>
To: zsh-workers@zsh.org
Subject: Re: [Pkg-zsh-devel] Bug#679824: zsh: Buggy perl completion with -e [origin: vincent@vinc17.net]
Date: Mon, 30 Jun 2014 22:02:37 +0900	[thread overview]
Message-ID: <461B8CB3-4C88-42D4-987F-3A9C3846EB03@kba.biglobe.ne.jp> (raw)
In-Reply-To: <FC2BB00F-2E7B-4E4A-BFC8-0FE072B26ECB@kba.biglobe.ne.jp>

2014/06/30 19:58, Jun T. <takimoto-j@kba.biglobe.ne.jp> wrote:

> I first thought that just replacing the line 19 of _perl
>    '(   -E)*-e+[run one line of program]:one line of program' \
> by
>    '(1   -E)*-e+[run one line of program]:one line of program' \
> would be enough, but it didn't work. For example
> 
>    perl -e 's/foo/bar/' <TAB>
> 
> will offer all the command names (external commands etc.), instead of
> the file names in the current directory.

I have found that _python and _ruby have this problem:

    python -c '...' <TAB>
    ruby -e '...' <TAB>

these will complete a command name, not a file name.
_python has

  '(1 -)-c+[program passed in as string ...]:python command:'
  '*::script argument: _normal'

while _ruby has

  "(1)*-e+[one line of script ...]:one line of script:"
  '*::script argument: _normal'

Maybe we need to fix them after figuring out how to fix _perl.


  reply	other threads:[~2014-06-30 13:02 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. [this message]
2014-07-03 15:59     ` Jun T.
2014-07-03 16:11       ` Peter Stephenson
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=461B8CB3-4C88-42D4-987F-3A9C3846EB03@kba.biglobe.ne.jp \
    --to=takimoto-j@kba.biglobe.ne.jp \
    --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).