Sure, but because after "applying" the change the file will just disappear, it's very easy to lose files this way... Maybe, if you add a special message (that can be suppressed for good for example) that notifies the user about the behaviour when he does it, that'd be a nice feature to keep. It looks very useful, but the risk of accidentally renaming to "/tmp/bla" or "bla/bla/bla2.txt" feels a bit too high.
On 10/09/12 16:52, Michael Blumenkrantz wrote: > renaming into other directories in this manner still prompts for > overwrites and everything just like moving a file normally would > > On Mon, Sep 10, 2012 at 2:49 PM, Tom Hacohen <tom.haco...@samsung.com > <mailto:tom.haco...@samsung.com>> wrote: > > On 10/09/12 16:35, Michael Blumenkrantz wrote: > > currently, rename functionality in EFM allows moving files by > typing paths. > this can be accomplished through the following: > > directory contents { directory/ file } > rename(file) -> "directory/file" > file is now located in the subdirectory > > the question is, is this behavior that we want? there isn't a > problem with > it from a functional perspective; it works, checks permissions, > all that. > the issue is just that this is not "expected" behavior when > renaming a file > in a graphical file manager. > > > People will likely lose files like that, we should probably filter > all the illegal path chars. > > -- > Tom. > > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
