Stuck in a rename loop

Post by **j_c_hallgren** » 25 Jul 2008 16:11

As an addendum to prior about extensions:

I see best option as similar to viewing full name in col A of a spreadsheet, or name in col A and ext in col B, so one would still always see it, but user decides if together or adjacent.

ivan · Post by **ivan** » 25 Jul 2008 16:50

So before this thread gets out of control with stuff that wasn't directly related (yeah, I know, I didn't help) to the main post, let's just sum up the list of wishes:

1. Implement XP-like behaviour for Vista users when it comes to accidental duplicate renaming procedures.

2. Include an option to disable creation/renaming of files with no base name.

The other issues can be handled via their respective threads without this one going off-topic. Let's just focus on those two. Now the ball is firmly in Don's court to see what he thinks and if he sees sense in having those "wishes" granted.

jacky · Post by **jacky** » 25 Jul 2008 17:25

ivan wrote:Include an option to disable creation/renaming of files with no base name.

No really, there's no reason for that. Just because you don't like it/see a use for it means XY should have an option to prevent it form happening.

ivan, somewhere else, wrote:But is it still possible to disable scripts overriding through a preference?

And I don't think this is doable, or would make sense. If you don't trust a script, read it first, use the step mode, or simply don't run it!

Besides, there are script commands to do the opposite and (temporarily) change settings to ensure that the script execution will go as planned. It's not allowing this that could end up cause trouble!

Yes, a script could rename files to start with a dot, or delete them, or anything. The simply action of copying of moving file can be harmful if it's meant to, doesn't mean it shouldn't be allowed from scripting.

ivan · Post by **ivan** » 25 Jul 2008 17:46

jacky wrote:No really, there's no reason for that. Just because you don't like it/see a use for it means XY should have an option to prevent it form happening.

We can keep going around in circles about this. XYplorer has dozens (maybe even hundreds) of options that I very likely will never use. Let's start with Catalog, I don't use that at all. However, just because one does not see a point in having something doesn't make it wrong for another to consider it a good thing. One person's crap is another person's gold, to put it bluntly.

jacky wrote:And I don't think this is doable, or would make sense. If you don't trust a script, read it first, use the step mode, or simply don't run it!

Besides, there are script commands to do the opposite and (temporarily) change settings to ensure that the script execution will go as planned. It's not allowing this that could end up cause trouble!

Yes, a script could rename files to start with a dot, or delete them, or anything. The simply action of copying of moving file can be harmful if it's meant to, doesn't mean it shouldn't be allowed from scripting.

a) A script shouldn't have to do tweak a setting that isn't changeable through Config. The whole point of me suggesting such ability was temp solution and making a person aware that the same is possible through a preference.

b) I'm not saying block scripting period. I'm saying that some (optonally selectable) restrictions should be put in place. Like Parental Controls on TVs - no problem if you wanna watch the latest episode of Transformers Animated but if you try to flick to see The Hottest Laydeez This Side of Las Vegas you get a big no-no. Scripting is a powerful tool, there's gotta be a safety net.