However the main patchset was not - maybe it just needed resending.
Eric - Do you know what happened here, was it simply a case of not resending it after the extra fix was submitted?
For reference, as far as I know / from testing that patch set, the windows cmd.exe will work fine in the 'copy con filename' mode once this patchset is applied.
The last patch in the series was wrong, and Eric submitted a few attempts to fix this in the console code in December 2012. The most recent set is here: www.winehq. org/pipermail/ wine-patches/ 2012-December/ 121090. html www.winehq. org/pipermail/ wine-devel/ 2013-January/ 098395. html www.winehq. org/pipermail/ wine-devel/ 2013-January/ 098425. html
http://
This had a problem due to a hanging process
(AJ) http://
(Eric) http://
Eric sent in a patch for the hanging process: www.winehq. org/pipermail/ wine-patches/ 2013-January/ 121501. html www.winehq. org/pipermail/ wine-cvs/ 2013-January/ 093158. html
http://
which was committed
http://
However the main patchset was not - maybe it just needed resending.
Eric - Do you know what happened here, was it simply a case of not resending it after the extra fix was submitted?
For reference, as far as I know / from testing that patch set, the windows cmd.exe will work fine in the 'copy con filename' mode once this patchset is applied.