From: DervishD <zsh@dervishd.net>
To: Peter Stephenson <pws@csr.com>
Cc: Zsh Users <zsh-users@sunsite.dk>
Subject: Re: Replacing sed for zsh portability
Date: Mon, 15 Aug 2005 22:21:26 +0200 [thread overview]
Message-ID: <20050815202126.GA64@DervishD> (raw)
In-Reply-To: <2283.1124104964@csr.com>
Hi Peter :)
* Peter Stephenson <pws@csr.com> dixit:
> DervishD wrote:
> > Can this be done in zsh easily or the only way is to use a while
> > loop to ignore lines before the delimiter and another to process the
> > documentation itself?
> A while loop is the obvious way. You can read in the entire file
> (file="$(<file)") and substitute on that. My example succeeded with this:
>
> print -r ${(S)file//$'\n#<='*$'\n#=>'}
This prints all the script *except* the lines I want ;)
Anyway, can I get rid of the 'S' flag if I know that the
delimiter won't appear in the script code?
Using the 'read-entire-file' solution, I'm using this expression
right now:
print -r ${file//(#b)*'#<='(*)'#=>'*/${match//\#/}}
Which gives a segmentation fault! It happens even when doing "zsh
-f", using 4.2.5 (i686-pc-linux-gnu)
This expression below:
print -r ${file//(#b)*'#<='(*)'#=>'*/$match}
gives me the result but with the hashes before the lines, and
uses the '\n' already in the text as separators. A bit prettier,
don't know. And this expression works OK:
print -r ${${file//(#b)*'#<='(*)'#=>'*/$match}//\#}
Don't know why the second substitution works and the first gave a
sigsegv. I may do a little research if you want me to. I'm not
familiar with the sources, but the fail may be on a memcpy call, at
least is there where it fails using gdb without debugging information
:((
> although the following is better since it takes account of the fact
> that a comment may be at the start:
>
> print -r ${(S)file//($'\n'|(#s))\#\<\=*$'\n#=>'}
Fortunately the comment won't never be at the start (the GPL
disclaimer is the first thing in the script just after the bangpath.
> > Another question, related to this. It seems that the X|Y glob
> > operator doesn't work left-to-right, but shortest-first. If I do
> > this:
> >
> > print ${line#\#(<=|=>| |)}
> >
> > then the 'nothing' at the end is used as the match, and the
> > delimiters are not matched.
> You're missing the fact that your substitution is of the form ${line#...}.
> This is explicitly documented to remove the shortest matching chunk at
> the head of the line. Try adding another "#":
>
> print ${line##\#(<=|=>| |)}
Yes, read my autoreply about my stupidity when writing the
expression. I just missed the second '#'. I noticed when rereading my
own message. Only then the single '#' appeared as a beacon. Sorry O:)
Thanks for your answer, Peter :) Very good solution. I refrained
from reading the entire file into memory although I am pretty sure
the scripts are small enough.
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-08-15 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 10:35 DervishD
2005-08-15 10:39 ` DervishD
2005-08-15 11:22 ` Peter Stephenson
2005-08-15 20:21 ` DervishD [this message]
2005-08-16 15:40 ` Vincent Lefevre
2005-08-16 15:51 ` DervishD
2005-08-16 16:18 ` Vincent Lefevre
2005-08-16 16:34 ` Oliver Kiddle
2005-08-16 18:02 ` Vincent Lefevre
2005-08-16 16:54 ` DervishD
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=20050815202126.GA64@DervishD \
--to=zsh@dervishd.net \
--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).