| Anonymous | Login | Signup for a new account | 11-10-2008 11:00 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 | ||||
| 0000811 | [BusyBox] Other | major | always | 04-02-06 12:47 | 02-11-08 10:15 | ||||
| Reporter | Belgabor | View Status | public | ||||||
| Assigned To | BusyBox | ||||||||
| Priority | normal | Resolution | no change required | ||||||
| Status | closed | Product Version | |||||||
| Summary | 0000811: Bugs in command line escaping with lash | ||||||||
| Description |
Two related issues: 1. Some characters are escaped inside "" or '', but normally everything inside those should be passed as is to the command. Example: echo "Test []*\1" expected output: Test []*\1 lash's output: Test \[\]\* (and at the end some strange character which refuses to be copy'n'pasted here properly. I suspect the 1 was tranlated to char 0x01) 2. lash escapes [] on tab completion, but passes the inserted \ to the command Example: let's assume we have a file named 'Test [a].txt' Using tab completeion we get (in any shell, including lash): echo Test\ \[a\].txt Expected output: Test [a].txt lash's output: Test \[a\].txt So either [] should not be escaped by lash or it should require and remove the backslashes. Was checked with version 1.1.1 |
||||||||
| Additional Information | |||||||||
| Attached Files | |||||||||
|
|
|||||||||
| Copyright © 2000 - 2006 Mantis Group |