Matthew Woehlke wrote:
In fact, it sounds like it might be a weird setup bug i.e.
an installed version that is no longer available messes up
the cycle. I would definitely try a setup snapshot and
checking the log as per Brian's advice (although I'm not
sure if the log will help since setup does
Matthew Woehlke wrote:
...the answer to your question is to first pick 'keep' and
then manually make any changes to things you do want to
install/upgrade.
That's what I've been doing. When I leave Keep selected,
clicking on CLISP's entry in the New column cycles between
Keep (my current
Matthew Woehlke wrote:
Hmm, ok, I was misunderstanding the problem then. You are
getting a new package list, right? (I.e. you are not
trying to install locally?)
Correct.
It's actually a bit different than the descriptions I gave
in my last couple messages:
If I leaved Curr selected, the
Dave Korn wrote:
I've tried a few mirrors (ftp.kr.freebsd.org,
ftp.mirrorservice.org, mirror.calvin.edu, and
mirrors.kernel.org) but the newest CLISP on all of them
is 2.41-1.
You may be doing something wrong: all those mirrors are
up-to-date, and according to the timestamps have been
since
Reini Urban wrote:
I've released a bugfix release clisp-2.41-2 for cygwin.
* changed default :line-terminator encoding from CRLF to
read and write default only LF, because of *TERMINAL-ENCODING*.
Bad for input, but needed for output.
Fixes clisp -i .clisprc test.lisp test.txt
See
Markus Hoenicka wrote:
maybe I'm being dense, but xargs does not seem to do what
it should:
xargs only calls the command (echo in this case) once, with
all the given arguments. (It will call it more than once
only if calling it once would be a too-long command line.)
If you want a command
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
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
Reini Urban wrote:
Confirmed.
Bug patched at
http://sourceforge.net/tracker/index.php?func=detailaid=1633552group_id=1355atid=101355
It's been moved to http://tinyurl.com/3b3yux with the
following comment from Sam Steingold:
This patch does not seem right.
on linux O_BINARY==0 and I see no
Reini Urban wrote:
Confirmed.
Bug patched at
http://sourceforge.net/tracker/index.php?func=detailaid=1633552group_id=1355atid=101355
Thanks!
--
Aaron
Beginning Lua Programming: http://www.amazon.com/gp/product/0470069171/
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
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*
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
12 matches
Mail list logo
