From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: compinit causes completion to fail?
Date: Sun, 29 Apr 2012 17:24:15 -0700 [thread overview]
Message-ID: <120429172415.ZM8837@torch.brasslantern.com> (raw)
In-Reply-To: <11E3E5A7F06F49C2B05AD5289019FC72@gmail.com>
On Apr 29, 2:57am, TJ Luoma wrote:
}
} IFS='
} '
}
} is what was causing the problem.
Could you say a bit more about exactly how this caused a problem? In
normal circumstances the value of IFS shouldn't affect parsing of
scripts etc., it should only affect "read" and parameter substitution.
So I'm puzzled as to how you got the command-not-found symptom.
next prev parent reply other threads:[~2012-04-30 0:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 5:21 TJ Luoma
2012-04-29 6:57 ` TJ Luoma
2012-04-29 18:29 ` Peter Stephenson
2012-04-30 0:24 ` Bart Schaefer [this message]
2012-04-30 5:04 ` TJ Luoma
2012-04-30 14:37 ` Bart Schaefer
2012-04-30 14:50 ` TJ Luoma
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=120429172415.ZM8837@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@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).