From: DervishD <zsh@dervishd.net>
To: Com MN PG P E B Consultant 3 <mn-pg-p-e-b-consultant-3.com@siemens.com>
Cc: zsh-users Mailinglist <zsh-users@sunsite.dk>
Subject: Re: "here" document broken? (New findings)
Date: Fri, 28 Oct 2005 12:16:47 +0200 [thread overview]
Message-ID: <20051028101647.GD233@DervishD> (raw)
In-Reply-To: <6F0CB04509C11D46A54232E852E390AC44B9AB@MCHP7R6A.ww002.siemens.net>
Hi Ronald :)
* Com MN PG P E B Consultant 3 <mn-pg-p-e-b-consultant-3.com@siemens.com> dixit:
> The following script, call it zsh_here, works well:
>
> #!/bin/zsh -f
> cat << EOD
> xxx
> EOD
>
> If I change it like this, it does not work anymore:
>
> #!/bin/zsh
> cat << EOD
> xxx
> EOD
>
> If I execute it, I get the error message
>
> zsh_here:2: no such file or directory
Try this:
#!/bin/zsh
cat << EOD
EOD
If you still get the error, then the problem is in the "cat" line
(which I assume from the error output and line number) and in some
interaction with RC files.
> (1) If in the "good" version (version 1), I explicitly source .zshenv
> and .zshrc, it still works.
Then the problem is probably not on those files but on /etc/zsh*
ones.
> I start to suspect that this zsh version (4.0.7) is broken. Unless
> someone has another idea where to look, I try to persuade our
> sysadmin to install a newer version (I know this won't be easy...).
First let's take a look at the /etc/zsh* files. If you source
them explictly in your first example, does it still work?
Can you install a new version of zsh locally (in your home) and
run it to reproduce the error?
Raúl Núñez de Arenas Coronado
--
Linux Registered User 88736 | http://www.dervishd.net
http://www.pleyades.net & http://www.gotesdelluna.net
It's my PC and I'll cry if I want to...
next prev parent reply other threads:[~2005-10-28 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 9:34 Com MN PG P E B Consultant 3
2005-10-28 10:16 ` DervishD [this message]
2005-10-28 15:13 ` Bart Schaefer
2005-11-02 6:38 Com MN PG P E B Consultant 3
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=20051028101647.GD233@DervishD \
--to=zsh@dervishd.net \
--cc=mn-pg-p-e-b-consultant-3.com@siemens.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).