-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TV Episodes with "?" in title fail to rename #5
Comments
I should also note that |
I haven't been able to reproduce this so far. The Lost S02E21 episode is titled "?" and that is able to rename just fine. Please could you provide the following so I can try to reproduce it:
I'm able to name files with a question mark just fine on an ext4 filesystem, that's definitely not a restriction. I'm not using Mint, so I'll try running it in a live USB later, but I don't see any reason why Mint would change that. You're definitely writing to an ext4 filesystem and not NTFS? |
Oh, that's my mistake and I apologize - I am actually writing to a drive
formatted as NTFS.
…On Wed, Jan 20, 2021, 3:48 AM James Tattersall ***@***.***> wrote:
I haven't been able to reproduce this so far. The Lost S02E21 episode is
titled "?" and that is able to rename just fine.
Please could you provide the following so I can try to reproduce it:
- the details of the episode(s) you're not able to rename
- the command you're running to invoke AutoTag
I'm able to name files with a question mark just fine on an ext4
filesystem, that's definitely not a restriction. I'm not using Mint, so
I'll try running it in a live USB later, but I don't see any reason why
Mint would change that. You're definitely writing to an ext4 filesystem and
not NTFS?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLMCWKITEBLM3WO43LON6TS22KFXANCNFSM4WJYRA4A>
.
|
That's okay, it's an annoying issue, I encountered it myself before I moved my content over to a proper filesystem. It's also a bit tricky to fix unfortunately. You can check the filesystem that a file is under, but under Linux it can only report it as a FUSE filesystem for an NTFS partition. There doesn't seem to be a way to easily check the actual underlying filesystem. An NTFS partition is probably the only thing that will commonly be mounted in FUSE, so it's probably fairly safe to assume that any drive reported as FUSE is actually an NTFS partition and characters such as "?" and ":" should be removed. |
I've added a new option in v3.0.4, |
Thanks!
…On Wed, Jan 20, 2021, 5:09 PM James Tattersall ***@***.***> wrote:
Closed #5 <#5>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLMCWKVZVHMPP3NWQ36RF3S25IATANCNFSM4WJYRA4A>
.
|
Using Linux Mint 20.1 with zsh, TV episodes with
?
in the title error when renaming as follows:The text was updated successfully, but these errors were encountered: