Opened 13 years ago

Closed 12 years ago

#276 closed defect (fixed)

clisp/maxima dies with "invalid byte" on non-ASCII filename characters

Reported by: cwitty Owned by: was
Priority: minor Milestone: sage-2.8.8
Component: interfaces Keywords: clisp maxima
Cc: Merged in:
Authors: Reviewers:
Report Upstream: Work issues:
Branch: Commit:
Dependencies: Stopgaps:


When clisp (and hence maxima) starts, it tries to load ~/.clisprc; this involves reading the names of all files in my home directory. If I have no locale-related environment variables set, and I have a non-ASCII character in some filename in my home directory (in my case, an 'ñ'), then clisp prints out the following error message:

*** - invalid byte #xF1 in CHARSET:ASCII conversion
The following restarts are available:
ABORT          :R1      ABORT
ABORT          :R2      ABORT
Break 1 [3]>

(If I abort from here, then clisp/maxima continues to start up, and apparently runs correctly.)

Evidently, the clisp people don't consider this a bug; it is documented here:

I suggest that SAGE should either set locale environment variables or use the -E flag to set encodings when it runs maxima (as suggested in the above-linked FAQ entry). (For now, I have worked around the problem by moving this file out of my home directory.)

Attachments (1)

trac276.patch (982 bytes) - added by was 12 years ago.

Download all attachments as: .zip

Change History (3)

comment:1 Changed 12 years ago by mabshoff

  • Milestone set to sage-2.9.1

Changed 12 years ago by was

comment:2 Changed 12 years ago by was

  • Milestone changed from sage-2.9.1 to sage-2.8.8
  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.