Update renaming extension

[ridemountainpig]

Description

Add a new Replace File(s) Characters command to change characters in file names.
closes #15484

Screencast

Checklist

• I read the extension guidelines
• I read the documentation about publishing
• I ran npm run build and tested this distribution build in Raycast
• I checked that files in the assets folder are used by the extension itself
• I checked that assets used by the README are placed outside of the metadata folder

[raycastbot]

Thank you for your contribution! 🎉

🔔 @theodaguier @ridemountainpig you might want to have a look.

You can use this guide to learn how to check out the Pull Request locally in order to test it.

You can expect an initial review within five business days.

[pernielsentikaer]

Do you have a clue why I don't see the form?

[ridemountainpig]

Do you have a clue why I don't see the form?

I have updated the script to resolve this error. Can you please check it again. Thank you, @pernielsentikaer.

[pernielsentikaer]

That works better 😊

Nothing happens when I use it, first after the timeout I'll get an error:

16:19:17.534 Error: Command timed out after undefined milliseconds: osascript
Timed out
    at Timeout.<anonymous> (/Users/pernielsentikaer/.config/raycast/extensions/renaming/replace.js:4464:32)
    at listOnTimeout (node:internal/timers:573:17)
    at process.processTimers (node:internal/timers:514:7) {
  timedOut: true,
  signal: 'SIGTERM',
  originalMessage: 'Timed out',
  shortMessage: 'Command timed out after undefined milliseconds: osascript\nTimed out',
  command: 'osascript',
  exitCode: null,
  stdout: '',
  stderr: ''
}

Do you have a clue about that one too?

[ridemountainpig]

Nothing happens when I use it, first after the timeout I'll get an error:

16:19:17.534 Error: Command timed out after undefined milliseconds: osascript
Timed out
    at Timeout.<anonymous> (/Users/pernielsentikaer/.config/raycast/extensions/renaming/replace.js:4464:32)
    at listOnTimeout (node:internal/timers:573:17)
    at process.processTimers (node:internal/timers:514:7) {
  timedOut: true,
  signal: 'SIGTERM',
  originalMessage: 'Timed out',
  shortMessage: 'Command timed out after undefined milliseconds: osascript\nTimed out',
  command: 'osascript',
  exitCode: null,
  stdout: '',
  stderr: ''
}

Do you have a clue about that one too?

Weird 😨, it runs normally on my end.

[pernielsentikaer]

Hi 👋

Looks good to me, approved 🔥

[pernielsentikaer]

Hi 👋

Looks good to me, approved 🔥

[github-actions]

Published to the Raycast Store:
https://raycast.com/theo_daguier/renaming

[raycastbot]

🎉 🎉 🎉

We've rewarded your Raycast account with some credits. You will soon be able to exchange them for some swag.