bugGNU nano - Bugs: bug #65781, the behavior when specifying...


You are not allowed to post comments on this tracker with your current authentication level.

bug #65781: the behavior when specifying 'foo:40:20' is inconsistent

Submitter:  Benno Schulenberg <bens>
Submitted:  Thu 23 May 2024 02:18:59 PM UTC
Severity:  2 - Minor Status:  Fixed
Assigned to:  bens Open/Closed:  Closed

Fri 31 May 2024 09:23:29 AM UTC, comment #1: 

Fixed in git, commit add945e7, by looking for digits and colons starting from the end of the specified filename.

Benno Schulenberg <bens>
Group administrator
Thu 23 May 2024 02:18:59 PM UTC, original submission:  

When the files 'foo' and 'foo:40' both exist, one would expect running `nano foo:40:20` to open 'foo:40' at line 20.  Instead it opens 'foo' at line 40, column 20.  To reproduce, run:

ln -s NEWS foo
ln -s README foo:40
src/nano foo:40:20

Of course, 'foo:40:20' is ambigiuous, but 'foo:40' is ambiguous too, and if nano acts on the longest name in the latter case, it should do so too in the former.

Benno Schulenberg <bens>
Group administrator


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by bens (Submitted the item)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.


    Follow 2 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2024-07-13 bens Open/ClosedOpen Closed
    2024-05-31 bens StatusNone Fixed

    Back to the top

    Powered by Savane 3.13-b921.
    Corresponding source code