I already ran make in the ncurses-cffi directory, but it seems that it's not the point... running make i get the ncurses.lisp and ncurses-cffi.lisp files, but loading with asdf says that thing anyway... I also tried to compile the lisp files manually, and reload with asdf but I just get the same error. Is it possible that it's a problem with common lisp controller?
On 10/22/06, Brad Beveridge brad.beveridge@gmail.com wrote:
On 22/10/06, Alessandro Piras laynor@gmail.com wrote:
Hi, i was trying to have a test run of vial, but when i load it with
(asdf:operate 'asdf:load-op 'vial)
it says
debugger invoked on a SB-INT:SIMPLE-FILE-ERROR in thread #<THREAD
"initial
thread" {A820561}>: The path
#P"/var/cache/common-lisp-controller/1000/sbcl/local/home/ale/src/vial/ncurses-cffi/ncurses.fasl"
does not exist.
I actually don't know what to do, should i manually compile ncurses.lisp file (the output of swig) and copy it to the that path? I guess there's a better way to do it, but don't know how :)
Hi Alessandro, please feel free to mail to the vial mailing list. If you have SWIG you can just run 'make' from the cffi directory. Or you can do another "darcs get", I've checked that file in - it should have been there from the start.
Cheers Brad
On 22/10/06, Alessandro Piras laynor@gmail.com wrote:
I already ran make in the ncurses-cffi directory, but it seems that it's not the point... running make i get the ncurses.lisp and ncurses-cffi.lisp files, but loading with asdf says that thing anyway... I also tried to compile the lisp files manually, and reload with asdf but I just get the same error. Is it possible that it's a problem with common lisp controller?
Hmm, I don't use common lisp controller - that could be the issue. The path looks a little strange, as if you have installed Vial under the common lisp controller directory? I also just use (require 'vial) on SBCL to load the asdf file.
I just looked at CL controller, I am pretty sure that is the issue. I'm afraid that you'll have to figure that one out without me - I manually install the packages that I need and then symlink the ASDF file to ~/.sbcl/systems/
Let me know how you get on, sorry I couldn't help more.
Cheers Brad
I managed to make it compile, and it seems it was a system definition problem. I attach here the fixed file, the fixes are documented through comments, just search for FIX and MOVED :)
Now I have another problem. when i run vial (with *(v**ial:vial)*), the editor opens, but when i try to write something it prints out (lots of) garbage, that seems something like the interpreter's output. Example garbage is shown in the other attached file, garbage.txt Let me know if it's somewhat "forbidden" to send attachments here, and how to send (supposed to be) fixes and patches :) __ Alessandro __ Alessandro
On 10/22/06, Brad Beveridge < brad.beveridge@gmail.com> wrote:
On 22/10/06, Alessandro Piras laynor@gmail.com wrote:
I already ran make in the ncurses-cffi directory, but it seems that it's not the point... running make i get the ncurses.lisp and ncurses-cffi.lisp files, but
loading
with asdf says that thing anyway... I also tried to compile the lisp files
manually,
and reload with asdf but I just get the same error. Is it possible that it's a
problem
with common lisp controller?
Hmm, I don't use common lisp controller - that could be the issue. The path looks a little strange, as if you have installed Vial under the common lisp controller directory? I also just use (require 'vial) on SBCL to load the asdf file.
I just looked at CL controller, I am pretty sure that is the issue. I'm afraid that you'll have to figure that one out without me - I manually install the packages that I need and then symlink the ASDF file to ~/.sbcl/systems/
Let me know how you get on, sorry I couldn't help more.
Cheers Brad _______________________________________________ vial-devel mailing list vial-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/vial-devel
On 22/10/06, Alessandro Piras laynor@gmail.com wrote:
I managed to make it compile, and it seems it was a system definition problem. I attach here the fixed file, the fixes are documented through comments, just search for FIX and MOVED :)
Now I have another problem. when i run vial (with (vial:vial)), the editor opens, but when i try to write something it prints out (lots of) garbage, that seems something like the interpreter's output. Example garbage is shown in the other attached file, garbage.txt Let me know if it's somewhat "forbidden" to send attachments here, and how to send (supposed to be) fixes and patches :)
Ah. The output is debugging that goes to out *standard-output*. I have developed Vial using Slime and Emacs as a debugger. Slime rebinds the standard output and error streams, so for me that output appears in Slime. I would suggest that for right now developing by using Slime as a REPL and debugger is probably a good idea. Otherwise, you can rebind those streams (to NIL?) so that they don't output to the screen.
Also, I appear to have a bug - the very first time that Vial runs the screen doesn't refresh until a key is pressed. I haven't figured out why that is yet :)
Thanks for the updated vial.asd - I'm also a noob with ASDF, so for right now I'm not worried about doing it "right", just that it works.
I don't mind patches and files being sent here as attachments, but I would prefer that patches are created with darcs and are attached with a commit comment. I've not used darcs over email that much, but it should work pretty well.
Also, if you wouldn't mind posting at the bottom when you reply I would appreciate it :)
Cheers Brad
On 10/23/06, Brad Beveridge brad.beveridge@gmail.com wrote:
Ah. The output is debugging that goes to out *standard-output*. I have developed Vial using Slime and Emacs as a debugger. Slime rebinds the standard output and error streams, so for me that output appears in Slime. I would suggest that for right now developing by using Slime as a REPL and debugger is probably a good idea. Otherwise, you can rebind those streams (to NIL?) so that they don't output to the screen.
Also, I appear to have a bug - the very first time that Vial runs the screen doesn't refresh until a key is pressed. I haven't figured out why that is yet :)
Thanks for the updated vial.asd - I'm also a noob with ASDF, so for right now I'm not worried about doing it "right", just that it works.
I don't mind patches and files being sent here as attachments, but I would prefer that patches are created with darcs and are attached with a commit comment. I've not used darcs over email that much, but it should work pretty well.
Also, if you wouldn't mind posting at the bottom when you reply I would appreciate it :)
Cheers Brad _______________________________________________ vial-devel mailing list vial-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/vial-devel
No problems about posting at the bottom, I didn't try it in emacs because i was just doing a test run and the repl was fine enough for it :) I'm an ASDF noob too, so we're in the same boat! I'll have a look at darcs to see how it works, 'cause I'm a darcs noob too, I just used it for my home directory and configuration files. Anyway, i'm just pleased for how fast you answer. __ Alessandro
On 22/10/06, Alessandro Piras laynor@gmail.com wrote:
On 10/23/06, Brad Beveridge brad.beveridge@gmail.com wrote:
Ah. The output is debugging that goes to out *standard-output*. I have developed Vial using Slime and Emacs as a debugger. Slime rebinds the standard output and error streams, so for me that output appears in Slime. I would suggest that for right now developing by using Slime as a REPL and debugger is probably a good idea. Otherwise, you can rebind those streams (to NIL?) so that they don't output to the screen.
Also, I appear to have a bug - the very first time that Vial runs the screen doesn't refresh until a key is pressed. I haven't figured out why that is yet :)
Thanks for the updated vial.asd - I'm also a noob with ASDF, so for right now I'm not worried about doing it "right", just that it works.
I don't mind patches and files being sent here as attachments, but I would prefer that patches are created with darcs and are attached with a commit comment. I've not used darcs over email that much, but it should work pretty well.
Also, if you wouldn't mind posting at the bottom when you reply I would appreciate it :)
Cheers Brad _______________________________________________ vial-devel mailing list vial-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/vial-devel
No problems about posting at the bottom, I didn't try it in emacs because i was just doing a test run and the repl was fine enough for it :) I'm an ASDF noob too, so we're in the same boat! I'll have a look at darcs to see how it works, 'cause I'm a darcs noob too, I just used it for my home directory and configuration files. Anyway, i'm just pleased for how fast you answer.
No problems, it's the weekend & I'm happy to have somebody else about. I'm going to start an IRC channel, #vial.
Cheers Brad
On 10/23/06, Brad Beveridge brad.beveridge@gmail.com wrote:
No problems, it's the weekend & I'm happy to have somebody else about. I'm going to start an IRC channel, #vial.
Cheers Brad _______________________________________________ vial-devel mailing list vial-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/vial-devel
In which server? freenode? Anyway, i forgot to ask you how to start vial from emacs/slime. Of course it doesn't open a terminal window automatically... So how to start it and try it using emacs/slime?
On 22/10/06, Alessandro Piras laynor@gmail.com wrote:
On 10/23/06, Brad Beveridge brad.beveridge@gmail.com wrote:
No problems, it's the weekend & I'm happy to have somebody else about. I'm going to start an IRC channel, #vial.
Cheers Brad _______________________________________________ vial-devel mailing list vial-devel@common-lisp.net
http://common-lisp.net/cgi-bin/mailman/listinfo/vial-devel
In which server? freenode? Anyway, i forgot to ask you how to start vial from emacs/slime. Of course it doesn't open a terminal window automatically... So how to start it and try it using emacs/slime?
Yes, freenode. My .sbclrc file has the lines (require 'swank) (swank:create-swank-server 4005)
I then start SBCL from the console as usual, and connect to it from Slime with Meta-x slime-connect.
Cheers Brad
-
Alessandro Piras -
Brad Beveridge