Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error_running_doclog. #5

Open
triska opened this issue Feb 22, 2024 · 5 comments
Open

error_running_doclog. #5

triska opened this issue Feb 22, 2024 · 5 comments

Comments

@triska
Copy link

triska commented Feb 22, 2024

I followed the steps in the documentation, and also adjusted the configuration file, and now I get:

$ bash doclog.sh scryer.config.pl 
doclog(1,1,0).
error_running_doclog.
@aarroyoc
Copy link
Owner

The output folder must not exist (make clean). Also, check if you have the latest dependencies (make setup).

@triska
Copy link
Author

triska commented Feb 23, 2024

I have done make setup, and no output folder exists yet, and I still get the same problem. This is from a freshly cloned repository. May I suggest emitting more information about why an error arises? Could an exception be shown? Thank you a lot!

@triska
Copy link
Author

triska commented Feb 24, 2024

I think one reason is that I have temporary files in the lib directory, these are created by Emacs when editing files:

all:user:path_segments(A,[[],"home","markus","scryer-prolog","src","lib",".","a.pl~"]).
exit:user:path_segments("/home/markus/scryer-prolog/src/lib/./a.pl~",[[],"home","markus","scryer-prolog","src","lib",".","a.pl~"]).
call:user:directory_exists("/home/markus/scryer-prolog/src/lib/./a.pl~").

@triska
Copy link
Author

triska commented Feb 24, 2024

The same issue for the .ediprolog file that exists in the library path:

call:user:directory_exists("/home/markus/scryer-prolog/src/lib/./.ediprolog").

Maybe doclog can be made more robust against such files? I think it cauld suffice to process only *.pl files.

@aarroyoc
Copy link
Owner

Yes, those are good points. File handling in DocLog was an afterthought and it can be improved a lot. I'll keep this issue open until I fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants