Tidy shell script source file

mmn357157 · 12-19-2008, 12:52 PM

Hi all,

Is there a tool to tidy up shell script source file and reformat it. Preferably I am looking for a perfect tool to do this.

Also I have heard it is possible to do with emacs editor but unfortunately it is looking very different and new from vi. Emacs is new to me and I could not find such an option myself yet.

Thanks,
mmn

tredegar · 12-20-2008, 06:37 AM

Maybe "Bash Script Beautifier"?
http://www.arachnoid.com/linux/beautify_bash/

pixellany · 12-20-2008, 06:45 AM

"Beautify Bash" seems like the ultimate oxymoron......

To me, readable code simply means tabs and comments.....and maybe following a consistent style.....eg:

Code:

#Loop based on output of "ls" in current directory
for name in `ls`; do
    command
    command
done

is more readable than:

Code:

for name in `ls`; do; command; command; done #Loop based on output of "ls" in current directory

If you follow a consistent style, then what will the "beautification" utility add?

custangro · 12-20-2008, 12:53 PM

Quote:

Originally Posted by pixellany

"Beautify Bash" seems like the ultimate oxymoron......

To me, readable code simply means tabs and comments.....and maybe following a consistent style.....eg:

Code:

#Loop based on output of "ls" in current directory
for name in `ls`; do
    command
    command
done

is more readable than:

Code:

for name in `ls`; do; command; command; done #Loop based on output of "ls" in current directory

If you follow a consistent style, then what will the "beautification" utility add?

IMHO $(ls) is easier to read than `ls`

-C

pixellany · 12-20-2008, 02:33 PM

Quote:

Originally Posted by custangro

IMHO $(ls) is easier to read than `ls`

-C

Perhaps, but it's one more keystroke....

Disillusionist · 12-20-2008, 03:33 PM

I have seen instances where a programmer made a minor modification to a piece of code, but he didn't like the way that comments were structured within the code.

Therefore he moved all the comments, so that they lined up.

When performing a diff comparison with the previous version of the code it was nearly impossible to see the actual change that had been made, as a fair proportion of the lines had changed!

unSpawn · 12-20-2008, 06:01 PM

Quote:

Originally Posted by pixellany

Perhaps, but it's one more keystroke....

It's not only easier to read: try nesting both and see which version "just works". Also note the backticks way doesn't remove trailing newlines.

tredegar · 12-20-2008, 06:09 PM

Mods,
Is this thread heading "off topic"?

custangro · 12-20-2008, 07:33 PM

Quote:

Originally Posted by pixellany

Perhaps, but it's one more keystroke....

I always stand alone when it comes to backticks...but since they are depricated (from what I've read)...I'll stick to $()

But for what it's worth, backticks are good when coding for backwards compatibility...you will have better luck having your code be "portable" if you use backticks (I'll give you guys _that_ much

)

Also for those who care

http://wooledge.org:8000/BashFAQ/082

Besides...my boss won't let me use backticks

-C