From: Anssi Saari <as@sci.fi>
To: zsh-users@zsh.org
Subject: Confused about splitting
Date: Sun, 31 Mar 2019 12:06:16 +0300 [thread overview]
Message-ID: <vg3k1gf4dmf.fsf@coffee.modeemi.fi> (raw)
I have a simple script which uses awk to assign and split a line from a
file to a zsh array. Simplified, just this:
foofunc () {
if [[ $# -ge 1 ]]
then
if=$1
else
if=eno1
fi
first=(`awk /$if/ /proc/net/dev`)
echo $first
echo length of first is $#first
}
Obvious and works, it prints out currently with parameter eno1 this:
eno1: 44977581223 33469291 0 139 0 0 0 57718 12574512832 21508919 0 0 0 0 0 0
length of first is 17
/proc/net/dev currently contains
Inter-| Receive | Transmit
face |bytes packets errs drop fifo frame compressed multicast|bytes packets errs drop fifo colls carrier compressed
lo: 990081491 293912 0 0 0 0 0 0 990081491 293912 0 0 0 0 0 0
eno1: 44978021588 33472121 0 139 0 0 0 57964 12575022205 21512486 0 0 0 0 0 0
But wanting to not call awk I ran into trouble.
If I set shwordsplit, no problem:
foofunc2 () {
if [[ $# -ge 1 ]]
then
if=$1
else
if=eno1
fi
setopt shwordsplit
while read g
do
if [[ $g =~ $if ]]
then
first=($g)
break
fi
done < /proc/net/dev
echo $first
echo length of first is $#first
}
But what if I don't want to set shwordsplit? I came up with
foofunc3 () {
if [[ $# -ge 1 ]]
then
if=$1
else
if=eno1
fi
while read g
do
if [[ $g =~ $if ]]
then
first=${=g}
break
fi
done < /proc/net/dev
echo $first
echo length of first is $#first
}
But this splits each character into an array element. I don't understand
this behavior at all. As I understand it, = in the assignment to $first
is supposed to turn shwordsplit on temporarily but it really doesn't
seem to. IFS is not set so field separator should be default, meaning
whitespace.
This is with zsh 5.3.1 on Debian.
next reply other threads:[~2019-03-31 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-31 9:06 Anssi Saari [this message]
2019-03-31 12:58 ` Daniel Shahaf
2019-03-31 17:56 ` Anssi Saari
2019-03-31 13:12 ` Daniel Shahaf
2019-04-01 9:07 ` Anssi Saari
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=vg3k1gf4dmf.fsf@coffee.modeemi.fi \
--to=as@sci.fi \
--cc=zsh-users@zsh.org \
/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).