From: Frank Terbeck <ft@bewatermyfriend.org>
To: meino.cramer@gmx.de
Cc: zsh-users@zsh.org
Subject: Re: Lua / zsh problems
Date: Tue, 19 Jun 2012 21:03:06 +0200 [thread overview]
Message-ID: <87vcinqg45.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <20120619182724.GC3191@solfire> (meino cramer's message of "Tue, 19 Jun 2012 20:27:24 +0200")
meino.cramer@gmx.de wrote:
[...]
> echo $LUA_PATH
>
> gives:
>
> zsh: no matches found:
> LUA_PATH='/usr/lib64/lua/luarocks/share/lua/5.1//?.lua;/usr/lib64/lua/luarocks/share/lua/5.1//?/init.lua;/usr/share/lua/5.1//?.lua;/usr/share/lua/5.1//?/init.lua;/usr/lib64/lua/luarocks/share/lua/5.1//?.lua;/usr/lib64/lua/luarocks/share/lua/5.1//?/init.lua;/usr/share/lua/5.1//?.lua;/usr/share/lua/5.1//?/init.lua;./?.lua;/usr/local/share/lua/5.1/?.lua;/usr/local/share/lua/5.1/?/init.lua;/usr/local/lib/lua/5.1/?.lua;/usr/local/lib/lua/5.1/?/init.lua;/usr/share/lua/5.1/?.lua;/usr/share/lua/5.1/?/init.lua'
You're probably setting the "prompt_subst" option, which is not the
default.
If you set it you need to double quote all parameters to avoid file name
expansion. So you would do this:
echo "$LUA_PATH"
But really, why set that option? IMHO zsh fixes one of the biggest
faults of POSIX shells by not expanding globs and by not IFS-splitting
non-quoted string variables... unless you ask for it explicitly.
If you like the POSIX like behaviour better you need to abide by its
most important idiom too: Double-quote *EVERY* parameter you use, unless
you *know* you want the non-quoted behaviour.
> and lua does not find any extensions at all.
I don't know why that is, though.
<guess>The semicolons are correct as delimiters?</guess>
Regards, Frank
--
In protocol design, perfection has been reached not when there is
nothing left to add, but when there is nothing left to take away.
-- RFC 1925
next prev parent reply other threads:[~2012-06-19 19:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 18:27 meino.cramer
2012-06-19 19:03 ` Frank Terbeck [this message]
2012-06-19 19:05 ` 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=87vcinqg45.fsf@ft.bewatermyfriend.org \
--to=ft@bewatermyfriend.org \
--cc=meino.cramer@gmx.de \
--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).