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

kakoune connection breaks due changed TMPDIR inside nix-shell #24738

Closed
tripokey opened this issue Apr 8, 2017 · 3 comments
Closed

kakoune connection breaks due changed TMPDIR inside nix-shell #24738

tripokey opened this issue Apr 8, 2017 · 3 comments

Comments

@tripokey
Copy link
Contributor

tripokey commented Apr 8, 2017

Issue description

kakoune fails to create new splits when run inside a nix-shell.

kakoune uses the TMPDIR environment variable when deciding where to create its session sockets and nix-shell changes TMPDIR rendering it unable to find the session socket to connect to after creating a new tmux split.

Steps to reproduce

$ tmux
$ nix-shell -p hello
$ kak

While in kakoune type :new and press .

Technical details

  • System: 17.03.902.536d3cac2e (Gorilla)
  • Nix version: nix-env (Nix) 1.11.8
  • Nixpkgs version: "17.03.902.536d3cac2e"
@Mic92 Mic92 changed the title kakoune broken when run inside nix-shell kakoune connection breaks due changed TMPDIR inside nix-shell Apr 8, 2017
@Mic92
Copy link
Member

Mic92 commented Apr 8, 2017

Workaround is to set TMPDIR to export TMPDIR=/run/user/$(id -u) in your shell rc. /tmp/ is currently not a tmpfs, which /run/user/<uid> is.

@Mic92
Copy link
Member

Mic92 commented Apr 8, 2017

Actually I don't know why they are different historically. Probably /run/user/ is better shielded against interference of other user.

@tripokey
Copy link
Contributor Author

tripokey commented Apr 8, 2017

Thanks!

Considering that TMPDIR might differ for tmux and kakoune regardless of wether NixOS is used or not I filed an issue for this in the kakoune repository:
mawww/kakoune#1319

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 a pull request may close this issue.

2 participants