bugGNU nano - Bugs: bug #47798, option --operatingdir accepts a...

 
 

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

bug #47798: option --operatingdir accepts a normal filename without protest

Submitted by:  Benno Schulenberg <bens>
Submitted on:  Thu 28 Apr 2016 09:06:27 AM UTC  
 
Severity:  3 - Normal Status:  Fixed
Assigned to:  Benno Schulenberg <bens> Open/Closed:  Closed

Sun 12 Jun 2016 09:40:25 AM UTC, comment #2: 

The first part is now fixed properly in git, aa09abe: when the specified operating dir is invalid, nano dies.

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.
Sun 22 May 2016 09:54:11 AM UTC, comment #1: 

Fixed in git, c028568 and fbb6208.

The first part is fixed by c028568, but not by dying, but by showing an error message.  On second thought, that is maybe not good.  Trying to confine nano and not succeeding is not like specifying a nonexistent syntax.  For the latter a message on the statusbar and continuing anyway is maybe acceptable; for the first refusing to start is probably a better choice.

The third part is fixed by fbb6208.

The second part is "fixed" by accepting the empty string to be equal to ".".

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.
Thu 28 Apr 2016 09:06:27 AM UTC, original submission:  

To reproduce, run 'src/nano --oper=NEWS'.  Nano says nothing, does not even beep, let alone fail to start.

Expected behavior: nano should fail to start when something that is not a valid directory has been specified with --operatingdir, just like when specifying nothing at all with that option (a blank "--oper").

Second bug: when specifying "--oper=  NEWS", nano takes the current directory as the operating dir, but indicates it on the statusbar with the empty string, which is somewhat confusing.

Expected behavior: nano should not accept an empty name as argument of --operatingdir.

Third bug: when specifying "--oper=..", the message when trying to read a file outside of the then current directory is confusing: "Can't go outside of .. in confined mode".

Expected behavior: nano should translate the argument of --operatingdir to an absolute pathname for presentation purposes.

Benno Schulenberg <bens>
Project AdministratorIn charge of this item.

 

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)
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only logged-in users can vote.

     

     

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-06-20 bens Open/ClosedOpen => Closed
    2016-06-12 bens StatusReady For Test => Fixed
    2016-05-22 bens StatusIn Progress => Ready For Test
    2016-04-30 bens StatusNone => In Progress
        Assigned toNone => bens

    Back to the top


    Powered by Savane 3.5