Skip to content
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

error: filename/filepath was too long #21

Open
etetlow opened this issue Feb 3, 2021 · 4 comments
Open

error: filename/filepath was too long #21

etetlow opened this issue Feb 3, 2021 · 4 comments

Comments

@etetlow
Copy link

etetlow commented Feb 3, 2021

Hey,

Just come up against one I haven't seen before.
AtomicParsley error: filename/filepath was too long.
Bit of a pain really. Was is the character length set to?

@github-actions
Copy link

github-actions bot commented Feb 3, 2021

Thanks for filing an issue! Please note that this project is only passively maintained, so your best bet for getting an issue resolved is through a pull request that is easy to verify! Please read this for more information.

@etetlow
Copy link
Author

etetlow commented Oct 5, 2021

Sorry, should have said before, this is on macOS Catalina.

@NitsuSaiNeko
Copy link

NitsuSaiNeko commented Oct 17, 2021

I'm also encountering this issue. It'll be great if it can bypass the 255 character limitation.
This issue was in the original developer's buglist.
I'm running this from Windows10 64bit.
Many full size characters that took 2 bit per characters really makes the 255 limitation not enough ; - ;

@malhal
Copy link
Contributor

malhal commented Jul 21, 2024

Same problem here:

AtomicParsley error: filename/filepath was too long.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants