search

tylerlong / google-code-prettify

Automatically exported from code.google.com/p/google-code-prettify
Apache License 2.0
0 stars 0 forks source link

/* triggers a code comment instead of # in BASH #51

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. In a bash script right something that would use the combination of /*
(or just look at my code here ->
http://code.google.com/p/backup-light/source/browse/trunk/%20backup-light/trunk/
backuplight.sh?r=72#153)

(Please include HTML, not just your source code)

What is the expected output?  What do you see instead?
If you notice on lines 169-175 the programs code and comments are the same
color, but on line 204 the color syntax goes back to normal

What version are you using?  On what browser?
I'm using openSUSE 11.0 with firefox 3
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0) Gecko/2008061600
SUSE/3.0-0.2 Firefox/3.0

Please provide any additional information below.
 This is just a minor issue, the only problem that this causes is that
someone looking over the code has to actually look to see the difference
between code and comments.

Original issue reported on code.google.com by vendion on 1 Aug 2008 at 2:23

GoogleCodeExporter commented 9 years ago 
Right now code.google.com uses language guessing.  Once they add a class with 
the
file extension as a language hint (e.g. "lang-sh") your code should format 
properly.

I added a test to the bash lang one
http://google-code-prettify.googlecode.com/svn/trunk/tests/prettify_test.html#ba
sh_lang
 just to be sure.

I'm going to mark this as fixed, since it's now a matter of google code's push
schedule, but please reopen this bug if the current language handler for Bash 
doesn't
meet your needs.

Original comment by mikesamuel@gmail.com on 1 Aug 2008 at 3:25