-
Notifications
You must be signed in to change notification settings - Fork 0
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 define WSL specific code in common Linux scripts? #499
Closed
kachick opened this issue
Mar 18, 2024
· 3 comments
· Fixed by #555 · May be fixed by kachick/fzf-git.sh#1 or #519
Closed
How to define WSL specific code in common Linux scripts? #499
kachick opened this issue
Mar 18, 2024
· 3 comments
· Fixed by #555 · May be fixed by kachick/fzf-git.sh#1 or #519
Labels
help wanted
Extra attention is needed
Comments
Merged
kachick
changed the title
Hot to define WSL specific code in common Linux scripts?
How to define WSL specific code in common Linux scripts?
Mar 18, 2024
This was referenced Mar 24, 2024
kachick
added a commit
that referenced
this issue
Apr 9, 2024
💭 No manage WSL specific code by nix maybe better... |
kachick
added a commit
that referenced
this issue
Apr 12, 2024
Mount Ubuntu volumes to a container on podman-remote which connects to a podman-machine in another WSL2 instance Resolves #564 Resolves #563 Updates #499 Initially, I tried to resolve the problem with SSH and rclone mount. Next, I switched to applying the `/mnt/wsl/instances/` path for that. The second method looks good to me, but I am keeping rclone era for now. That is useful for non-WSL environments and cloud sync.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How
https://zenn.dev/ryuu/scraps/a683aee48a2e70
https://github.com/NixOS/nixpkgs/blob/82540cbb879087f40a0ca9a904e50ef4bb1d4e54/pkgs/tools/misc/wsl-open/default.nix#L4
https://wslutiliti.es/wslu/install.html
Problem
junegunn/fzf-git.sh@da11f5c#diff-0734083c99301d10f2914f0db6c255a56e8947417b2ec966d2f4441083a8b003R63
The text was updated successfully, but these errors were encountered: