Opened 8 years ago

Closed 6 years ago

#479 closed defect (fixed)

Keep file permissions when doing "Save as..."

Reported by: Sewi Owned by:
Priority: major Milestone:
Component: editor Version: trunk
Keywords: Cc:


When you open a file with - for example - an unix execution bit (chmod +x), it is not kept when using the "Save as..." - function.

Change History (5)

comment:1 Changed 8 years ago by karl.forner

I guess it is the usual unix behaviour on files. When you write on an existing file the permissions do not change, but if you create a new file, it is created using your umask and the directory permissions.
Do we really want to memorize the permissions of the opened file ??

comment:2 Changed 8 years ago by karl.forner

So, should we decide to keep the current behaviour ?

comment:3 Changed 8 years ago by Sewi

It might be usual but it isn't expected or good :-)

I'd keep it open.

comment:4 Changed 8 years ago by karl.forner

Actually I'm not convinced...
In my opinion, "saving as..." means creating a new file that has no relation with the previous file, just the contents.
So the permissions should not be kept.
But, and that is another problem, when you create a script (.pl° file, maybe by default it should have the execution bit.
What do you think ?

comment:5 Changed 6 years ago by bowtie

  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.