From: Anssi Saari <as@sci.fi>
To: zsh-users@sunsite.dk
Subject: Re: Vanishing files ?
Date: Mon, 29 May 2006 10:57:22 +0300 [thread overview]
Message-ID: <20060529075722.GA28846@sci.fi> (raw)
In-Reply-To: <060528113200.ZM31855@torch.brasslantern.com>
On Sun, May 28, 2006 at 11:32:00AM -0700, Bart Schaefer wrote:
> On May 28, 5:24pm, Meino Christian Cramer wrote:
> }
> } Why can I execute the contents of the script "tempwatch" but not the
> } script itsself?
>
> That usually means that the program named in the #! line is not where
> the path in that line says it is.
Now that we're on the topic, I think bash does this a little better. If you have an
invalid interpreter, it tells you, like this:
bash: ./foo: /bin/foo: bad interpreter: No such file or directory
Maybe this could be improved with zsh?
> } By the way: Does anyone know a trick how to remove _all_
> } Escape-Sequences from a script generated by the command "script" ...
>
> sed "s/[^"$'\t '"-~]//g"
>
> The order of tab and space in $'\t ' is important. The above actually
> strips anything that's not printable ASCII, so if you're using an ISO
> character set you probably need to put more stuff inside the [ ].
That doesn't really work for escape sequences now does it? For example, on
this machine, my prompt under script is shown in less like this:
^MESC[m^OESC[mESC[mESC[Jkuori% ESC[Kls^M
That sed removes the ^M and escapes, but what it leaves behind is
[m[m[m[Jkuori% [K
next prev parent reply other threads:[~2006-05-29 7:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-28 15:24 Meino Christian Cramer
2006-05-28 18:32 ` Bart Schaefer
2006-05-28 18:38 ` Meino Christian Cramer
2006-05-28 23:24 ` Bart Schaefer
2006-05-29 2:38 ` Meino Christian Cramer
2006-05-29 7:57 ` Anssi Saari [this message]
2006-05-29 15:32 ` Peter Stephenson
2006-05-29 17:51 ` Paul Lew
2006-05-29 18:16 ` De-script (Re: Vanishing files ?) Bart Schaefer
2006-05-28 18:37 ` Vanishing files ? DervishD
2006-05-28 18:44 ` Meino Christian Cramer
2006-05-29 6:11 ` DervishD
2006-05-29 8:56 ` Meino Christian Cramer
2006-05-29 8:58 ` DervishD
2006-05-30 21:59 ` Tobias Gruetzmacher
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=20060529075722.GA28846@sci.fi \
--to=as@sci.fi \
--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).