Skip to content

Commit

Permalink
Update 600_show_unprocessed.sh
Browse files Browse the repository at this point in the history 
Better looking code (from my point of view)
because somehow I do not like long strings
that wrap around more than one line
(regardless that it is technically correct).
  • Loading branch information
@jsmeix
jsmeix committed Oct 22, 2019
1 parent 7f82b89 commit da065df
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions usr/share/rear/layout/prepare/default/600_show_unprocessed.sh
View file
Expand Up @@ -14,8 +14,8 @@ choices[4]="Abort '$rear_workflow'"

while read status name type junk ; do
missing_component="$name ($type)"
LogUserOutput "No code has been generated to recreate $missing_component.
To recreate it manually add code to $LAYOUT_CODE or abort."
LogUserOutput "No code has been generated to recreate $missing_component"
LogUserOutput "To recreate $missing_component manually add code to $LAYOUT_CODE or abort"
while true ; do
# The default user input is "Continue" to make it possible to run ReaR unattended
# so that 'rear recover' proceeds after the timeout regardless that it probably fails
Expand Down

1 comment on commit da065df

@jsmeix
Copy link
Member Author

@jsmeix jsmeix commented on da065df Oct 22, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

An addedum FYI:
For me none of the bash lines continuation methods listed at
https://stackoverflow.com/questions/7316107/bash-continuation-lines
makes code with indentation look actually nice to me.
I would appreciate it if C-style string literal concatenation like

    echo "This is a"
         " long line"

would be also possible in bash.

Please sign in to comment.