From: dev+git@drbeat.li
To: git@vger.kernel.org
Cc: tboegi@web.de, Beat Bolli <dev+git@drbeat.li>
Subject: [PATCH 5/5] update_unicode.sh: Delete the command group
Date: Fri, 19 Dec 2014 15:39:31 +0100 [thread overview]
Message-ID: <1418999971-21548-5-git-send-email-dev+git@drbeat.li> (raw)
In-Reply-To: <1418999971-21548-1-git-send-email-dev+git@drbeat.li>
From: Beat Bolli <dev+git@drbeat.li>
Now that the whole file is generated by one single command, the command
group is no longer needed.
Signed-off-by: Beat Bolli <dev+git@drbeat.li>
---
update_unicode.sh | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/update_unicode.sh b/update_unicode.sh
index 61968d9..45bd12a 100755
--- a/update_unicode.sh
+++ b/update_unicode.sh
@@ -26,9 +26,9 @@ fi &&
./configure --enable-warnings=-Werror CFLAGS='-O0 -ggdb'
fi &&
make
- ) && {
- UNICODE_DIR=. && export UNICODE_DIR &&
- printf "\
+ ) &&
+ UNICODE_DIR=. && export UNICODE_DIR &&
+ printf "\
static const struct interval zero_width[] = {
%s
};
@@ -36,8 +36,7 @@ static const struct interval double_width[] = {
%s
};
" \
- "$(uniset/uniset --32 cat:Me,Mn,Cf + U+1160..U+11FF - U+00AD |
- grep -v plane)" \
- "$(uniset/uniset --32 eaw:F,W)"
- } >$UNICODEWIDTH_H
+ "$(uniset/uniset --32 cat:Me,Mn,Cf + U+1160..U+11FF - U+00AD |
+ grep -v plane)" \
+ "$(uniset/uniset --32 eaw:F,W)" >$UNICODEWIDTH_H
)
--
2.1.3
next prev parent reply other threads:[~2014-12-19 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 14:39 [PATCH 1/5] update_unicode.sh: simplify output capture dev+git
2014-12-19 14:39 ` [PATCH 2/5] update_unicode.sh: set UNICODE_DIR only once dev+git
2014-12-19 14:39 ` [PATCH 3/5] update_unicode.sh: shorten uniset invocation path dev+git
2014-12-19 14:39 ` [PATCH 4/5] update_unicode.sh: Make the output structure visible dev+git
2014-12-19 15:22 ` Jeff King
2014-12-19 15:43 ` Beat Bolli
2014-12-19 15:48 ` Jeff King
2014-12-19 14:39 ` dev+git [this message]
2014-12-19 15:12 ` [PATCH 1/5] update_unicode.sh: simplify output capture Beat Bolli
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=1418999971-21548-5-git-send-email-dev+git@drbeat.li \
--to=dev+git@drbeat.li \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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;
as well as URLs for NNTP newsgroup(s).