This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Problem with -i ignore-file option in version 6.9 ptx in cygwin environment


Eric -

In that original email your were replying to John Cowan, so I thought you were talking about coding approaches.  From your message posted to the Cygwin list, I take it you were offering me, the end user, a way to solve the problem.  

I know about d2u and could use that now that I know what the problem is, but I'm not familiar with binary vs text mounts on a Windows system.  I'm referencing the ignore file with the command line option of "--ignore-file=ptx_ignore.txt".  How do I involve a text mount with that?

Another aspect of this problem from the end user point of view is the different behavior in the handling of the ignore file vs the main data input file.  I constructed both files in the same way (using vim on Windows).  ptx reads and processes the standard input just fine, but from the user's point of view, just ignores the content of the ignore file. :-)

If nothing else, it would help if the man page for ptx had something about this issue.

Thanks for listening,
Graig

----- Original Message ----
From: Eric Blake <ebb9@byu.net>
To: cygwin@cygwin.com; Graig McHendrie <graigm@sbcglobal.net>
Sent: Sunday, October 14, 2007 7:18:19 AM
Subject: Re: Problem with -i ignore-file option in version 6.9 ptx in cygwin  environment

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Graig on 10/14/2007 7:51 AM:
> The message below generated an email thread amongst the gnu folks,

to which, I reiterate what I said in that thread:

> I maintain the cygwin port of coreutils.  Cygwin's philosophy is a bit
> different from some of the other ports to windows: when  using binary
> mounts, cygwin's goal is to behave like Linux.  Since ptx on Linux has the
> same behavior in treating \r literally, that is why I have made no effort
> for cygwin to behave any differently when you are using a cygwin binary
> mount.  Put another way, the fact that you use a binary mount on cygwin is
> an agreement on your part to use files that are binary-compatible with
> Linux (ie no \r line endings), and tools like d2u should be used to
> convert problem files on a cygwin binary mount.  On the other hand, you
> can use a cygwin text mount, which will ignore the \r with no
> recompilation required.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHEiUr84KuGfSFAYARArL0AJ9rl3IaBfKaPeiyo3MPnkAmyw5ZggCgw8ha
hkKSvZ/vLHlcWKwQumXjTsU=
=Xxwb
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/





--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]