zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Completion in braces limitation
Date: Wed, 28 Apr 1999 09:43:30 -0700	[thread overview]
Message-ID: <990428094331.ZM3151@candle.brasslantern.com> (raw)
In-Reply-To: <199904280719.JAA16812@beta.informatik.hu-berlin.de>

On Apr 28,  9:19am, Sven Wischnowsky wrote:
} Subject: Re: Completion in braces limitation
}
} > cd $(sw)/{<tab>
} > 
} > This expands $(sw) and quotes the brace. There may be a reason for doing
} > this but I can't think of one.
} 
} This is (again) intentional. To get rid of it, use complete-word
} instead of expand-or-complete.

Right; the "reason for it" is that you implicitly asked zsh to attempt
expansion before completion.

} I vaguely remember a discussion about this (several years ago), where, 
} if I remember correctly, most people said that one sometimes want to
} complete after a parameter expansion, but almost never after a command 
} substitution.

The problem with completing after a command substitution is that it has
to actually execute the command to figure out what to complete.  There's
no way to predict the side effects of executing the command multiple
times (at least twice -- once when completing and once when executing
the whole command line) so it's better to never start down the road.

Dunno if this is frequently-asked enough to be worthy of a FAQ entry ...

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1999-04-28 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-28  7:19 Sven Wischnowsky
1999-04-28 16:43 ` Bart Schaefer [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-05-03  9:25 Sven Wischnowsky
1999-04-27 13:37 Sven Wischnowsky
1999-04-27 15:45 ` Oliver Kiddle
1999-04-27 12:56 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=990428094331.ZM3151@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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).