Opened 6 years ago

Last modified 6 years ago

#1467 closed enhancement

Hash-prefixed numbers cause confusing error message in scripts — at Initial Version

Reported by: sjamaan Owned by: sjamaan
Priority: minor Milestone: 5.1
Component: core libraries Version: 5.0.0
Keywords: read syntax, history references, scripts, errors Cc:
Estimated difficulty: easy

Description

As pointed out by erkin on IRC, when you run a script with -ss which contains something like #0, the error message you get is confusing if you don't know about csi's history references (especially given that this is a script, not manual input).

The error is:

Error: history entry index out of range: 0

If this is the result of running a long script that somewhere contains #0, this doesn't point to the location of the issue either.

Proposed possible improvements:

  • Add the # to the error message so it's clear that this syntax is causing it, even if you don't know what a "history index" is.
  • Include the line number (part of a larger issue in evaluated script code, and the hardest to implement)
  • Disable history syntax when running with -s or -ss.

Change History (0)

Note: See TracTickets for help on using tickets.