Activity for CLISP - an ANSI Common Lisp
-
Bruno Haible modified ticket #751
princ prints extra newlines
-
This is a consequence of *PRINT-PRETTY* and *PPRINT-FIRST-NEWLINE* being true. Documented at https://clisp.sourceforge.io/impnotes.html#ppr-first-newline . Not a bug.
-
Mariano Montone created ticket #751
princ prints extra newlines
-
Bernhard M. Wiedemann created ticket #59
timestamps beyond 2036 do not work
-
Erik Auerswald posted a comment on ticket #748
I have further explored the man page generation rabbit hole, and attached two fresh patches against current HEAD in the GitLab git repository. The XML source seems not to be used by the normal build scripts. Thus modifying doc/_clisp.1 seems closest to the practical source of the man page. The attached patch clisp-gitlab-manpage-formatting-fix-via-_clisp.1.patch against current GitLab HEAD does this for both current instances of the problem. But since the doc/_clisp.1 file seems to be generated from...
-
I have also opened a bug report regarding this issue at Ubuntu, because I originally encountered the issue with CLISP packaged in Ubuntu 20.04: https://bugs.launchpad.net/bugs/2022970
-
I agree with at least the first part of your example: NCONC should validate that its arguments except the last one are lists. MAPCAN and MAPCON should check the intermediate results accordingly.
-
Alexander Fedorov created ticket #750
MAPCAN/MAPCON Edge cases
-
Florian Weimer posted a comment on ticket #749
Thanks for the hint, moved: https://gitlab.com/gnu-clisp/clisp/-/issues/42
-
Hi Florian, I am not involved with the CLISP project, but it seems to me as if the project has switched to GitLab. It seems as if they imported issues from this tracker there at some point in time in the past (see https://gitlab.com/gnu-clisp/clisp/-/issues). The clisp.org (redirected to https://clisp.sourceforge.io/) and https://www.gnu.org/software/clisp/ sites still direct bug reporters here, to the SourceForge bug tracker. I do not see much activity here in the SourceForge project, but the GitLab...
-
CL_MACH_VM configure check will fail with future compilers
-
Well, I have looked at the wrong repository, i.e., the one at SourceForge instead of the one at GitLab. The problem is still there, but the affected line in doc/_clisp.1 is 438, not 434. Thus the fix would be sed -i '438s/:\.PP/:\n.PP/' doc/_clisp.1 for the generated man page, and possibly sed -i '316s/:/:\n /' doc/clisp.xml.in for the XML source for (among other formats) the man page (same line as in SourceForge Mercurial repository). Since the generated doc/_clisp.1 man page is checked into the...
-
Going deeper down this rabbit hole…: doc/man.xsl seems to be the style sheet entry point this reference http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl that file invokes further XSL stuff, somewhere within must be defined how to write man macros, including .PP One might assume that the docbook transformation to man page format should ensure that formatting directives that need to be preceded by a newline are actually preceded by a newline. Thus one might assume that there...
-
OK, I think I found the problematic file: doc/clisp.xml.in. Comparing the domain encoding and on error sections it seems to me as if a newline should be inserted in front of <variablelist>: sed -i '316s/:/:\n /' doc/clisp.xml.in The attached patch shows the results of above command. Please note that I did not test this and thus do not know if it really fixes the issue. I have not yet attempted to build the clisp sources….
-
I have created the attached patch via sed -i '434s/:\.PP/:\n.PP/' doc/_clisp.1 followed by hg diff.
-
Well, it seems as if the file doc/_clisp.1 might be generated via XSLT transformations, but I have not yet found the source, nor have I found the relevant style sheet. The root cause for the issue might be found in either of them, or at least a workaround would likely pertain to the man page source or the style sheet. If I were told (e.g., via ticket comment) where to find those and how to generate just the doc/_clisp.1 file, I would be happy to look into finding a solution.
-
While the above sed command works in the current case, the . in the pattern should have been escaped: sed -i '434s/:\.PP/:\n.PP/' doc/_clisp.1
-
docs: formatting error in man page: missing newline before macro (with fix)
-
ChristophK modified a comment on discussion Help
Actually I was expecting that I'd get a hex number with lower case hex digits when specifying the following format: (format out "_pnames=0x~x;~." *pnames* ) _pnames=0x80B9; But actually I'm getting upper-case 'B' instead of 'b'. Am I overlooking something?
-
Actually I was expecting that I'd get a hex number with lower case hex digits when specifying the following format: (format out "_pnames=0x~x;~." *pnames* ) _pnames=0x80B9; But actually I'm getting upper-case 'B' instead of 'b'. Am I overlooking something?
-
Actually I was expecting that I'd get a hex number with lower case hex digits when specifying the following format: (format out "_pnames=0x~x;~." *pnames* ) _pnames=0x80B9; But actually I'm getting upper-case 'B' instead of 'b'. Am I overlooking something?
-
Sam Steingold modified a comment on ticket #747
I agree with the analysis in the debian bug by Dennis Filder: In a test suite you usually can since it is probably not supposed to be run by a privileged user in such a way that it fails. Build servers and CI pipelines, which are almost always involved in exposing such bugs, really ought to put in more effort to make their environment more similar to the one the developer develops and tests the code in instead of silently expecting everyone else to put in the additional effort to placate them. I...
-
I agree with the analysis in the debian bug by Dennis Filder: In a test suite you usually can since it is probably not supposed to be run by a privileged user in such a way that it fails. Build servers and CI pipelines, which are almost always involved in exposing such bugs, really ought to put in more effort to make their environment more similar to the one the developer develops and tests the code in instead of silently expecting everyone else to put in the additional effort to placate them. I...
-
Roberto Avanzi posted a comment on ticket #742
More recent versions compile nicely - just check them out. Furthermore, if you add # Mac OS X/arm64 darwin*--arm64) XCFLAGS="$XCFLAGS -DNO_ASM" ;; to src/makemake.in (for instance, just after the corresponding block for Mac OS X/x86_64) then it compiles even with generational garbage collection (if you have a proper libsigsev installed)! It passes all tests except some socket related ones which are known to give problems under macOS anyway also with intel CPUs. Roberto
-
Ariel D'Alessandro created ticket #747
tests/streams: Failing test on pipe stdout file descriptor
-
Is Apple Silicon support for clisp worked on?
-
Pascal J. Bourguignon created ticket #746
Confusing error message: "*PATHNAME_ENCODING* on this platform can only be ~S"
-
Leo posted a comment on discussion Help
How is it possible that (- 305 295.3) returns 9.700012, instead of 9.7? This is a huge error in a super simple arithmetic operation. Any workarounds? I'm using v, 2.49
-
Rafael Sorkin posted a comment on ticket #744
Is there some way to edit the bug report above? I just wanted to neaten it up in a couple of places. Thanks!
-
Didier Verna created ticket #745
Command-line arguments processing problems
-
wrong answers from `expt' for certain arguments
-
Install of CLISP 2.49, deletes Windows 10 Path Statement.
-
Thank you for the details. Someone else had the same problem on 2019-12-12 and gave this comment: "WARNING: The default installation will wipe out your PATH variable. " I have therefore removed the .exe-format installers from the download directory. Windows users can still use the clisp-2.49-win32-mingw-small.zip and clisp-2.49-win32-mingw-big.zip files. I have also added a note about this bug in the development sources.
-
Thomas Cubbins posted a comment on ticket #8
Hello Bruno Haible, Thank you for your follow up. Sorry for the delay I had a class this afternoon. Yes, it was a surprise to find my system path replaced with an address of clisp. Here are some screen prints below to provide an outline of what happened. For myself, I plan on just using my User Path statement to rebuild, System Path statement. That is the fix. I am contacting you, because I think you need to check your install procedure. Once that is done, the matter is closed. I will fix the changes...
-
Hello Bruno Haible, Thank you for your follow up. Sorry for the delay I had a class this afternoon. Yes, it was a surprise to find my system path replaced with an address of clisp. Here are some screen prints below to provide an outline of what happened. For myself, I plan on just using my User Path statement to rebuild, System Path statement. That is the fix. I am contacting you, because I think you need to check your install procedure. Once that is done, the matter is closed. I will fix the changes...
-
1) Where do you downloaded the CLISP installer from? 2) About your Windows installation: What version is it (32-bit or 64-bit Windows)? 3) Did you see the "deleted" PATH environment variable in the Control Panel? 4) Did you see the "deleted" PATH environment variable in a cmd.exe window? 5) Did you see the "deleted" PATH environment variable through a clisp command (getenv "PATH") ?
-
This is a duplicate of https://sourceforge.net/p/clisp/support-requests/8/.
-
Install of CIisp 2.49, deletes entire Windows 10, Path Statement
-
Install of CLisp 2.49, deletes entire Windows Path Statement
-
This is a duplicate of https://sourceforge.net/p/clisp/support-requests/8/.
-
Install of CLisp 2.49, deletes entire Windows Path Statement
-
Install of CIisp 2.49, deletes entire Windows 10, Path Statement
-
Install of CLISP 2.49, deletes Windows 10 Path Statement.
-
FX created ticket #742
Build failure on macOS Apple Silicon
-
What would I best refer to when it comes to a full comprehensive language reference? Can I still use Steeles Book "Common Lisp"?
-
I thought that too, in the first place, but it gives (Windows 8.1) : module ’syscalls’ requires package POSIX On the Windows 10 system the latest clisp gives: C:\Projekte\forth>\clisp\clisp --version GNU CLISP 2.49 (2010-07-07) (built on STSst063.jenty.by [150.0.0.63]) Software: GNU-C 3.4.5 (mingw-vista special r3) gcc -mno-cygwin -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4...
-
clisp --version
-
Found that I had to invoke C:\clisp\full\lisp.exe instead.
-
I installed the most recent version (2.49) under Windows 8.1 and got an error when invoking clisp with the following command line: C:\Projekte>c:\clisp\clisp.exe -B "C:/clisp/" -M "C:\clisp\/full/lispinit.mem" "myapp.lisp" 1>myapp.txt C:/clisp//base/lisp.exe: initialization file `C:\clisp\/full/lispinit.mem' was not created by this version of CLISP runtime
-
I installed the most recent version (2.49) under WIndows 8.1 and got an error when invoking clisp with the following command line: C:\Projekte>c:\clisp\clisp.exe -B "C:/clisp/" -M "C:\clisp\/full/lispinit.mem" "myapp.lisp" 1>myapp.txt C:/clisp//base/lisp.exe: initialization file `C:\clisp\/full/lispinit.mem' was not created by this version of CLISP runtime
-
Hi, I'm new to Clisp. How can I find out the version of Clisp that is installed?
-
Until someone has reproduced, investigated, and fixed the two issues, your best bet is 1. to use the HEAD of either the master branch or the clisp-2.50 branch at https://gitlab.com/gnu-clisp/clisp , 2. use "make -f Makefile.devel build-porting64-gcc-portability". This is the least optimized variant. You can try out multiple variants through "build-porting64-gcc-portability multibuild-porting64-gcc".
-
Joern Clausen created ticket #57
Solaris 11/sparc 64bit
-
supmener posted a comment on ticket #56
Earned at ConEmu
-
Clipboard in Windows XP Home Russian 32 bits
-
Alex P created ticket #55
Hyperspec error with (describe 'x) - HTTPS protocol is not supported yet
-
http-->https
-
See also issue https://www.cliki.net/Issue%20LOOP-FINALLY-VARIABLES.
-
make makemake work on macOS
-
Thanks for the report. Fixed.
-
CLISP fails ANSI-TEST LOOP.1.40
-
There are two more related cases: > (loop for i from 1 to 5 finally (return i)) 6 > (loop for i from 1 upto 5 finally (return i)) 6 > (loop for i from 1 below 6 finally (return i)) 6 ANSI CL 6.1.2.1.1 http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/sec_6-1-2-1-1.html says: "The variable var is bound to the value of form1 in the first iteration and is stepped[1] by the value of form3 in each succeeding iteration, or by 1 if form3 is not provided." Therefore here, the variable I is...
-
Roland Illig posted a comment on ticket #740
Ah, stupid SourceForge text formatter. The URL https://mail-index.netbsd.org/pkgsrc-users/2019/11/02/msg029846.html was not supposed to end with a period.
-
make makemake work on macOS
-
Michał "phoe" Herda created ticket #739
CLISP fails ANSI-TEST LOOP.1.40
-
Flaky test on MacOS: socket-server with run-program
-
fixed in git
-
yq s created ticket #56
MIPS r6 fix: multu -> mul
-
Richard M Kreuter created ticket #738
Impnotes slightly misleading regarding Unix namestring contents
-
Yaron Shahrabani posted a comment on ticket #33
I'm terribly sorry, I saw some bug reports and work done on other bug reports and assumed it's well known. Well, I'm trying to install sbcl for armhf in Alpine 3.8 on RPi3B+, the only thing matters here is the architecture used for the kernel, in my case ARMv7 (ARMv8 - aarch64 is supported but it doesn't matter, same thing happens). Since there was no package I tried downloading the same files as appear in the APKBUILD definition (the file used by Alpine to describe all the different aspect of installing...
-
Jerry James posted a comment on ticket #33
I don't know what you mean by "still" or "doesn't work". Be more specific please.
-
Tried using this patch, still doesn't work, I tried patching it for Alpine 3.8.
-
Macro Lambda-Lists Don't Permit early &environment Parameter
-
When you read section 3.4.1 http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/sec_3-4-1.html it is clear how the brackets have to be interpreted, namely as an optional part at the given position. (Optional parts at ANY position are written in a different way, see http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/sec_1-4-1-2-1.html .) Per 3.4.7 http://www.ai.mit.edu/projects/iiip/doc/CommonLISP/HyperSpec/Body/sec_3-4-7.html the &environment var section must come at...
-
Nicolas Hafner posted a comment on ticket #737
Ah, I see. I prematurely assumed that &environment had to come first like in other lambda-lists. Looking at 3.4.7 again now I'm not sure if &environment coming first is even allowed.
-
Macro Lambda-Lists Don't Permit early &environment Parameter
-
(defsetf foo (place &environment env) (value)) works just fine. The problem is that CLISP does not allow &environment before reqvars.
-
Defsetf Lambda-Lists Don't Permit the &environment Parameter
-
Gunter Königsmann created ticket #736
windows Only: Ctrl+Break segfaults
-
windows Only: Ctrl+C handling broken
-
Mark this repository as obsolete.
-
test failures on mips in socket.tst
-
Thank you. I have applied your patch.
-
Bruno, bidirectional errno<--->keyword conversion is already present in the syscalls module. the right solution is probably to move these tests from the core to the syscalls module.
-
Thank you for the patch. I will apply it soon. > Maybe a more systematic solution should be designed. Absolutely. There are three options I can currently think of: Extend OS-ERROR so that it includes not only the numeric value of the code, but also a list of known names of this error code. Add a function that converts a numeric errno code to a list of symbolic ones. * Just add a function that maps a symbolic errno code to a numeric one.
-
Sébastien Villemot posted a comment on ticket #734
FWIW, here is an updated version of my hackish patch, that supports more architectures.
-
Actually there are similar issues on sparc64, GNU/Hurd and GNU/kFreeBSD. Maybe a more systematic solution should be designed.
-
test failures on mips in socket.tst
-
Fix possible build failure on some Linux/powerpc machines.
-
Fix possible build failure on some Linux/powerpc machines.
-
Accepted and rejected key arguments for defgeneric/defmethod. (7.6.4)
-
Concerning clisp-hurd-einval-extra.patch, I have verified that it is no longer needed on the tip of the clisp-2.50 branch. I am going to drop it from the Debian package. Hence this bug can be closed.
-
Fix memory map related warnings on Alpine Linux 3.7/x86_64.
-
Fix compilation error in C++ mode with musl libc.
-
Fix memory map related warnings on Alpine Linux 3.7/i386.
-
Fix memory map related warnings on Alpine Linux 3.7/i386.
-
Fix compilation error in C++ mode with musl libc.