Changes between Initial Version and Version 1 of Ticket #1467


Ignore:
Timestamp:
05/30/18 21:41:55 (7 years ago)
Author:
sjamaan
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #1467

    • Property Priority changed from major to minor
    • Property Summary changed from Hash-prefixed numbers cause confusing error message in scripts to Bare hashes cause confusing error message in scripts

  • Ticket #1467 – Description

    initial v1  
    1 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).
     1As pointed out by erkin on IRC, when you run a script with `-ss` which contains something like `#`, the error message you get is confusing, especially if you don't know about csi's history references (especially given that this is a script, not manual input).
    22
    33The error is:
    … …  
    77}}}
    88
    9 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.
     9If this is the result of running a long script that somewhere contains `#` (or just `#0`), this doesn't point to the location of the issue either.
    1010
    1111Proposed possible improvements:
    1212
    13 - 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.
     13- 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. But note that just adding it is not going to be enough, since just `#` also triggers this error.
     14- Give a better/different error when reading a bare `#`
    1415- Include the line number (part of a larger issue in evaluated script code, and the hardest to implement)
    1516- Disable history syntax when running with `-s` or `-ss`.