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

zsh-syntax-highlighting: init at 0.4.1 #19179

Closed
wants to merge 3 commits into from
Closed

Conversation

loskutov
Copy link
Contributor

@loskutov loskutov commented Oct 2, 2016

Motivation for this change

zsh-syntax-highlighting is a popular package (available in Ubuntu, homebrew, etc.), lacking in nixpkgs.

Things done
  • Tested using sandboxing
    (nix.useSandbox on NixOS,
    or option build-use-sandbox in nix.conf
    on non-NixOS)
  • Built on platform(s)
    • NixOS
    • OS X
    • Linux
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@loskutov
Copy link
Contributor Author

loskutov commented Oct 2, 2016

It also requires something like source /run/current-system/sw/share/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh in programs.zsh.interactiveShellInit to work. Is it a good idea to leave a comment about it, or add an entry to config.programs.zsh, or do something else?

@langston-barrett
Copy link
Contributor

langston-barrett commented Oct 2, 2016

@loskutov You could add a new configuration option to nixpkgs/nixos/modules/programs/zsh/zsh.nix that would automatically add that line at the end of the interactiveShellInit.

somewhere in here you could add something like

${optionalString (cfg.syntaxHighlighting) "source /run/current-system/sw/share/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh"}

and add the appropriate mkOption.

@Mic92
Copy link
Member

Mic92 commented Oct 3, 2016

I would also leave a comment in the package itself.

@Mic92
Copy link
Member

Mic92 commented Oct 3, 2016

I had to adapt the source line a little (9f34b55#diff-0740f57e63af61694d14796286cb9204R132), but then it worked. Thanks!

@langston-barrett
Copy link
Contributor

Working perfectly. Thanks @Mic92, @loskutov!

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

Successfully merging this pull request may close these issues.

None yet

3 participants