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

How to handle reserved filenames in Windows? #262

Open
joeytakeda opened this issue Jan 25, 2023 · 1 comment
Open

How to handle reserved filenames in Windows? #262

joeytakeda opened this issue Jan 25, 2023 · 1 comment
Assignees
Labels
enhancement New feature or request question Further information is requested
Milestone

Comments

@joeytakeda
Copy link
Contributor

We now have Windows support (#250 and #33), but we will need to handle reserved filenames in Windows. As @martindholmes wrote:

List of reserved windows filenames:

CON, PRN, AUX, NUL
COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9
LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9

If files called e.g. "con.json" are created, they can't be deleted by an ordinary user. No idea what we might do here, other than add these things to the stopword list if you're building on Windows.

@joeytakeda joeytakeda added enhancement New feature or request question Further information is requested labels Jan 25, 2023
@joeytakeda joeytakeda added this to the Release 2.0 milestone Jan 25, 2023
@martindholmes
Copy link
Collaborator

I think we could silently add ones with numerals to the stopword list at build time, since they're not really words, but the first four might require an explicit warning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants