[armedbear-devel] Filename errors in Windows
Hi, I just started with ABCL using the J editor on WinXP SP3. I replaced the ABCL jar in the J lib with the latest 0.23.1, but also in the old version ABCL 0.19 I had the same errors. I am able to create and save a very simple lisp file. However, when I use the menu function: Mode | Compile and load file I get this: [1] CL-USER(3): ;;; Compiling and loading D:\src\lisp\plus.lisp ... #<THREAD "JLisp interpreter" {FD5428}>: Debugger invoked on condition of type FILE-ERROR The file "D:/src/lisp/srclispplus.lisp" does not exist. It seems that somewhere under the hood the filename gets corrupted. Trying to change the name using double backslashes in the text box above the source file does have no effect. Can I change this behaviour? Thx, Arie
On Jan 16, 2011, at 10:21 PM, Arie van Wingerden wrote:
Hi, I just started with ABCL using the J editor on WinXP SP3.
I replaced the ABCL jar in the J lib with the latest 0.23.1, but also in the old version ABCL 0.19 I had the same errors.
I am able to create and save a very simple lisp file. However, when I use the menu function: Mode | Compile and load file I get this:
[1] CL-USER(3): ;;; Compiling and loading D:\src\lisp\plus.lisp ... #<THREAD "JLisp interpreter" {FD5428}>: Debugger invoked on condition of type FILE-ERROR The file "D:/src/lisp/srclispplus.lisp" does not exist.
It seems that somewhere under the hood the filename gets corrupted. Trying to change the name using double backslashes in the text box above the source file does have no effect.
Can I change this behaviour?
From your report, it seems likely that you are encountering problems stemming from the use of forward slash as the PATHNAME separator on all platforms in [abcl-0.21][1] (N.B. strings with backslash characters are normalized by the PATHNAME routines to forward slashes so such input should be fine). What is odd about your report, is that abcl-0.19 does not have this "all slashes become forward slashes" behavior, so it should not produce the same kind of error. Unfortunately, ABCL development was split off from J quite some time ago (three years?). Wethe ABCL developers on armedbear-developdo not actively test with the J source tree, nor do we make the J releases. If there are J developers out there who wish help bringing the integrated ABCL release forward to solve this issue, we would be more than happy to assist by debugging/modifying our side. [1] http://trac.common-lisp.net/armedbear/changeset/12798 -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
Hi Mark, what a pity! I really think the combination of J and ABCL is a superb platform for Common Lisp development. Alas I do not like Emacs and J is like a fresh breeze. I'd very much like this issue to be fixed by somebody in the know. Thx for the prompt and to the point response! Regards, Arie 2011/1/17 Mark Evenson <evenson@panix.com>
On Jan 16, 2011, at 10:21 PM, Arie van Wingerden wrote:
Hi, I just started with ABCL using the J editor on WinXP SP3.
I replaced the ABCL jar in the J lib with the latest 0.23.1, but also in the old version ABCL 0.19 I had the same errors.
I am able to create and save a very simple lisp file. However, when I use the menu function: Mode | Compile and load file I get this:
[1] CL-USER(3): ;;; Compiling and loading D:\src\lisp\plus.lisp ... #<THREAD "JLisp interpreter" {FD5428}>: Debugger invoked on condition of type FILE-ERROR The file "D:/src/lisp/srclispplus.lisp" does not exist.
It seems that somewhere under the hood the filename gets corrupted. Trying to change the name using double backslashes in the text box above the source file does have no effect.
Can I change this behaviour?
From your report, it seems likely that you are encountering problems stemming from the use of forward slash as the PATHNAME separator on all platforms in [abcl-0.21][1] (N.B. strings with backslash characters are normalized by the PATHNAME routines to forward slashes so such input should be fine). What is odd about your report, is that abcl-0.19 does not have this "all slashes become forward slashes" behavior, so it should not produce the same kind of error.
Unfortunately, ABCL development was split off from J quite some time ago (three years?). Wethe ABCL developers on armedbear-developdo not actively test with the J source tree, nor do we make the J releases. If there are J developers out there who wish help bringing the integrated ABCL release forward to solve this issue, we would be more than happy to assist by debugging/modifying our side.
[1] http://trac.common-lisp.net/armedbear/changeset/12798
-- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
Hi Arie, I occasionally produce new builds of J when there is a new version of ABCL. When the ABCL pathname change appeared, I fixed it up so that J would build again, but didn't test much as you have found out. I'd love to get some help with the lisp side of things in J. For example, the slime integration doesn't work and I've disabled the command. I'll take a look at the path issue in J and see if I can unblock you. Also, for J issues we still use the old sourceforge users<http://sourceforge.net/mailarchive/forum.php?forum_name=armedbear-j-users>and dev<http://sourceforge.net/mailarchive/forum.php?forum_name=armedbear-j-devel>mailing lists. Kevin On Mon, Jan 17, 2011 at 2:36 AM, Arie van Wingerden <xapwing@gmail.com>wrote:
Hi Mark,
what a pity! I really think the combination of J and ABCL is a superb platform for Common Lisp development. Alas I do not like Emacs and J is like a fresh breeze.
I'd very much like this issue to be fixed by somebody in the know.
Thx for the prompt and to the point response!
Regards, Arie
2011/1/17 Mark Evenson <evenson@panix.com>
On Jan 16, 2011, at 10:21 PM, Arie van Wingerden wrote:
Hi, I just started with ABCL using the J editor on WinXP SP3.
I replaced the ABCL jar in the J lib with the latest 0.23.1, but also in the old version ABCL 0.19 I had the same errors.
I am able to create and save a very simple lisp file. However, when I use the menu function: Mode | Compile and load file I get this:
[1] CL-USER(3): ;;; Compiling and loading D:\src\lisp\plus.lisp ... #<THREAD "JLisp interpreter" {FD5428}>: Debugger invoked on condition of type FILE-ERROR The file "D:/src/lisp/srclispplus.lisp" does not exist.
It seems that somewhere under the hood the filename gets corrupted. Trying to change the name using double backslashes in the text box above the source file does have no effect.
Can I change this behaviour?
From your report, it seems likely that you are encountering problems stemming from the use of forward slash as the PATHNAME separator on all platforms in [abcl-0.21][1] (N.B. strings with backslash characters are normalized by the PATHNAME routines to forward slashes so such input should be fine). What is odd about your report, is that abcl-0.19 does not have this "all slashes become forward slashes" behavior, so it should not produce the same kind of error.
Unfortunately, ABCL development was split off from J quite some time ago (three years?). Wethe ABCL developers on armedbear-developdo not actively test with the J source tree, nor do we make the J releases. If there are J developers out there who wish help bringing the integrated ABCL release forward to solve this issue, we would be more than happy to assist by debugging/modifying our side.
[1] http://trac.common-lisp.net/armedbear/changeset/12798
-- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
_______________________________________________ armedbear-devel mailing list armedbear-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
Hi Kevin, thanks you are willing to help. Please let me now what's happening ;-) Kind regards, Arie 2011/1/18 Kevin Krouse <kevin.krouse@gmail.com>
Hi Arie,
I occasionally produce new builds of J when there is a new version of ABCL. When the ABCL pathname change appeared, I fixed it up so that J would build again, but didn't test much as you have found out. I'd love to get some help with the lisp side of things in J. For example, the slime integration doesn't work and I've disabled the command.
I'll take a look at the path issue in J and see if I can unblock you. Also, for J issues we still use the old sourceforge users<http://sourceforge.net/mailarchive/forum.php?forum_name=armedbear-j-users>and dev<http://sourceforge.net/mailarchive/forum.php?forum_name=armedbear-j-devel>mailing lists.
Kevin
On Mon, Jan 17, 2011 at 2:36 AM, Arie van Wingerden <xapwing@gmail.com>wrote:
Hi Mark,
what a pity! I really think the combination of J and ABCL is a superb platform for Common Lisp development. Alas I do not like Emacs and J is like a fresh breeze.
I'd very much like this issue to be fixed by somebody in the know.
Thx for the prompt and to the point response!
Regards, Arie
2011/1/17 Mark Evenson <evenson@panix.com>
On Jan 16, 2011, at 10:21 PM, Arie van Wingerden wrote:
Hi, I just started with ABCL using the J editor on WinXP SP3.
I replaced the ABCL jar in the J lib with the latest 0.23.1, but also in the old version ABCL 0.19 I had the same errors.
I am able to create and save a very simple lisp file. However, when I use the menu function: Mode | Compile and load file I get this:
[1] CL-USER(3): ;;; Compiling and loading D:\src\lisp\plus.lisp ... #<THREAD "JLisp interpreter" {FD5428}>: Debugger invoked on condition of type FILE-ERROR The file "D:/src/lisp/srclispplus.lisp" does not exist.
It seems that somewhere under the hood the filename gets corrupted. Trying to change the name using double backslashes in the text box above the source file does have no effect.
Can I change this behaviour?
From your report, it seems likely that you are encountering problems stemming from the use of forward slash as the PATHNAME separator on all platforms in [abcl-0.21][1] (N.B. strings with backslash characters are normalized by the PATHNAME routines to forward slashes so such input should be fine). What is odd about your report, is that abcl-0.19 does not have this "all slashes become forward slashes" behavior, so it should not produce the same kind of error.
Unfortunately, ABCL development was split off from J quite some time ago (three years?). Wethe ABCL developers on armedbear-developdo not actively test with the J source tree, nor do we make the J releases. If there are J developers out there who wish help bringing the integrated ABCL release forward to solve this issue, we would be more than happy to assist by debugging/modifying our side.
[1] http://trac.common-lisp.net/armedbear/changeset/12798
-- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
_______________________________________________ armedbear-devel mailing list armedbear-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/armedbear-devel
On 1/18/11 6:04 PM, Kevin Krouse wrote:
Hi Arie,
I occasionally produce new builds of J when there is a new version of ABCL. When the ABCL pathname change appeared, I fixed it up so that J would build again, but didn't test much as you have found out. I'd love to get some help with the lisp side of things in J. For example, the slime integration doesn't work and I've disabled the command.
I'll take a look at the path issue in J and see if I can unblock you. Also, for J issues we still use the old sourceforge users <http://sourceforge.net/mailarchive/forum.php?forum_name=armedbear-j-users
and dev <http://sourceforge.net/mailarchive/forum.php?forum_name=armedbear-j-devel> mailing lists.
[…] Most of the armedbear developers are probably still subscribed to the armedbear-j-devel list (I know I am), so we should be able to help quickly with any Lisp-side issues published there. As a group, the ABCL developers are very grateful to have been "birthed" from J, so are more than willing to ensure that J will continue to work smoothly with ABCL (or provide some migration mechanism). That being said, I'll try to get around to building J with the latest ABCL in the next week, to see if there is anything obvious that I can help with. It is real nice to see that J has maintained its community! -- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
I did a little debugging this weekend and the issue came from the command sent to the external abcl process. The path separators wren't backslash escaped. So the command: (CL:COMPILE-FILE "D:\src\lisp\plus.lisp") will fail, while either one of the following will succeed: (CL:COMPILE-FILE "D:\\src\\lisp\\plus.lisp") (CL:COMPILE-FILE "D:/src/lisp/plus.lisp") I've committed r11339 to J's svn trunk that should fix the issue for you. Please give it a try and let me know if it works. Thanks, Kevin On Tue, Jan 18, 2011 at 12:33 PM, Mark Evenson <evenson@panix.com> wrote:
On 1/18/11 6:04 PM, Kevin Krouse wrote:
Hi Arie,
I occasionally produce new builds of J when there is a new version of ABCL. When the ABCL pathname change appeared, I fixed it up so that J would build again, but didn't test much as you have found out. I'd love to get some help with the lisp side of things in J. For example, the slime integration doesn't work and I've disabled the command.
I'll take a look at the path issue in J and see if I can unblock you. Also, for J issues we still use the old sourceforge users < http://sourceforge.net/mailarchive/forum.php?forum_name=armedbear-j-users
and dev < http://sourceforge.net/mailarchive/forum.php?forum_name=armedbear-j-devel
mailing lists.
[…]
Most of the armedbear developers are probably still subscribed to the armedbear-j-devel list (I know I am), so we should be able to help quickly with any Lisp-side issues published there. As a group, the ABCL developers are very grateful to have been "birthed" from J, so are more than willing to ensure that J will continue to work smoothly with ABCL (or provide some migration mechanism).
That being said, I'll try to get around to building J with the latest ABCL in the next week, to see if there is anything obvious that I can help with. It is real nice to see that J has maintained its community!
-- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
Hi Kevin, thanks for your help! Since I am not really a Java guy and am running Windows XP the whole build process is quite alien to me. However, I managed to download the trunk with SVN and built the classes using ANT. After that point I got stuck, since no j.jar had been generated. I built a j.jar myself using this Windows CMD file: set cp=D:\downloads\Programming\ABCL Armed Bear Common Lisp\J-Editor\armedbear-j\trunk\j\build\classes jar cf d:/work/j.jar Main.class "%cp%" Using cvf instead of cf didn't solve the problem. When I run the jar it complains however that no manifest could be found. For you this is maybe an obvious thing. Could you point me to a solution, or, for me even better ;-), could you generate a correct j.jar for me? Thx again. Arie 2011/1/23 Kevin Krouse <kevin.krouse@gmail.com>
I did a little debugging this weekend and the issue came from the command sent to the external abcl process. The path separators wren't backslash escaped. So the command:
(CL:COMPILE-FILE "D:\src\lisp\plus.lisp")
will fail, while either one of the following will succeed:
(CL:COMPILE-FILE "D:\\src\\lisp\\plus.lisp") (CL:COMPILE-FILE "D:/src/lisp/plus.lisp")
I've committed r11339 to J's svn trunk that should fix the issue for you. Please give it a try and let me know if it works.
Thanks, Kevin
On Tue, Jan 18, 2011 at 12:33 PM, Mark Evenson <evenson@panix.com> wrote:
On 1/18/11 6:04 PM, Kevin Krouse wrote:
Hi Arie,
I occasionally produce new builds of J when there is a new version of ABCL. When the ABCL pathname change appeared, I fixed it up so that J would build again, but didn't test much as you have found out. I'd love to get some help with the lisp side of things in J. For example, the slime integration doesn't work and I've disabled the command.
I'll take a look at the path issue in J and see if I can unblock you. Also, for J issues we still use the old sourceforge users < http://sourceforge.net/mailarchive/forum.php?forum_name=armedbear-j-users
and dev < http://sourceforge.net/mailarchive/forum.php?forum_name=armedbear-j-devel
mailing lists.
[…]
Most of the armedbear developers are probably still subscribed to the armedbear-j-devel list (I know I am), so we should be able to help quickly with any Lisp-side issues published there. As a group, the ABCL developers are very grateful to have been "birthed" from J, so are more than willing to ensure that J will continue to work smoothly with ABCL (or provide some migration mechanism).
That being said, I'll try to get around to building J with the latest ABCL in the next week, to see if there is anything obvious that I can help with. It is real nice to see that J has maintained its community!
-- "A screaming comes across the sky. It has happened before, but there is nothing to compare to it now."
Hi Arie, I was hoping to get a new build out to you, but I don't think I'll be able to for a few weeks. In the mean time, you can produce a new j.jar by running "ant dist" from the command line. That will package up the build and docs together under a 'dist' directory. Kevin On Mon, 24 Jan 2011 04:26:22 -0800, Arie van Wingerden <xapwing@gmail.com> wrote:
Hi Kevin,
thanks for your help! Since I am not really a Java guy and am running Windows XP the whole build process is quite alien to me. However, I managed to download the trunk with SVN and built the classes using ANT.
After that point I got stuck, since no j.jar had been generated. I built a j.jar myself using this Windows CMD file: set cp=D:\downloads\Programming\ABCL Armed Bear Common Lisp\J-Editor\armedbear-j\trunk\j\build\classes jar cf d:/work/j.jar Main.class "%cp%"
Using cvf instead of cf didn't solve the problem.
When I run the jar it complains however that no manifest could be found. For you this is maybe an obvious thing. Could you point me to a solution, or, for me even better ;-), could you generate a correct j.jar for me?
Thx again. Arie
participants (3)
-
Arie van Wingerden -
Kevin Krouse -
Mark Evenson