Open Thescorps opened 2 years ago
Big +1 on wildcards especially. * and ? use are bizarrely missing here, which makes little sense considering the apparent design philosophy of PowerRename. By all accounts, based on its design and comments I've seen here, it's meant as a fairly basic yet moderately powerful renamer, not quite as powerful as many others but with a much simpler UI. I've been using it for what should be very quick renaming tasks, as it seems that's what it's geared toward (i.e. making a single, simple change versus multiple and/or complex changes, in which case I use another program), with the idea that it will be quicker than using something else, but I often find it to actually be slower and more complicated, partially due to its overly simplistic UI, and partially due to the lack of basic functionality that would make it much faster to use.
The use of wildcards is just one such example of this. A bit earlier, I tried to do what should have been a very quick task, taking a few seconds to accomplish, by putting "*" (without quotes) in the search box and "jpg" in the replace box and selecting apply to extensions only. This should have been all that was necessary, being both easy and fast, to rename the file extensions, but it didn't do anything, because of the lack of basic wildcards. Yes, I can use regex to accomplish this, but that shouldn't be necessary, and most users won't know how. In fact, I'd argue that most users are going to likely have little knowledge and may not even be able to (easily) do such a task even with basic wildcards, and a wizard or at least a dropdown with different tasks (e.g. rename extension in this case) could be implemented to assist them in setting things up for a given task.
Another renaming task I often use this for is to add some text to the end of multiple files. Again, this should be as simple as selecting the file in explorer, right-clicking them and selecting PowerRename, and typing the text to append (or prepend if that's the case) in the replace box and selecting append/prepend from a dropdown, or alternately an option to add at a certain position at which point the user can enter a position or select beginning/end or prepend/append. This is, I believe, what @Thescorps meant by "digits from left/right" and it is a basic function in every renamer I've used and greatly simplifies things, as opposed to having to use regex, which most don't know how to do and, even for those that do, can be more cumbersome and slower, especially for adding text at a specific position not at the beginning or end.
Again, I've been using PowerRename a good bit in order to try it out, but every time I use it, I find myself thinking I could do what I'm doing faster and easier with a different program, despite it being more complicated, because it's more versatile and powerful. PowerRename seems to be at odds with itself, trying to be so "simple" that it ends up being more difficult and time-consuming to use as a result. Just looking at the number of issues requesting various functions to perform these basic tasks is proof, to me, of this.
When using Title case fn, restart Apply(ies) To Filename + Extension.
Use case: Torrent containing '.' between words and lower case. Replace '.' for ' ', Change to Title Case.
Next restart I lose my terminal, say, '.mkv'
I do agree that the current implementation of PowerRename, despite having so much potential, leaves much to be desired in the current form. I'd be happy to contribute to improving this feature, as it does seem to be unfortunately neglected from what I've seen.
@Thescorps, you may want to consider editing the title of this issue so it isn't so general...there's no way we're the only three people that would like to see the text matching options receive some TLC, but I suspect this issue gets overlooked in most cases because of this. Something to the effect of "Improved string pattern matching for PowerRename"
perhaps; just a suggestions.
I gave it a look on Gitbub and I don't see an edit button. Anything for hygienic coding standards. Show me the path (Jedi/Coder humour). PS always a project manager never a coder/bride... Improved string pattern matching for PowerRename -------- Original message --------From: Stelio Kontos @.> Date: 2023-01-20 13:33 (GMT-05:00) To: microsoft/PowerToys @.> Cc: Thescorps @.>, Mention @.> Subject: Re: [microsoft/PowerToys] PowerRename Enhancement (Issue #18662) I do agree that the current implementation of PowerRename, despite having so much potential, leaves much to be desired in the current form. I'd be happy to contribute to improving this feature, as it does seem to be unfortunately neglected from what I've seen. @Thescorps, you may want to consider editing the title of this issue so it isn't so general...there's no way we're the only three people that would like to see the text matching options receive some TLC, but I suspect this issue gets overlooked in most cases because of this. Something to the effect of "Improved string pattern matching for PowerRename" perhaps; just a suggestions.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
People should be able to find it with keywords. I don't take lack of participation in an issue to necessarily mean there's a lack of interest by users, but rather how many people are actually using PowerToys, how many are using this feature as opposed to, frankly, far superior already existing tools, and how many people even use Github.
Oh man that's a lot of how many's. But in my view PowerToys has a bit of a wizbang factor like we're on the Beta channel of Windows updates. I'm sure they have a stat about number of downloads? We wouldnt be talking if we both didn't appreciate the effort and Work In Progress that it is...My top apps are Chrome, QBittorrent, Power Rename aaaand the Global Keeeys (F1 = Terminate and F11 = close window), mp3tag Renamer and KL Codec pack Mega featuring MPC Classic. And Excel :) -------- Original message --------From: vertigo220 @.> Date: 2023-01-20 13:49 (GMT-05:00) To: microsoft/PowerToys @.> Cc: Thescorps @.>, Mention @.> Subject: Re: [microsoft/PowerToys] PowerRename Enhancement (Issue #18662) People should be able to find it with keywords. I don't take lack of participation in an issue to necessarily mean there's a lack of interest by users, but rather how many people are actually using PowerToys, how many are using this feature as opposed to, frankly, far superior already existing tools, and how many people even use Github.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: @.***>
People should be able to find it with keywords.
@vertigo220 I beg to differ; 200 open issues all specific to the PowerRename feature tells me there's more than 3 users that give a crap about this particular slice of PowerToys. Lazy titles in SEO equates to no clicks, and the same applies here. No attention = no traction = no resolution.
[edit] That said, I 100% agree with your original comment; I can relate to every one of your points...was relief to know it wasn't just me spending longer trying to make it perform a basic lookup/replace for some rather common scenarios than it would've taken me to manually rename them from the get-go. :(
@Thescorps look for an "Edit" button on the right side, even with the title (should be next to the green "New Issue" button). Edit it inline, hit return, done.
I do agree that the current implementation of PowerRename, despite having so much potential, leaves much to be desired in the current form. I'd be happy to contribute to improving this feature, as it does seem to be unfortunately neglected from what I've seen.
@Thescorps, you may want to consider editing the title of this issue so it isn't so general...there's no way we're the only three people that would like to see the text matching options receive some TLC, but I suspect this issue gets overlooked in most cases because of this. Something to the effect of
"Improved string pattern matching for PowerRename"
perhaps; just a suggestions.People should be able to find it with keywords.
@vertigo220 I beg to differ; 200 open issues all specific to the PowerRename feature tells me there's more than 3 users that give a crap about this particular slice of PowerToys. Lazy titles in SEO equates to no clicks, and the same applies here. No attention = no traction = no resolution.
[edit] That said, I 100% agree with your original comment; I can relate to every one of your points...was relief to know it wasn't just me spending longer trying to make it perform a basic lookup/replace for some rather common scenarios than it would've taken me to manually rename them from the get-go. :(
@Thescorps look for an "Edit" button on the right side, even with the title (should be next to the green "New Issue" button). Edit it inline, hit return, done.
Thanks Fella, (wasn't logged in) and edited for @vertigo220 let's Reddit bump/thumbs up this thing!
especially. * and ? use are bizarrely missing here
@vertigo220 Are you sure the checkbox for Regular expressions is marked?
@Jay-o-Way Not sure, since that was four months ago, and I gave up using this, but I'm going to guess probably not, because I didn't say . and .? but rather * and ?, which should be usable in non-regex, as they are in pretty much every other non-regex search/filter function I've ever used.
which should be usable in non-regex, as they are in pretty much every other non-regex search/filter function I've ever used
There might lie the cause of an incorrect assumption. Maybe those characters are treated as literal, in stead of a variable. Need one of the core writers to confirm... @jaimecbernardo @yuyoyuppe ?
which should be usable in non-regex, as they are in pretty much every other non-regex search/filter function I've ever used
There might lie the cause of an incorrect assumption. Maybe those characters are treated as literal, in stead of a variable. Need one of the core writers to confirm... @jaimecbernardo @yuyoyuppe ?
They're treated as literal when you're not using regex, I assume. @stefansjfw , please keep me honest here. Regarding this issue, it looks indeed like it's too general. It makes sense to turn the wildcards suggestion into its own issue.
They're treated as literal when you're not using regex, I assume. @stefansjfw , please keep me honest here.
This is correct. Also, as * and ? are not permitted in folder/file names, it makes sense to use them regardless of regex switch Let's create a new issue to track that one, and continue more general discussion here
Given there has been no formal reaction to this ticket since June 7 I'm beginning to sence that this is a lost toy. I see in updates to the Toys suite that other coders contribute to other features like accented characters, so I guess if we can't bring a coded solution to the table it will just die on the vine. Maybe get ChatGPT to write some batch files in lieu...
Description of the new feature / enhancement
Improved string pattern matching for PowerRename
Wildcards, digits from left/right, Sentence case, user filter list (all CAPS conventions), cycle through all conditions until they are changed, auto close when complete, allow only one instance, file HERE when done.....
Scenario when this would be used?
Everytime we use PowerRename
Supporting information
No response