Skip to content

Don't generally require args and paths to be valid UTF-8, remove dependency on camino#33

Open
alurm wants to merge 1 commit intonoamraph:masterfrom
alurm:do-not-require-utf-8-args-and-paths
Open

Don't generally require args and paths to be valid UTF-8, remove dependency on camino#33
alurm wants to merge 1 commit intonoamraph:masterfrom
alurm:do-not-require-utf-8-args-and-paths

Conversation

@alurm
Copy link

@alurm alurm commented Aug 2, 2025

OsStr and OsString is used instead.
"_utf8" versions of functions are replaced with their regular versions. Paths are printed with {:?} in logs and errors.
NIXSA_BWRAP_ARGS is still required to be UTF-8.
quote() still returns String, but is expected to perform a proper conversion from OsString under the hood.

Closes #32.

…ndency on camino

OsStr and OsString is used instead.
"_utf8" versions of functions are replaced with their regular versions.
Paths are printed with {:?} in logs and errors.
NIXSA_BWRAP_ARGS is still required to be UTF-8.
quote() still returns String, but is expected to perform a proper conversion from OsString under the hood.

Closes noamraph#32.
@alurm
Copy link
Author

alurm commented Aug 2, 2025

I haven't tested this yet. I'll be testing it now.

@alurm
Copy link
Author

alurm commented Aug 2, 2025

Some parts of this definitely work:

$ nixsa "$(printf '\777')"
--: line 1: exec: �: not found

What do you think?

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

Successfully merging this pull request may close these issues.

Nixsa doesn't work with non-UTF-8 paths

1 participant