From: "André Aparício" <aparicio99@gmail.com>
To: gentoo-soc@lists.gentoo.org
Subject: [gentoo-soc] libbash - Progress report #7
Date: Tue, 10 Jul 2012 02:45:06 +0100 [thread overview]
Message-ID: <20120710024506.51b5c8b5@null> (raw)
Hi,
=== Progress of previous week ===
- Support the 'for' loop with implicit positional list.
for arg; do echo $arg; done
- Support line continuation inside keyword tests.
if [[ 1 == 1 &&
1 == 1 ]]; then echo "Should print this"; fi
- Proper "$@" expansion.
It was expanding to "1 2 3" instead of "1" "2" "3", and now it
expands correctly, and differently for "$@" and "$*" as supposed.
=== Plan for this week ===
Have yet to search for more useful things to fix or implement.
For now I already have one thing to fix, there's a problem in function
names starting with a keyword, like do-func. This isn't very relevant,
but happens at least in one eclass.
https://github.com/Aparicio99/libbash
Best regards,
André Aparício
reply other threads:[~2012-07-10 2:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120710024506.51b5c8b5@null \
--to=aparicio99@gmail.com \
--cc=gentoo-soc@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox