zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: Ex-bash script for optimisation
Date: Fri, 11 Mar 2005 05:14:17 +0000	[thread overview]
Message-ID: <1050311051417.ZM9377@candle.brasslantern.com> (raw)
In-Reply-To: <20050310.194249.41192134.Meino.Cramer@gmx.de>

On Mar 10,  7:42pm, Meino Christian Cramer wrote:
} Subject: Re: Ex-bash script for optimisation

Please start a new message with a new subject if you're asking a new
question, rather than replying to an unrelated discussion re-using a
misleading subject.  Thank you.

}  I want to limit the expand function (that one called when pressing
}  TAB after entering for example "cd")

It's important to know whether you really mean "expansion" or whether
(as I suspect) you're asking about "completion".

"Expansion" means you have something like a glob pattern, for example
a*e, and you want the shell to replace it with file names that match
the pattern, for example ankle apple argue.  In general, expansion is
not context-sensitive.

"Completion" means you've typed part of a word -- usually a prefix --
and you want the shell to supply the rest of the word in a way that
fits the context where the word appears.  For example, directory names
in the arguments of cd.

}  to file of the current working directory or in other words I want to
}  switch off the global search for expansion possibilities...

This question is a bit mystifying because there normally is no "global
search."  One possibility is that you need to "unset cdpath", but it
would help if you explained more about (1) whether you use "compinit"
to set up completion or are using the built-in defaults, and (2) what
happens when you press TAB that makes you think a "global" search is
being done.


  reply	other threads:[~2005-03-11  5:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-10 18:42 Meino Christian Cramer
2005-03-11  5:14 ` Bart Schaefer [this message]
2005-03-11 18:37   ` TAB-expansion problems Meino Christian Cramer
2005-03-12  9:15     ` Tim Kruse
2005-03-13  4:50     ` Bart Schaefer
2005-03-13  8:54       ` Meino Christian Cramer
2005-03-13 17:21         ` Bart Schaefer
2005-03-14  4:37           ` ESC-Question Meino Christian Cramer
2005-03-14  7:44             ` ESC-Question Philippe Troin
2005-03-14 16:58               ` ESC-Question Meino Christian Cramer
2005-03-14 17:09                 ` ESC-Question Peter Stephenson
2005-03-14 17:22                   ` ESC-Question Meino Christian Cramer
2005-03-14 18:18                   ` ESC-Question Philippe Troin
2005-03-14 10:01             ` ESC-Question Sami Samhuri
  -- strict thread matches above, loose matches on Subject: below --
2005-03-10 16:43 Ex-bash script for optimisation zzapper
2005-03-10 18:15 ` Peter Miller
2005-03-11  4:48   ` Bart Schaefer
2005-03-11  9:04     ` zzapper
2005-03-13 18:46     ` zzapper
2005-03-13 19:23       ` Bart Schaefer

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=1050311051417.ZM9377@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.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).