James Murty

The problem is when a file with problematic characters – like the "Terrible File" example – is added as a secret/encrypted file, its name gets munged by the `_list_encrypted_files()` function...

Hi @andreineculau are you sure you are checking a file with a problematic name when that file is also _encrypted_, not just staged as a standard file? The problem manifests...

Hi, thanks. Which version of transcrypt are you using? And which version of bash is on the systems that show the problem (run `/usr/bin/env bash --version`)? If it's the latest...

I should mention that – assuming the line I linked above is indeed the problem line – you can run just the problematic function for easier testing with the `--list`...

Ah okay, it definitely seems like you're hitting a transcrypt bug handling one of your file names. Here is a command you can run which is a trimmed down version...

The latest `main` version of transcrypt has changes to the `_list_encrypted_files()` function to improve performance in large repos (#193). These changes aren't yet in an official release and are not...

I have been able to reproduce the issue by creating and staging a file with this name: `"Terrible file""")))(((][][].secret` Using a different variant of the `while` loop line does fix...

Hi @pets-er could you try a potential fix I've applied to _transcrypt_ in PR #205?

Great! Glad to hear the 204 fix worked for you. Could you list example file name(s) that caused this problem for you? I would like to collect another example or...

Hi @andreineculau I have fixed one potential place where global Git configs could be set by running `bats tests/` in commit f88979c6. I'm not sure how your _~/.gitattributes_global_ file is...