From: Sean <schliden@gmail.com>
To: "Peter Stephenson" <pws@csr.com>
Cc: zsh-users@sunsite.dk
Subject: Re: Does zsh have an equivalent to the shopt command ?
Date: Mon, 24 Jul 2006 21:23:21 +1000 [thread overview]
Message-ID: <96c45c490607240423u131caf80w6e5d667c735a65b9@mail.gmail.com> (raw)
In-Reply-To: <200607241001.k6OA1rvM003764@news01.csr.com>
The message fails to print and the shell hangs !
On 7/24/06, Peter Stephenson <pws@csr.com> wrote:
> Sean wrote:
> > On futher investigation, it appears that it is not actually choking on
> > that line, rather this code which appears in many of the case option
> > function calls:
> >
> > version() { sed -e 's/^ //' <<EndVersion
> > TODO.TXT Manager
> > Version 1.6.3
> > Author: Gina Trapani (ginatrapani@gmail.com)
> > Release date: 5/11/2006
> > Last updated: 7/6/2006
> > License: GPL, http://www.gnu.org/copyleft/gpl.html
> > More information and mailing list at http://todotxt.com
> > EndVersion
> > exit 1
> > }
>
> Hmmm... again, that should work fine and does on my machine; the
> shell isn't asked to do anything much beyond parsing a here document.
> When you say "chokes", what do you mean? Obviously calling the
> function will cause the shell to exit, because of the "exit 1" at the
> end ; is it failing to print the message, exiting in some odd way,
> hanging...? Or are you saying the options to the parent function (with
> the getopts) are such that this function shouldn't be called? In which
> case, what combination of options to that function is causing unexpected
> behaviour? (I could believe getopts behaved differently from bash but I
> need to see the command line being passed.)
>
> I'm guessing a lot of the spaces in that function were actually
> tabs, but I've put those back and not had any problem.
>
> --
> Peter Stephenson <pws@csr.com> Software Engineer
> CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
> Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
>
>
> To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
>
next prev parent reply other threads:[~2006-07-24 11:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <96c45c490607220357h2c841b20q506de061f0e6f43b@mail.gmail.com>
[not found] ` <200607221508.k6MF8W0w002651@pwslaptop.csr.com>
2006-07-24 7:44 ` Sean
2006-07-24 10:01 ` Peter Stephenson
2006-07-24 11:23 ` Sean [this message]
2006-07-24 11:35 ` Lloyd Zusman
2006-07-24 11:38 ` Peter Stephenson
2006-07-27 3:38 ` Sean
2006-07-27 9:18 ` Lloyd Zusman
2006-07-27 15:12 ` john_oshea
2006-07-28 0:25 ` Sean
2006-07-27 10:17 ` Peter Stephenson
2006-07-19 16:44 Sean
2006-07-19 18:06 ` Jean-Rene David
2006-07-20 9:47 ` Peter Stephenson
2006-07-22 2:16 ` Sean
2006-07-22 10:36 ` 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=96c45c490607240423u131caf80w6e5d667c735a65b9@mail.gmail.com \
--to=schliden@gmail.com \
--cc=pws@csr.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).