two formatting errors (new paragraphs) in clisp.1 man page

[Erik Auerswald]

Hi,

the clisp.1 man page contains two instances where the .PP macro is not preceded by a newline. This results in literal .PP inside the rendered man page instead of creating a new paragraph with the .PP macro:

Instance one:

       -on-error action
           Establish global error handlers, depending on action:.PP appease
               continuable[17] ERROR[18]s are turned into WARNING[19]s (with
               EXT:APPEASE-CERRORS) other ERROR[18]s are handled in the
               default way

           debug
               ERROR[18]s INVOKE-DEBUGGER[20] (the normal read-eval-print
               loop[2] behavior), disables batch mode imposed by -c, -x, and
               lisp-file,

Instance two:

USING AND EXTENDING CLISP
       Common Lisp[1] is a programmable programming language. —John
       Foderaro[47].PP When CLISP[6] is invoked, the runtime loads the initial
       memory image and outputs the prompt; at which one can start typing
       DEFVAR[48]s, DEFUN[49]s and DEFMACRO[50]s.

The fix is simple, just add a newline in front of the two .PP macros, as done in the attached patch. The result looks as follows:

Instance one:

       -on-error action
           Establish global error handlers, depending on action:

           appease
               continuable[17] ERROR[18]s are turned into WARNING[19]s (with
               EXT:APPEASE-CERRORS) other ERROR[18]s are handled in the
               default way

           debug
               ERROR[18]s INVOKE-DEBUGGER[20] (the normal read-eval-print
               loop[2] behavior), disables batch mode imposed by -c, -x, and
               lisp-file,

Instance two:

USING AND EXTENDING CLISP
       Common Lisp[1] is a programmable programming language. —John
       Foderaro[47]

       When CLISP[6] is invoked, the runtime loads the initial memory image
       and outputs the prompt; at which one can start typing DEFVAR[48]s,
       DEFUN[49]s and DEFMACRO[50]s.

The patch can be put into the "debian/patches" directory and appended to the "debian/patches/series" file.

At the end of last year, I had reported this bug to the upstream CLISP bug tracker at <https://sourceforge.net/p/clisp/bugs/> as described on the CLISP home page <https://clisp.sourceforge.io/> (identical to <https://www.gnu.org/software/clisp/>), please see <https://sourceforge.net/p/clisp/bugs/748/>. I did not receive any feedback there. The bug is still present in the upstream development repository. Thus it seems to me as if it might be prudent to add this fix to the Ubuntu (and Debian) clisp package.

The attached patch is against the clisp version in Ubuntu 20.04.6 LTS (Focal Fossa), because that is the version I use.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "formatting bug fix that can be used inside debian/patches/" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Brian Murray (brian-murray)]

The package clisp in Ubuntu is currently in sync with the version of the package in Debian. Subsequently, I think the best path forward here is to submit your changes to Debian. You can find the source code for clisp in Debian at https://salsa.debian.org/common-lisp-team/clisp/-/tree/master. Would mind creating a pull request there? Thanks in advance!

[Erik Auerswald (auerswal)]

Thanks for the response!

I have created a bug report in the Debian bug tracker:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041788

Best regards,
Erik