Michael Z. Kadaner

Results 76 comments of Michael Z. Kadaner

This could be done by extending regex syntax: a pattern to match end-of-line in search string, and special symbol to insert end-of-line in replace string. Visual Studio has this.

@ildar-shaimordanov Could you please clarify the intended behavior? Should new metasymbols apply to the file spec they are attached to, or to rest of the command line? Assuming the file...

OK. Wrong question. Sorry. Let's try again. I added the following test script to the user menu: ``` dir /b !\ dir /b !#!\ echo !# blah !.! !.! ```...

@vfekete, if you point to specific strings, I'll help you with the context.

For `MConfigSortingXxx` this may help: ![system settings](https://user-images.githubusercontent.com/35671029/44948204-62f6a680-adce-11e8-8962-205346d8d4b5.png)

The documentation is a bit confusing. The default value of `rowDelimiter` parameter of the default text extractors (`Text`, `Csv`, `Tsv`) is `null`, which is handled in a very special way....

With the custom extractor, you can call `input.Split("\r\n")`, and it will split the input on `` boundary only. Neither lone `` nor lone `` will be considered row delimiters.

``` TEXT: ID1, ### ID2,Date,Rs,Rs1,Number,Direction,ID3\r\n1,1,9/14/2014 0:00,46.81006, ``` It looks like your file contains a header row. You should use `skipFirstNRows` parameter of CSV extractor: ``` USING Extractors.Csv(skipFirstNRows: 1); ```

Oh, and I eventually noticed `USING Outputters.Csv();` on the first line of the script. You do not need it. Just remove it and your script should be OK. This clause...

I can say nothing about the second issue, but exit code `0xc0000709` strongly suggests that physical memory in your machine is unreliable. Do you get this error each time you...