This is important when typing characters such as ⚡(U+26A1 HIGH VOLTAGE
SIGN), otherwise fish computes a different character width than the
terminal. See https://github.com/fish-shell/fish-shell/pull/4816
Instead of searching `/usr` it should search for the `xkb`,
$XDG_DATA_DIRS will be searched. With this approach we allow compliance
on NixOS and non-NixOS systems to find `symbols` in the `xkb` directory.
The patch has been accepted by upstream, but isn't released yet, so this
is mainly a temporary fix until we can bump ZSH to the next stable version.
The `xserver` module links `/share/X11/xkb` to `/run/current-system` to
make this possible.
The fix can be tested inside the following VM:
```
{
zshtest = {
programs.zsh.enable = true;
users.extraUsers.vm = {
password = "vm";
isNormalUser = true;
};
services.xserver.enable = true;
};
}
```
Fixes#46025
From upstream's NEWS:
> Changes from 5.6.1 to 5.6.2
> ---------------------------
>
> Fix another SIGTTOU case.
>
> Fix SIGWINCH being ignored when zsh is not in the foreground.
>
> The release tarballs are now compressed using xz(1), whereas previously
> both xz(1) and gzip(1) versions were available. If this gets in your way,
> give us a shout.
>
This ensures that no impurity exists due to implicitly depending
on`/usr/bin/env`.
It stores the theme into `$out/share/zsh/themes` to make it possible to
find theme using `buildEnv` and remain consistent with other ZSH
extensions.
These files feature simple aliases and a nix-shell detector when using
`nix-shell --run zsh`. The package itself contains the completion scripts in
`$out/share/zsh/site-functions` (to keep it compatible with ZSH-only
setups) and the plugins in `$out/share/zsh/plugins` for oh-my-zsh.
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/xonsh/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/yp41kipqmmsjl0ldi4b16z2590shv9dp-xonsh-0.6.8/bin/xon.sh had a zero exit code or showed the expected version
- /nix/store/yp41kipqmmsjl0ldi4b16z2590shv9dp-xonsh-0.6.8/bin/.xonsh-wrapped passed the binary check.
- /nix/store/yp41kipqmmsjl0ldi4b16z2590shv9dp-xonsh-0.6.8/bin/xonsh passed the binary check.
- 2 of 3 passed binary check by having a zero exit code.
- 2 of 3 passed binary check by having the new version present in output.
- found 0.6.8 with grep in /nix/store/yp41kipqmmsjl0ldi4b16z2590shv9dp-xonsh-0.6.8
- directory tree listing: https://gist.github.com/e53ad25422aa303572f4452029cb65b3
- du listing: https://gist.github.com/0c29b7c27c01e8d34986163ba00f1615
This package adds completion scripts for `gradle` on the `bash` and
`zsh` shells.
The completions can be enabled like this:
```
{ pkgs, ... }:
{
environment.systemPackages = [ pkgs.gradle pkgs.gradle-completion ];
programs.zsh.enable = true;
}
```
The package stores the scripts into the expected directories in
`$out/share` to ensure that the shells can easily find their scripts.
Closes#42799
* treewide: http -> https sources
This updates the source urls of all top-level packages from http to
https where possible.
* buildtorrent: fix url and tab -> spaces
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/xonsh/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/mb1vva59dwhq6yzqf98gkygljbzpdf37-xonsh-0.6.7/bin/xon.sh had a zero exit code or showed the expected version
- /nix/store/mb1vva59dwhq6yzqf98gkygljbzpdf37-xonsh-0.6.7/bin/.xonsh-wrapped passed the binary check.
- /nix/store/mb1vva59dwhq6yzqf98gkygljbzpdf37-xonsh-0.6.7/bin/xonsh passed the binary check.
- 2 of 3 passed binary check by having a zero exit code.
- 2 of 3 passed binary check by having the new version present in output.
- found 0.6.7 with grep in /nix/store/mb1vva59dwhq6yzqf98gkygljbzpdf37-xonsh-0.6.7
- directory tree listing: https://gist.github.com/1d8694bad62c300714d6658deedc7ec0
- du listing: https://gist.github.com/2d8baff97fce82b5ba4ded4746d954a0
For some reason, building powershell derivation started failing with
these errors:
```
liblttng-ust.so.0 -> not found!
...
libpam.so.0 -> not found!
```
This patch adds these dependencies
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/xonsh/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/n2hvc59jjmqfww86pqz7w6hmr7wlklbw-xonsh-0.6.6/bin/xon.sh had a zero exit code or showed the expected version
- /nix/store/n2hvc59jjmqfww86pqz7w6hmr7wlklbw-xonsh-0.6.6/bin/.xonsh-wrapped passed the binary check.
- /nix/store/n2hvc59jjmqfww86pqz7w6hmr7wlklbw-xonsh-0.6.6/bin/xonsh passed the binary check.
- 2 of 3 passed binary check by having a zero exit code.
- 2 of 3 passed binary check by having the new version present in output.
- found 0.6.6 with grep in /nix/store/n2hvc59jjmqfww86pqz7w6hmr7wlklbw-xonsh-0.6.6
- directory tree listing: https://gist.github.com/dba795a63cf24871f010baf56dba68d0
- du listing: https://gist.github.com/afde349bcf27d995e595d895941de9de
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/xonsh/versions.
These checks were done:
- built on NixOS
- Warning: no invocation of /nix/store/zdkhffpw9yfjkxi877mildima9kp7skm-xonsh-0.6.4/bin/xon.sh had a zero exit code or showed the expected version
- /nix/store/zdkhffpw9yfjkxi877mildima9kp7skm-xonsh-0.6.4/bin/.xonsh-wrapped passed the binary check.
- /nix/store/zdkhffpw9yfjkxi877mildima9kp7skm-xonsh-0.6.4/bin/xonsh passed the binary check.
- 2 of 3 passed binary check by having a zero exit code.
- 2 of 3 passed binary check by having the new version present in output.
- found 0.6.4 with grep in /nix/store/zdkhffpw9yfjkxi877mildima9kp7skm-xonsh-0.6.4
- directory tree listing: https://gist.github.com/f4e56948f12666dc9fa8965e32e1844e
- du listing: https://gist.github.com/de490af4f1967c7d07e86d7068da2c32
Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/xonsh/versions.
These checks were done:
- built on NixOS
- ran ‘/nix/store/prjh0vgnnn80ba9im4j9minjivsa8bj4-xonsh-0.6.3/bin/.xonsh-wrapped -h’ got 0 exit code
- ran ‘/nix/store/prjh0vgnnn80ba9im4j9minjivsa8bj4-xonsh-0.6.3/bin/.xonsh-wrapped --help’ got 0 exit code
- ran ‘/nix/store/prjh0vgnnn80ba9im4j9minjivsa8bj4-xonsh-0.6.3/bin/.xonsh-wrapped help’ got 0 exit code
- ran ‘/nix/store/prjh0vgnnn80ba9im4j9minjivsa8bj4-xonsh-0.6.3/bin/.xonsh-wrapped -V’ and found version 0.6.3
- ran ‘/nix/store/prjh0vgnnn80ba9im4j9minjivsa8bj4-xonsh-0.6.3/bin/.xonsh-wrapped --version’ and found version 0.6.3
- ran ‘/nix/store/prjh0vgnnn80ba9im4j9minjivsa8bj4-xonsh-0.6.3/bin/xonsh -h’ got 0 exit code
- ran ‘/nix/store/prjh0vgnnn80ba9im4j9minjivsa8bj4-xonsh-0.6.3/bin/xonsh --help’ got 0 exit code
- ran ‘/nix/store/prjh0vgnnn80ba9im4j9minjivsa8bj4-xonsh-0.6.3/bin/xonsh help’ got 0 exit code
- ran ‘/nix/store/prjh0vgnnn80ba9im4j9minjivsa8bj4-xonsh-0.6.3/bin/xonsh -V’ and found version 0.6.3
- ran ‘/nix/store/prjh0vgnnn80ba9im4j9minjivsa8bj4-xonsh-0.6.3/bin/xonsh --version’ and found version 0.6.3
- found 0.6.3 with grep in /nix/store/prjh0vgnnn80ba9im4j9minjivsa8bj4-xonsh-0.6.3
- directory tree listing: https://gist.github.com/c4698aa16268961773b245a4b849a9f0
- du listing: https://gist.github.com/db7c65ccf5f4bf3c4457401c300d1862
Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 2.8 with grep in /nix/store/svgfjl0v59ff90l6h2gzbsplhbk3aqhp-bash-completion-2.8
- directory tree listing: https://gist.github.com/23a9bb8eddc5667ef5a94d69ea7ab340
Semi-automatic update. These checks were done:
- built on NixOS
- Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
- found 0.14.3 in filename of file in /nix/store/2z6cjbqfwc5h5rwz64c3pjd0a008yhp8-grml-zsh-config-0.14.3
Semi-automatic update. These checks were performed:
- built on NixOS
- found 0.4.2 with grep in /nix/store/pgilg1imys99x1i42dslrv4qvqkp0p4d-zsh-autosuggestions-0.4.2
- found 0.4.2 in filename of file in /nix/store/pgilg1imys99x1i42dslrv4qvqkp0p4d-zsh-autosuggestions-0.4.2
cc "@loskutov"
Semi-automatic update. These checks were performed:
- built on NixOS
- found 56c in filename of file in /nix/store/88xmgl9p82fph7d8qqzp48iqvkh688jd-mksh-56c
cc "@AndersonTorres @joachifm"
As-is the use of 'configureFlags="..."' breaks cross compilation
as it drops the configure platforms arguments.
Set zprofile separately to handle $out.
`bash-completion` lazy loads completion scripts by looking up the command name
in the completion directory. As such we need to create a symlink for every
nix command.
The problem had been masked by nixos sourcing all completion scripts on startup.
To use, add this option to your configuration.nix:
`programs.zsh.promptInit = "source ${pkgs.zsh-powerlevel9k}/share/zsh-powerlevel9k/powerlevel9k.zsh-theme";`
As per #30645, fish with fish-foreign-env prints this
(harmless) warning:
```
set: Tried to change the read-only variable “_”
```
This patch was developed by @rnhmjoj in the aforementioned
issue discussion
I don't know where this comes from (I accidentally did that as well
once), but some derivations seem to use `buildPhases` rather than
`phases` in their derivations.
This kills all improper usages as the lack of a `phases` argument
didn't break the build, so this can be safely removed.
The biggest benefit is that we no longer have to update the registry
package. This means that just about any cargo package can be built by
nix. No longer does `cargo update` need to be feared because it will
update to packages newer then what is available in nixpkgs.
Instead of fetching the cargo registry this bundles all the source code
into a "vendor/" folder.
This also uses the new --frozen and --locked flags which is nice.
Currently cargo-vendor only provides binaries for Linux and
macOS 64-bit. This can be solved by building it for the other
architectures and uploading it somewhere (like the NixOS cache).
This also has the downside that it requires a change to everyone's deps
hash. And if the old one is used because it was cached it will fail to
build as it will attempt to use the old version. For this reason the
attribute has been renamed to `cargoSha256`.
Authors:
* Kevin Cox <kevincox@kevincox.ca>
* Jörg Thalheim <Mic92@users.noreply.github.com>
* zimbatm <zimbatm@zimbatm.com>
This requires some small changes in the stdenv, then working around the
weird choice LLVM made to hardcode @rpath in its install name, and then
lets us remove a ton of annoying workaround hacks in many of our Go
packages. With any luck this will mean less hackery going forward.
* First attempt at making elvish compile on darwin
* Fixed cyclic dependency on darwin
This fixes the "cycle detected in the references of" error when building
on darwin. The fix is based on the solution in issue #18131.
* Use version 0.10 and not 0.10.1, which is not officially released yet
I wrote the patch. Unfortunately it's Nix specific because upstream
rejected it because Ubuntu Trusty's version of realpath doesn't seem to
have the `--relative-to` option. (Upstream used to use realpath before).
But for Nix, our version of realpath is recent enough. Also, upstream
will probably use realpath again anyway in May 2019 when Ubuntu Trusty
becomes unsupported, so this patch should probably be used.
* pkgs: refactor needless quoting of homepage meta attribute
A lot of packages are needlessly quoting the homepage meta attribute
(about 1400, 22%), this commit refactors all of those instances.
* pkgs: Fixing some links that were wrongfully unquoted in the previous
commit
* Fixed some instances
This is a plugin of sorts for your `.zshrc` that can add status
information about the current git repository to your prompt. By
default it uses a python script and is thus easy on the dependencies
and not really worth packaging. But there's also a Haskell
implementation. I set it up sometime back, but then it died when the
libgmp version it was compiled with disappeared in a garbage
collection. So I decided that the Haskell version of zsh-git-prompt
might be worth packaging after all.
The file is an example makefile for developing bash plugins, and
contains stuff like:
````
example: example.o
$(SHOBJ_LD) $(SHOBJ_LDFLAGS) $(SHOBJ_XLDFLAGS) -o $@ example.o $(SHOBJ_LIBS)
````
So no package is really going to depend on that, and it's making the
.dev output keep a reference to the bootstrap tools. Just nuke it.
Because if you don't, the configure script assumes that your getcwd()
function is broken. Which then makes bash use it's own getcwd()
implementation, which doesn't work if the path to the current directory
contains bind mounts in its paths. This shows up as:
shell-init: error retrieving current directory: getcwd: cannot access parent directories: Bad file descriptor
... and fails the aarch64 glibc build with sandboxes enabled.
Sigh.
The rssh package did not have the 'shellPath' attribute, so it could not
be used as the default shell for a nixos user. I fixed this by adding
the attribute.
After #16017 there were a lot
of comments saying that `nix` would be better than `JSON`
for Go packages dependency sets.
As said in https://github.com/NixOS/nixpkgs/pull/16017#issuecomment-229624046
> Because of the content-addressable store, if two programs have the
> same dependency it will already result in the same derivation in
> the
> store. Git also has compression in the pack files so it won't make
> much difference to duplicate the dependencies on disk. And finally
> most users will just use the binary builds so it won't make any
> differences to them.
This PR removes `libs.json` file and puts all package dependencies in
theirs `deps.json`.
"This projects aims at gathering/developing new completion scripts that
are not available in Zsh yet. The scripts are meant to be contributed to
the Zsh project when stable enough."
