zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Recursive globbing shorthand (a la **.c)
Date: Sat, 31 Oct 2015 13:16:10 -0700	[thread overview]
Message-ID: <151031131610.ZM21483@torch.brasslantern.com> (raw)
In-Reply-To: <20151031092414.GA5301@chaz.gmail.com>

On Oct 31,  9:24am, Stephane Chazelas wrote:
} 
} It reminds me of the discussion about:
} 
} *$var*/foo

That and *$~var*.c inadvertently doing a follow-symlinks if var=*

Furtermore if I've got all of globstarshort globcomplete completinword
and the cursor is on the first * out of **.c, what gets completed?  Or
if I DO NOT have completeinword?  When using expand-or-complete-prefix?

I suppose **/ already has all of these problems, but e.g. the guts of
_path_files isn't likely to accidentally cons up that form.

} (probably not a big issue. Note that bash -O globstar and ksh93
} -o globstar are already affected by that (and yash -o
} extended-glob -c 'echo *$empty*/*' like zsh)).

So we need to add globstar as an alias for globstarshort in ksh and bash
emulations?  Or since globstarshort is new should we just chop off the
"short" and extend it to the other emulations?


  reply	other threads:[~2015-10-31 20:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151028065702.GA8236@linux.vnet.ibm.com>
     [not found] ` <20151029105343.67b579f3@pwslap01u.europe.root.pri>
2015-10-30  9:30   ` Peter Stephenson
2015-10-30 15:50     ` Bart Schaefer
2015-10-31  9:24       ` Stephane Chazelas
2015-10-31 20:16         ` Bart Schaefer [this message]
2015-11-01 18:10           ` 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=151031131610.ZM21483@torch.brasslantern.com \
    --to=schaefer@brasslantern.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).