From: Beat Bolli <redacted>
Instead of capturing the output of each echo and uniset invocation, wrap
the whole section in a group command and redirect its output all at
once.
Signed-off-by: Beat Bolli <redacted>
---
update_unicode.sh | 17 +++++++++--------
1 file changed, 9 insertions(+), 8 deletions(-)
From: Beat Bolli <redacted>
Now that the whole file is generated by one single command, the command
group is no longer needed.
Signed-off-by: Beat Bolli <redacted>
---
update_unicode.sh | 23 +++++++++++------------
1 file changed, 11 insertions(+), 12 deletions(-)
From: Beat Bolli <redacted>
The value is the same on both uniset invocations, so "Don't Repeat
Yourself" applies.
Since we're in a subshell already, there's no need to unset UNICODE_DIR
at the end.
Signed-off-by: Beat Bolli <redacted>
---
update_unicode.sh | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
From: Beat Bolli <redacted>
"uniset/uniset" is a relative path; there's no need to prefix it with "./".
Signed-off-by: Beat Bolli <redacted>
---
update_unicode.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
From: Beat Bolli <redacted>
By using a here document instead of the echo/uniset sequence, the final
structure of the generated file becomes obvious.
Signed-off-by: Beat Bolli <redacted>
---
update_unicode.sh | 16 +++++++++-------
1 file changed, 9 insertions(+), 7 deletions(-)
(Technically both do the same)
I personally think that using ./ it is extra obvious that a command is not
from the path somewhere.
But that may be because of my un-careful reading, what do others think ?
Thanks for improving Git