|
From: | Jannick |
Subject: | [PATCHES] enhancements of sed error messages, using sed on Windows |
Date: | Thu, 1 Nov 2018 21:16:34 +0100 |
Hi, I spent some time today with sed's new and valuable debug feature. Please find attached a series of patches as suggestions for your review and which I would be happy to be committed. I do hope that the commit messages meet the requirements and the coding is alright. Some remarks: #1-2 are meant as suggestions to improve sed's debug features during the preparation phase when sed commands are read and compiled. This feeds into the new debug feature lately added to sed (debug.c). With #4 sed could be more widely used in Windows' dos shell, in particular when working through the examples in the sed manual. Please note that sed exits with an error when (1) sed is compiled with a (gcc compliant) compiler not belonging to the cygwin family and (2) a sed command like 's/1/2/' is called from the dos shell (see commit message #4). This is sadly a showstopper for many Windows users who fail even in the first example of the manual and turn away from sed. #3 is a minor patch on memory leakage. If any questions, please let me know. Please feel free to edit anything as you might think it is best for sed. Many thanks, J.
0004-sed-ignore-enclosing-single-quotes-from-command-line.patch
Description: Binary data
0001-sed-display-the-error-position-by-caret-for-command-.patch
Description: Binary data
0002-sed-enhance-error-reporting-for-script-files.patch
Description: Binary data
0003-sed-fix-memory-leakage.patch
Description: Binary data
[Prev in Thread] | Current Thread | [Next in Thread] |