zsh-users
 help / color / mirror / code / Atom feed
From: Sean <schliden@gmail.com>
To: "Lloyd Zusman" <ljz@asfast.com>
Cc: zsh-users@sunsite.dk
Subject: Re: Does zsh have an equivalent to the shopt command ?
Date: Fri, 28 Jul 2006 10:25:14 +1000	[thread overview]
Message-ID: <96c45c490607271725o59c970bdt71ba7fe3f620317e@mail.gmail.com> (raw)
In-Reply-To: <87y7ufcsnu.fsf@asfast.com>

As Lloyd pointed out, the script is a little long to post inline, but
is available here:

http://todotxt.com/download/todo.sh

Peter, I tried your replacement suggestion, but it also (after a long
think) crashed zsh.

I have come up with this brilliant fix:

version()
{
  echo "TODO.TXT Manager
Version 1.7.1
Author:  Gina Trapani (ginatrapani@gmail.com)
Release date:  5/11/2006
Last updated:  7/20/2006
License:  GPL, http://www.gnu.org/copyleft/gpl.html
More information and mailing list at http://todotxt.com"
    exit 1
}

Cheers

Sean

On 7/27/06, Lloyd Zusman <ljz@asfast.com> wrote:
> Sean <schliden@gmail.com> writes:
>
> > Sorry for the slow reply... wife's birthdays seems to take preceedence :^)
> >
> > I can run sed from the command line ok, and all of the other sed stuff
> > in the script works.
> >
> > It seems to be something to do with processing these text blocks:
> >
> > <<EndVersion
> > EndVersion
> >
> > <<EndHelp
> > EndHelp
> >
> > <<Endusage
> > EndUsage
> >
> > I have tried saving these in seperate files and running them but zsh
> > crashes immeadiately, without outputting a single line.
> >
> > What does:   -e 's/^    //'  do anyway ?
> >
> > Perhaps I can work around this with a different approach.
> >
> > Cheers
> >
> > Sean
>
> Again, could you post the entire script, from top to bottom?  It will be
> easier to help you with this if you do so.
>
> The "-e ..." stuff you mention above strips the leading whitespace out
> of the lines within the here document, e.g., between "<<EndVersion" and
> "EndVersion".
>
>
> >
> > On 7/24/06, Peter Stephenson <pws@csr.com> wrote:
> >> Sean wrote:
> >> > The message fails to print and the shell hangs !
> >>
> >> I can't reproduce that.  What happens if you run the sed (and its
> >> here-document) from the command line, or by running ". file" on a file
> >> that contains only the sed command?  Could the path to "sed" be wrong?
> >>
> >> pws
> >>
> >>
> >> To access the latest news from CSR copy this link into a web browser:  http://www.csr.com/email_sig.php
> >>
> >
>
> --
>  Lloyd Zusman
>  ljz@asfast.com
>  God bless you.
>
>


  parent reply	other threads:[~2006-07-28  0:25 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
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 [this message]
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=96c45c490607271725o59c970bdt71ba7fe3f620317e@mail.gmail.com \
    --to=schliden@gmail.com \
    --cc=ljz@asfast.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).