Re: Compile-time detection of EOL translation mode (CLISP)

Reini Urban wrote: For me [defined(WIN32)] is true during clisp compilation. I had to change the patch to fix the WIN32 section, not the UNIX one. I'll check which optional header defines WIN32. I did actually test it to make sure I wasn't misremembering it being false. I haven't found any of

Re: Compile-time detection of EOL translation mode (CLISP)

2007/1/30, Aaron Brown <[EMAIL PROTECTED]>: Reini Urban (quoting Sam Steingold at the issue tracker page [1]) wrote: > The original problem is best solved by a > (setq *default-file-encoding* :unix) > in ~/.clisprc.lisp As mentioned in an earlier post, that doesn't work for *standard-output*,

Re: Compile-time detection of EOL translation mode (CLISP)

Reini Urban (quoting Sam Steingold at the issue tracker page [1]) wrote: The original problem is best solved by a (setq *default-file-encoding* :unix) in ~/.clisprc.lisp As mentioned in an earlier post, that doesn't work for *standard-output*, presumably because it's already :dos before .cli

Re: Compile-time detection of EOL translation mode (CLISP)

Reini Urban schrieb: Aaron Brown schrieb: Reini Urban wrote: Confirmed. Bug patched at http://sourceforge.net/tracker/index.php?func=detail&aid=1633552&group_id=1355&atid=101355 It's been moved to with the following comment from Sam Steingold: This patch does

Re: Compile-time detection of EOL translation mode (CLISP)

Aaron Brown schrieb: Reini Urban wrote: Confirmed. Bug patched at http://sourceforge.net/tracker/index.php?func=detail&aid=1633552&group_id=1355&atid=101355 It's been moved to with the following comment from Sam Steingold: This patch does not seem right. on li

Re: Compile-time detection of EOL translation mode (CLISP)

Reini Urban wrote: Confirmed. Bug patched at http://sourceforge.net/tracker/index.php?func=detail&aid=1633552&group_id=1355&atid=101355 It's been moved to with the following comment from Sam Steingold: This patch does not seem right. on linux O_BINARY==0 and I se

Re: Compile-time detection of EOL translation mode (CLISP)

Reini Urban wrote: Confirmed. Bug patched at http://sourceforge.net/tracker/index.php?func=detail&aid=1633552&group_id=1355&atid=101355 Thanks! -- Aaron Beginning Lua Programming: http://www.amazon.com/gp/product/0470069171/ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple

Re: Compile-time detection of EOL translation mode (CLISP)

2007/1/9, Reini Urban <[EMAIL PROTECTED]>: defined(UNIX) && (O_BINARY != 0) seems to only target cygwin and looks like an upstream bug to me. If binary then do binary and not DOS. Thanks for the report! I'll check and update it then. Confirmed. Bug patched at http://sourceforge.net/tracker/in

Re: Compile-time detection of EOL translation mode (CLISP)

2007/1/4, Dave Korn <[EMAIL PROTECTED]>: On 04 January 2007 18:58, Aaron Brown wrote: > Dave Korn wrote: >> What is the /end/ result you're trying to achieve here? > > When CLISP does text output, it opens the file in binary > mode and does EOL translation itself, according to the > requested

RE: Compile-time detection of EOL translation mode (CLISP)

On 04 January 2007 18:58, Aaron Brown wrote: > Dave Korn wrote: >> What is the /end/ result you're trying to achieve here? > > When CLISP does text output, it opens the file in binary > mode and does EOL translation itself, according to the > requested line terminator mode. For instance, the f

Re: Compile-time detection of EOL translation mode (CLISP)

Dave Korn wrote: From within the C preprocessor, how do I find out whether a Cygwin installation is set to use dos or unix EOLs? You don't. Whatever you're trying to do, this is the wrong way to go about it. What is the /end/ result you're trying to achieve here? When CLISP does text

RE: Compile-time detection of EOL translation mode (CLISP)

On 04 January 2007 17:17, Aaron Brown wrote: > From within the C preprocessor, how do I find out whether a > Cygwin installation is set to use dos or unix EOLs? You don't. Whatever you're trying to do, this is the wrong way to go about it. For a start, the answer to the question "Is this in

Compile-time detection of EOL translation mode (CLISP)

From within the C preprocessor, how do I find out whether a Cygwin installation is set to use dos or unix EOLs? The reason I ask is this: I'm using version 2.41 as downloaded from a Cygwin mirror, and my *default-file-encoding* uses dos-style line terminators [1]> *default-file-encoding* #