![]() ![]() ![]() Marder-1:/cygdrive/e/mozilla_src/mozilla$Ībout a native port and not the patch that's available through Cygwin. No, the one installed by the cygwin setup program: To assume that since you mention the "Windows version" that your talking What patch are you using? The Cygwin version works fine with '/'. won't build with MSVC ?) with the intention of making my own version that works with '/'.Ĭan anyone confirm that there isn't an undocumented option (cmd line or build) to make it use '/'? If there isn't, why is it that the Windows version works this way, especially when diff(1) DTRT? I have d/l the sources but have yet to build it (am I correct that it needs gcc to build, i.e. Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. I've been using pyzbar to read barcodes which works very good but it seems (or i'm missing out on something) that it can't read patch codes. This is somewhat at odds with diff(1) which uses '/', even on Windows.Īccording to the manpage there is no option to change this behaviour. I'm trying to find a way to read patchT (and/or other patch 1/2/.) separator pages using python. Patch(1) on Win32 seems to insist on '\' rather than '/' in the paths in diffs. On the Others tab of the ISIS driver properties, select Patchcode from the Batch Separation drop-down list. On 18:14 Larry Hall (RFK Partners, Inc) stood on a soap-box Insert the patchcode sheet in front of the document that you want to save as a separate file before placing the documents on the scanner. Subject: Re: patch(1) (Win32) and path separators.This is the mail archive of list for the Cygwin project. Parish - Re: patch(1) (Win32) and path separators
0 Comments
Leave a Reply. |