Timeline for Why does this perl script give different results from git-for-windows vs. windows subsystem for linux?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jun 13, 2020 at 21:24 | history | suggested | annahri | CC BY-SA 4.0 |
reformatting
|
| Jun 13, 2020 at 15:21 | review | Suggested edits | |||
| S Jun 13, 2020 at 21:24 | |||||
| Jun 13, 2020 at 13:51 | vote | accept | AronGahagan | ||
| Jun 13, 2020 at 12:19 | answer | added | AronGahagan | timeline score: 0 | |
| Jun 12, 2020 at 14:03 | comment | added | Rakesh Sharma | Since bash -c "......" is enrobed in double quotes so you need to escape the $1 of the perl code. OTW it will be taking that as a blank(unless, horror of horrors, its set and you will see strange output). It's a problem of quoting. Better to interchange your single and double quotes. | |
| Jun 11, 2020 at 14:37 | comment | added | D. SM |
You are using a character class ([abc], in your case a negated one [^abc]) which permits every character to be matched in any position. The pipes you've added and the opening parenthesis are considered as the allowed characters along with newlines and the quote.
|
|
| Jun 11, 2020 at 14:29 | comment | added | AronGahagan | @D.SM - I'm still learning regex, but the point there was to exclude either new line OR carriage return OR an apostrophe from the capturing group. | |
| Jun 11, 2020 at 8:21 | comment | added | ruud | have a look at the characterset [^(\n|\r|\x27]. I think you need [^\n\r\x27], but there is something wrong with the ( in the character set. You should debug it first. | |
| Jun 11, 2020 at 5:44 | comment | added | D. SM | That's a weird regular expression. Why do you have two pipes in it? | |
| Jun 11, 2020 at 5:20 | review | First posts | |||
| Jun 11, 2020 at 7:41 | |||||
| Jun 11, 2020 at 5:14 | history | asked | AronGahagan | CC BY-SA 4.0 |