Project

General

Profile

Bug #164

CoCoA-5 emacs interface bug (minor): Source & SourceRegion with troublesome filenames

Added by John Abbott almost 12 years ago. Updated over 8 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
EmacsUI
Start date:
20 May 2012
Due date:
% Done:

100%

Estimated time:
1.00 h
Spent time:

Description

By accident I created a filename containing a newline.
Sending the file to CoCoA-5 in emacs (by C-c C-f) produced the following error:

ERROR: Newline characters are not allowed inside string literals (you can insert them using escape sequences, for instance, \n or use multi-line string literals)

I suspect something bad may occur if the filename contains double quote characters too. We should add some safety checks.


Related issues

Related to CoCoA-5 - Feature #8: source regionClosed2011-10-20

History

#1 Updated by Anna Maria Bigatti about 10 years ago

  • Target version set to CoCoA-5.1.0 Easter14

#2 Updated by John Abbott about 10 years ago

  • Category changed from GUI to EmacsUI
  • Target version changed from CoCoA-5.1.0 Easter14 to CoCoA-5.?.?

#3 Updated by John Abbott almost 10 years ago

  • Subject changed from CoCoA-5 emacs interface bug (minor) to CoCoA-5 emacs interface bug (minor): Source & SourceRegion with troublesome filenames
  • Status changed from New to Feedback
  • Assignee set to John Abbott
  • % Done changed from 0 to 90
  • Estimated time set to 1.00 h

I have modified cocoa5.el to add escapes for " and newlines inside filenames.
A quick test showed that it works as expected (on my computer).

#4 Updated by John Abbott almost 9 years ago

  • Target version changed from CoCoA-5.?.? to CoCoA-5.1.2 summer 2015

#5 Updated by John Abbott over 8 years ago

  • Status changed from Feedback to Closed
  • % Done changed from 90 to 100

This has been in feedback for a year; a quick check shows that it works for a filename containing a double-quote, and for one containing a newline. So I'm closing.

Also available in: Atom PDF