| Anonymous | Login | Signup for a new account | 11-10-2008 11:03 PST |
| Main | My View | View Issues | Change Log | Docs |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
| 0000922 | [BusyBox] Standards Compliance | minor | always | 06-21-06 23:01 | 02-12-08 02:12 | ||||
| Reporter | falk | View Status | public | ||||||
| Assigned To | BusyBox | ||||||||
| Priority | normal | Resolution | fixed | ||||||
| Status | closed | Product Version | svn | ||||||
| Summary | 0000922: msh doesn't forward arguments with '=' to scripts | ||||||||
| Description |
I've got a couple of scripts using an arg=val scheme. I found the script "argtest" #!/bin/msh echo $# $0 $1 $2 $3 $4 $5 called with argtest one two=2 should give as a result: 2 ./argtest one two=2 with msh I get: 1 ./argtest one only ./argtest one 'two\=three' gives the expected result. Quoting is not an option for me as the arguments are passed to another script I'm not sure if it was a bug or a feature to ignore arguments with "=" but the following changes fixed the thing for me. At a glance the assign() call is only there to check if there might be an assignment, not to actually create the vars internally... Didn't check too much for side effects... Should be cross checked by someone with more knowledge about the msh internals. Falk |
||||||||
| Additional Information | |||||||||
| Attached Files |
|
||||||||
|
|
|||||||||
| Copyright © 2000 - 2006 Mantis Group |