Bug#934926: [Pkg-zsh-devel] Bug#934926: update (overridding of default fpath causes uncessary complexity and pain for software providing zsh completions)

Axel Beckert wrote: […] >> With that, we could add the prefix based site-functions directory, >> but deprecate its use. > > Ack, that thought came to me also after having read your mail > half-through. It though has the danger that some so far not active > plugins will suddenly start to work. So

Bug#934926: update

Daniel Shahaf wrote: […] > - Packages that are part of Debian should install to > /usr/share/zsh/vendor-*. > > - Upstream packages have three options: > > + Install to /usr/local/share/zsh/site-functions (regardless of their > own $PREFIX _and_ of zsh's $PREFIX) This is precisely the

Bug#970848: Problem with path to completion scripts

Georgy Komarov wrote: > I encountered with a problem, when trying to use custom zsh completions. As debian/README.Debian states: Load-path for functions from other packages --- In respsonse to #620452, the zsh-binary from Debian's zsh package started to

Bug#921236: [Pkg-zsh-devel] Bug#921236: Bug#921236: zsh: provide equivalent of dh_bash-completion

Daniel Shahaf wrote: > [...] and autoloadable > functions (first line is "#autoload") to /usr/share/zsh/vendor-functions; > both of these paths are Debian-specific. I suggest that, at least for > now, you manually install the files to these paths. vendor-functions takes any sort of zsh function

Bug#622933: [Pkg-zsh-devel] Bug#622933: zsh: Enable completions by default, unless skip_global_compinit is set

Hi, TS wrote: [...] > Replying here because i think the patch that never got applied > should look like: In the meantime (it's been more than seven years), I've changed my mind about this. I think a vendor should do as little as possible in their global configuration files. We already do a

Bug#898619: [Pkg-zsh-devel] Bug#898619: Bug#898619: zsh autocompletion does not deal gracefully with upgrades in the background

Axel Beckert wrote: > Philipp Kern wrote: [...] >> My gut feeling is that this is because I did not autocomplete in the >> old shell yet but now the module is gone. > > Yes, that's the same conclusion I came to. > >> At least with a new shell complist.so is only in /proc/$$/maps after >> an

Bug#879187: zsh-completion: add --clean for vim

Hello Christian, Christian Brabandt wrote: [...] > Vim since patchlevel 8.0.0716 includes the --clean argument for starting > in a clean mode (only loading defaults.vim and in non-cp mode). So > please add this patch to the vim completion. [...] > --- _vim.backup 2017-10-20

Bug#859070: [Pkg-zsh-devel] Bug#859070: /bin/zsh: status of resumed background jobs incorrectly listed as 'unknown signal (core dumped)'

Axel Beckert wrote: >> Here's the upstream commit: >> >> commit 12d950ba0cc345d047c94c9d94325dbfe47fc79d >> Author: Barton E. Schaefer >> Date: Thu Feb 23 16:19:07 2017 -0800 > > Indeed looks small. > > Daniel, Frank: Do we have to expect any side effects from >

Bug#844095: fdm: please make the build reproducible

Hi, Reiner Herrmann wrote: > While working on the "reproducible builds" effort [1], we have noticed > that fdm could not be built reproducibly. It collects source files > with "echo *.c", which varies with different locales. This causes a > different order of objects during linking. Thanks!

Bug#844710: Fwd: Re: [Pkg-zsh-devel] Bug#844710: autocorrection suggested rm for typing mr without typing "y"

Hey, Martin Steigerwald wrote: >> On a tangent: what do "nyae" mean? I couldn't find the answer in the >> manual. > > I thought about this as well. This would be: (Y)es, (N)o, (A)bort, (E)dit. Regards, Frank

Bug#843582: 0xffff: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

Package: 0x Version: 0.6.1-3 Severity: normal Dear Maintainer, Debian's zsh package offers a dedicated directory for other packages to put additional completion function files into. That directory is: /usr/share/zsh/vendor-completions 0x seems to use:

Bug#843576: taskwarrior: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

Package: taskwarrior Version: 2.5.1+dfsg-1 Severity: normal Dear Maintainer, Debian's zsh package offers a dedicated directory for other packages to put additional completion function files into. That directory is: /usr/share/zsh/vendor-completions taskwarrior seems to use:

Bug#843581: python3-doit: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

Package: python3-doit Version: 0.28.0-1 Severity: normal Dear Maintainer, Debian's zsh package offers a dedicated directory for other packages to put additional completion function files into. That directory is: /usr/share/zsh/vendor-completions python3-doit seems to use:

Bug#843578: dochelp: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

Package: dochelp Version: 0.1.3+b1 Severity: normal Dear Maintainer, Debian's zsh package offers a dedicated directory for other packages to put additional completion function files into. That directory is: /usr/share/zsh/vendor-completions dochelp seems to use:

Bug#843573: herbstluftwm: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

Package: herbstluftwm Version: 0.7.0-1 Severity: normal Dear Maintainer, Debian's zsh package offers a dedicated directory for other packages to put additional completion function files into. That directory is: /usr/share/zsh/vendor-completions herbstluftwm seems to use:

Bug#843580: autojump: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

Package: autojump Version: 22.5.0-1 Severity: normal Dear Maintainer, Debian's zsh package offers a dedicated directory for other packages to put additional completion function files into. That directory is: /usr/share/zsh/vendor-completions autojump seems to use:

Bug#843575: ninja-build: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

Package: ninja-build Version: 1.7.1-1 Severity: normal Dear Maintainer, Debian's zsh package offers a dedicated directory for other packages to put additional completion function files into. That directory is: /usr/share/zsh/vendor-completions ninja-build seems to use:

Bug#843579: python-doit: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

Package: python-doit Version: 0.28.0-1 Severity: normal Dear Maintainer, Debian's zsh package offers a dedicated directory for other packages to put additional completion function files into. That directory is: /usr/share/zsh/vendor-completions python-doit seems to use:

Bug#843577: nikola: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

Package: nikola Version: 7.6.4-1 Severity: normal Dear Maintainer, Debian's zsh package offers a dedicated directory for other packages to put additional completion function files into. That directory is: /usr/share/zsh/vendor-completions nikola seems to use:

Bug#843574: sup-mail: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

Package: sup-mail Version: 0.22.1-2 Severity: normal Dear Maintainer, Debian's zsh package offers a dedicated directory for other packages to put additional completion function files into. That directory is: /usr/share/zsh/vendor-completions sup-mail seems to use:

Bug#843483: torsocks: Zsh completion should be deployed to /usr/share/zsh/vendor-completions

Package: torsocks Version: 2.2.0-1 Severity: normal Dear Maintainer, Debian's zsh packages offers a dedicated directory for other packages to put additional completion function files into. That directory is: /usr/share/zsh/vendor-completions Torsocks seems to use:

Bug#836580: systemd: systemctl status pipes through less with escape sequences not applied

Hi, Michael Biebl wrote: [...] martin@merkaba:~> systemctl status ^[[0;1;31m●^[[0m merkaba State: ^[[0;1;31mdegraded^[[0m Jobs: 0 queued Failed: 2 units I can't reproduce this. If zsh changed its terminal to behave like that, no

Bug#828180: zsh: $RANDOM number generator is not reset for subshells

Ben Longbons wrote: > Dear Maintainer, Hi Ben, > Zsh just repeats the same number when $RANDOM is requested in fresh > subshells. In general, this sort of bug is a security vulnerability, > though I'm not aware of anyone doing security-sensitive stuff in zsh. This works exactly as documented

Bug#823093: zsh-common: Zsh config files are stored in /etc/zsh instead of /etc/zsh.d, which is more expected by users

Hi, Christopher Slojkowski wrote: > Zsh files are stored in /etc/zsh, they should be stored in /etc/zsh.d instead. > This is more consitant with other directories. I included a patch which makes > the new folder, moves, and creates a symlink. There is proabably a better > solution, but I just

Bug#790535: susv4: fails to install: post-installation script returned error exit status 1

Hello maintainer! I just tried to install the "susv4" package on my system and it revealed the following issue, which I believe was mentioned in the bug id I am reopening right now. Note, that I tried to install "susv2" and "susv3" and neither of those packages had any problems of that kind.

Bug#720707: state of RFP: grml-zsh-config?

Hi, Disclaimer: Even though I am involved with grml's setup a great deal, I never was a big fan of packaging it up for Debian. The reason for that being mainly, that I am absolutely convinced that a vendor should impose the least possible changes to a package as possible and most

Bug#794967: zsh: please enhance /etc/zshrc

Hi! Carsten Hey wrote: * Frank Terbeck [2015-08-08 23:46 +0200]: [...] I firmly believe, that a vendor's *global* setup file should be as minimal as possible, which is why I really don't want to add anything that's more than making the zsh defaults behave more robustly across multiple

Bug#756138: Bug#792703: zsh: please improve newuser.zshrc.recommended and add new prompt_debian_setup

Hi Carsten, I looked through the suggestions from your last mail; comments inline. Carsten Hey wrote: [...] I think #setopt no_beep and #stty -ixon should also be added to The latter might better be replaced by zsh's no_flow_control option. [...] This prompt color-scheme-able via zstyle. If

Bug#794967: zsh: please enhance /etc/zshrc

Carsten Hey wrote: [...] * Please add some additional keybindings, at least for the emacs keymap: - bind PageUp ${terminfo[kpp]} to history-search-backward - bind PageDown ${terminfo[knp]} to history-search-forward - bind BackTabKey ${terminfo[kcbt]} to reverse-menu-complete I

Bug#794968: zsh: please clear console on logout (if recommended config is used)

Carsten Hey wrote: Please clear console on logout if the recommended config for new users is used. I think this should be doable with a zshexit hook like this: function debian_clear_upon_exit () { clear } add-zsh-hook zshexit debian_clear_upon_exit That hook could be

Bug#780531: zsh: tail -F does not complete file names

Hello Sebastian, Sebastian Ramacher wrote: [...] The completion for tail -f correctly completes files, but it does not for tail -F . tail -F tab displays completing -f and and nothing else. I'd also expect to get completing files there. Zsh does not supply a completion function for tail.

Bug#776964: Headers installed by zsh-dev packages miss critical pieces

Hey there! ZyX wrote: [...] To use zsh headers in some module at least `config.h` file is needed Finally, someone who actually wants to use zsh's facilities to load third party modules. Yay. ;) in addition to those already present in the package. `config.h` files contains defines guessed by

Bug#776663: Bug#776663: zsh-common: Wish for /etc/zsh/zprofile.d or equivalent

Tach Axel, Axel Beckert wrote: Hi Frank and Tim, Frank Terbeck wrote: Tim Booth wrote: This is a request on behalf of Bio-Linux and the Debian Med developers. The attached file shows the zshrc used on Bio-Linux, and the part we'd really like to see in the standard zsh-common package

Bug#776663: zsh-common: Wish for /etc/zsh/zprofile.d or equivalent

Hey Tim, Tim Booth wrote: [...] This is a request on behalf of Bio-Linux and the Debian Med developers. The attached file shows the zshrc used on Bio-Linux, and the part we'd really like to see in the standard zsh-common package is support for a zprofile.d configuration directory[...] Is

Bug#776663: zsh-common: Wish for /etc/zsh/zprofile.d or equivalent

Frank Terbeck wrote: [...] you don't need null_glob at all. Thus, I'd do this: for i in /etc/zsh/zshrc.d/*.zsh; do Well, since zsh's default behaviour is to error out with non-matching globs, using the qualifier is actually required: for i in /etc/zsh/zshrc.d/*.zsh(N); do # I'm quoting

Bug#707760: zsh: Alternatives broken for long time during upgrade from zsh4 to zsh5

Frank Terbeck wrote: [...] #!/bin/zsh -f if [[ -o interactive ]]; then [...] This wasn't the smartest idea ever. Since this is a script, it's obviously not interactive invocation, which means that the test always fails. Oh well. I guess we can just warn upon every invocation interactive

Bug#764650: zsh: FTBFS with noatime mounts

Hi Thorsten! Thorsten Glaser wrote: Justification: FTBFS, but maybe m68k are the only ones with noatime? http://buildd.debian-ports.org/status/fetch.php?pkg=zsharch=m68kver=5.0.6-3stamp=1412524530 ../../Test/C02cond.ztst: test failed. The following may (or may not) help identifying the

Bug#707760: zsh: Alternatives broken for long time during upgrade from zsh4 to zsh5

Axel Beckert wrote: Sven Joachim wrote: [...] How about adding a symlink /bin/zsh4 - zsh5 in the zsh package? Not extremely pretty, but it should work. What about putting a shell script at /bin/zsh4 which more or less looks this? #!/bin/sh echo $0 is deprecated, please switch to

Bug#764650: zsh: FTBFS with noatime mounts

Thorsten Glaser wrote: Frank Terbeck dixit: [...] elif test -f /etc/mtab { grep $(df . 2/dev/null| tail -n1 | awk '{print $1}') /etc/mtab | grep -q noatime; }; then [...] Hm, I think this rings a bell. Didn’t we have this on another buildd already, years ago, because something like mtab

Bug#753296: Acknowledgement (mpv completion fails)

Yuri D'Elia wrote: Ahh sorry, I noticed only now that the _mpv function is shipped with mpv itself. Could you reassign it to mpv? The problem you're describing looks like a broken completions-cache file. Before you proceed, try this: % rm ~/.zcompdump % exec zsh And see if the problem

Bug#418199: Fwd: Re: segfault with exceedingly long path [origin: schae...@brasslantern.com]

Goswin von Brederlow wrote: On Sat, Jan 18, 2014 at 10:19:39AM +0100, Axel Beckert wrote: [...] upstream said, this is an issue which is unlikely ever to be fixed. Marking as such. [...] From: Bart Schaefer schae...@brasslantern.com: [...] Various parts of the shell rely on system limits

Bug#733075: zsh: command completion not working after semicolon

Hello Jay! Jay Berkenbilt wrote: Usually when I type a command followed by ;, after the ;, zsh is back to a state where TAB should complete on commands again. This is pretty basic completion behavior. After I upgraded to 5.0.4-1, I observed that this was no longer working. As soon as I

Bug#733075: Bug#733075: zsh: command completion not working after semicolon

Hey Richard! Richard Hartmann wrote: Seems we worked in parallel here; I already confirmed and forwarded to zsh-workers. Seems like it. :-) 5.0.2-6 was not affected. I git-bisected this to: [568e0db7a964feefa45061967d0c7079a0e59c1e] 31611: attempt to fix crash completing redirection in

Bug#727222: debian/patches/38-linux-3.11-sf.patch

The fix James proposes does indeed fix the issue for me. I'm attaching the patch-file I used as debian/patches/38-linux-3.11-sf.patch for convenience. Regards, FrankDescription: Import upstream fix for shared folders with linux 3.11 Apparently, listing directories in shared folders with

Bug#717002: zsh: Update for git-buildpackage completion

Hey, with my pkg-zsh hat on, here are some thoughts: Guido Günther wrote: On Mon, Oct 28, 2013 at 03:50:33PM -0300, Felipe Sateler wrote: On Mon, Oct 28, 2013 at 2:22 PM, Vincent Bernat ber...@debian.org wrote: ❦ 15 juillet 2013 23:27 CEST, Felipe Sateler fsate...@debian.org : [...]

Bug#724721: zsh: Tab completion error with vi

Hi Ludovic, Ludovic Lebègue wrote: [...] While using zsh shell trying to autocomplete with tab key display the following message instead of showing the files in the current directory : ludo@leonardo ~ % vi _arguments:450: _vim_files: function definition file not found Did this happen

Bug#720707: RFP: grml-zsh-config -- zsh configuration that ships with the Debian-based grml distro

Thomas Koch wrote: thank you very much for taking this! Your question about how the zshrc will be provided is so common that I proposed a general solution: http://lists.alioth.debian.org/pipermail/soc-coordination/2012-February/001156.html In short and for the start I'd say: just put the

Bug#692785: zsh: '.zprofice' typo in zshrc

Michael Terry wrote: Package: zsh Version: 5.0.0-2 [...] Ubuntu user Logan Rosen provided the attached patch to fix a typo in debian/zshrc. .zprofice should be .zprofile. Hey there, this does not apply to the debian package, since we don't call `compinit' under any circumstances in the

Bug#685511: zsh: /etc/zsh/zshrc brokes return on numpad

sergio wrote: [...] Version: 5.0.0-2 After upgrade to 5.0 numpad return (KP_Enter) key doesn't work anymore. Yes. This is due to our reimplementation of keyboard handling within the global zshrc file of the 5.0.0 packages. What we did is enable application mode in the terminal, when the line

Bug#666755: [zsh] GnuPG2 completion

Mika Suomalainen wrote: zsh is not automatically completing options for gpg2 (package gnupg). Many gpg2 command line flags are probably same as gpg ones. If so, then the following may be a workaround for your configuration until someone comes up with a full-featured gpg2 completion: compdef

Bug#666168: zsh: Many function definitions are missing zsh-newuser-install, compinit, etc.

Hong Xu wrote: /usr/share/zsh/4.3.17/scripts/newuser:6: zsh-newuser-install: function definition file not found [...] autoload -U compinit compinit [...] zsh: compinit: function definition file not found This sounds like a severely broken installation. Debian's zsh packages do not split the

Bug#666168: zsh: Many function definitions are missing zsh-newuser-install, compinit, etc.

Hong Xu wrote: On 03/29/2012 09:18 PM, Frank Terbeck wrote: [...] print -l $fpath c=( ${^fpath}/compinit(N.) ) (( $#c )) ls -l $c[1] || echo compinit not found [...] It cames up with: /opt/intel/composerxe-2011.5.220/mkl/include compinit not found I have no idea were

Bug#666168: zsh: Many function definitions are missing zsh-newuser-install, compinit, etc.

Hong Xu wrote: On Mar 29, 2012, at 21:59, Frank Terbeck f...@bewatermyfriend.org wrote: [...] In particular, we do NOT have any /opt/intel/... paths in there. I know what's going on here now: intel compiler init scripts change the fpath variable. Is that by chance the Intel Fortran

Bug#663982: zsh: autocompletion does not work anymore after compinit

Martin Steigerwald wrote: auto completion stopped worked since this week. This might be related to an upgrade of Z-Shell. It is related configuration, with an empty .zshrc it works. But with the recommended configuration from the system administrator it does not. I found it to stop working

Bug#658223: zsh: 'man zshmisc' typo: defintions

tags 658223 + fixed-upstream thanks A. Costa wrote: [...] Found a typo in '/usr/share/man/man1/zshmisc.1.gz', see attached '.diff'. Hope this helps... [...] --- zshmisc.1 2012-01-22 18:15:59.0 -0500 [...] Thanks for noticing! Zsh's manual is not in roff format, though. It's in yodl

Bug#463507: Triage

A. Costa wrote: [...] Still there in 'zsh' v4.3.15-1. Example: I typed what's above the carets and the Tab key, then the line looks like: ls -_main_complete:166: permission denied: Please do this: % rm ~/.zcompdump % zsh -f (and in that new shell) % autoload -Uz

Bug#654225: zsh: Multibyte fails when $LANG.utf variable is not set

Just for the record: This issue is fixed upstream by now and will be in the next version of the package. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#654444: zsh: `q' flag for paramater expansion does not work as advertised

Samuel Bronson wrote: Frank Terbeck wrote: Samuel Bronson wrote: [...] | naesten@hydrogen:~/hacking/crawl/crawl-ref/source% echo -n ${(q)$(echo | -e \e)}|hd |  24 27 1b 27                                       |$'.'| | 0004 [...] zsh% printf '%s\n' ${(q)$(echo -e \e)} $'\033

Bug#654225: zsh: Multibyte fails when $LANG.utf variable is not set

Morten Bo Johansen wrote: [...] What you are missing is that you never once tried the combination setting I described as causing problem. Please try to set a non-utf8 _country_ I'd be surprised to see different results with `de_DE' and `POSIX'. locale for the LANG variable together with a

Bug#654225: zsh: Multibyte fails when $LANG.utf variable is not set

Morten Bo Johansen wrote: [...] export LANG=de_DE export LC_ALL=de_DE.utf8 type in e.g. an umlaut character, type backspace to delete it and notice that it is deleted piecemeal by octet. It should happen to you too! Hum. I can reproduce this right now. I'm unsure where I went

Bug#654225: zsh: Multibyte fails when $LANG.utf variable is not set

Frank Terbeck wrote: [...] I can reproduce this right now. I'm unsure where I went wrong before. Now I know. The order in which you have to set LANG and LC_ALL is crucial to reproduce the issue. And the order in my recipe from the last mail is wrong: [...] b) export LANG=de_DE

Bug#654225: Bug#654225: zsh: Multibyte fails when $LANG.utf variable is not set

Michael Prokop wrote: [...] I sadly still can't reproduce it yet, FTR. Mika and I talked about this on IRC. Turns out he had `LC_CTYPE' in his environment, which gets saved by zsh's handling, which prevents the problem. So, the real[tm] recipe is this: a) Start a blank zsh (zsh -f) b)

Bug#654225: PATCH: Restore `LC_ALL' when setting `LANG'

(Cc:ing Upstream) When setting LANG, zsh sets LC_ALL and then goes on to restore all interesting LC_* values after that. Up to now, it did not restore LC_ALL itself, though. That could lead to trouble when setting LC_ALL=something-utf8-ish and after that LANG=something-non-utf8. This was

Bug#654444: zsh: `q' flag for paramater expansion does not work as advertised

Samuel Bronson wrote: [...] , | q | Quote the resulting words with backslashes; unprintable or invalid | characters are quoted using the $'\NNN' form, with separate quotes | for each octet. [...] ` Unfortunately, the second clause seems to be only half correct;

Bug#654225: zsh: Multibyte fails when $LANG.utf variable is not set

Morten Bo Johansen wrote: I could not get multibyte support to work in zsh, even if I had a, what seemed to me, perfectly working utf-8 environment. I then checked the output from the locale command and noticed that all my LC_.* variables were set to da_DK.utf8 whereas the $LANG variable

Bug#654225: zsh: Multibyte fails when $LANG.utf variable is not set

Morten Bo Johansen wrote: [...] I attach my rather small zshrc. Nothing in that file is relevant to this issue. ~/.zshenv is a symlink to ~/.environment which just set a lot of environment variables. It is there that I now specifiy the LANG variable which makes zsh behave correctly. That

Bug#648246: fdm: FTBFS(kfreebsd): Unable to configure for GNU/kFreeBSD

Sorry for the delay; hardware died on me... Robert Millan wrote: The rest of the blob is OK but mremap() is Linux-specific. I'll take your word for it. Here's a fixed patch (tested and known to build). Thanks, applied to https://github.com/ft/debian_fdm/. Btw, instead of shipping your own

Bug#648246: fdm: FTBFS(kfreebsd): Unable to configure for GNU/kFreeBSD

Robert Millan wrote: 2011/11/9 Frank Terbeck f...@bewatermyfriend.org: +    Linux|GNU/k*BSD) Maybe better use: Linux|GNU|GNU/*) this way it works on GNU/Hurd and possibly other GNU-ish systems. Fine by me. Do you happen to know whether this actually fixes the build on kfreebsd? If it does

Bug#631689: Bug#639176: fdm: diff for NMU version 1.6-4.1

gregor herrmann wrote: I've prepared an NMU for fdm (versioned as 1.6-4.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Hey gregor, I actually got an updated package ready since about a month. I just didn't get to asking my sponsor to upload it yet.

Bug#639176: Bug#631689: Bug#639176: fdm: diff for NMU version 1.6-4.1

gregor herrmann wrote: On Wed, 09 Nov 2011 18:41:51 +0100, Frank Terbeck wrote: [...] I'm unsure about what the procedure is now that you got an NMU in the pipeline. [...] minor things I'd change (e.g. remove the quilt build-dep) [...] Yes, good point. I should have done that, when I removed

Bug#648246: fdm: FTBFS(kfreebsd): Unable to configure for GNU/kFreeBSD

Hi there, Christoph Egger wrote: Package: src:fdm Version: 1.6+cvs20111013-1 [...] Your package failed to build on the kfreebsd-* buildds: [...] test -f config.mk || sh configure Unable to configure for GNU/kFreeBSD Yeah well, `fdm' uses a simple configure script now to setup the build for

Bug#646046: manual page still refers to /etc/zshenv

Norbert Kiesel wrote: man zsh says Commands are first read from /etc/zshenv; this cannot be overridden., but this was changed to /etc/zsh/zshenv at some point. Likewise for zprofile, zlogin, and zshrc. Hey Norbert, This is actually a build-time option. `--enable-etcdir=' to be specific.

Bug#645112: Full error message and a patch from Ubuntu

Sven Joachim wrote: | checking for library containing tigetflag... no | checking for library containing tgetent... no [...] Ubuntu has hit this bug as well, see [1]. The attached patch against git is stolen from [2], with the commit message edited to close the Debian bug for your

Bug#176626: screen: mini-curses type of interface for screen -r w/ multiple screens?

Axel Beckert wrote: [...] zsh, at least with grml's zshrc, allows proper tab completion for screen sessions: There is nothing special about this completion (because you mentioned a certain setup file). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#578466: Shouldn't correct to rm too easily

A. N. Other wrote: You can use the variable CORRECT_IGNORE to exempt commands from correction. E.g.: CORRECT_IGNORE=_*|rm I'm firmly against doing such configuration in the global configuration file (which is doing too much already - but that's another problem). It is something the user

Bug#639176: fdm: FTBFS: unsatisfiable build-dependency: tdb-dev (= 1.1.1~svn26294-1.1) (versioned dep on a virtual pkg?)

[...] The following packages have unmet dependencies: sbuild-build-depends-fdm-dummy : Depends: tdb-dev (= 1.1.1~svn26294-1.1) Right. That should be replaced with libtdb-dev nowadays, I guess. I'll be preparing an updated package as soon as spare time permits. Regards, Frank -- To

Bug#631689: fdm: FTBFS with ld --as-needed

Ilya Barygin wrote: [...] The package fails to build when --as-needed linker option is enabled, because of incorrect order of parameters passed to ld. Here's a log of failed build in Ubuntu:

Bug#634609: zsh: debian/control uses hardcoded list of non-Linux architectures

Robert Millan wrote: [...] Build-Depends: libfoo-dev [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386] vs. Build-Depends: libfoo-dev [linux-any] Please consider making this adjustment to make life easier for future porting efforts. I guess

Bug#634609: zsh: debian/control uses hardcoded list of non-Linux architectures

Robert Millan wrote: Build-Depends: libfoo-dev [linux-any] Sorry, I read your mail way too quickly. Using one positive architecture specification is definitely preferable to several negated ones. So, here's a patch on top of the previous ones, which should do the trick (really, this time):

Bug#632140: PATCH: _aptitude: Completion for -F format specifiers

From: Daniel Bolton d...@dbbo.us Received via the Debian BTS: #632140 Thanks! --- Completion/Debian/Command/_aptitude | 35 ++- 1 files changed, 34 insertions(+), 1 deletions(-) diff --git a/Completion/Debian/Command/_aptitude

Bug#630906: git-annex completion gone missing

Joey Hess wrote: bash does not complete git antab, or git annex getab but it does complete git annex get somefiletab with filenames, which is all that's really needed. Here is an update: Tonight I kicked the following series towards zsh-workers:

Bug#631795: PATCH: _apt: add markauto and unmarkauto sub-commands

From: Sebastian Ramacher s.ramac...@gmx.at Received via Debian BTS #631795: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631795 Thanks! --- Completion/Debian/Command/_apt |4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/Completion/Debian/Command/_apt

Bug#630906: git-annex completion gone missing

Joey Hess wrote: The basic git-annex completion that was added to partially fix #603503 has gone missing, now zsh can neither complete git anntab, nor can it complete git annex foo somefiltab Just to let you know this didn't fall through the cracks... The 4.3.12 release of zsh includes a

Bug#630906: git-annex completion gone missing

Joey Hess wrote: Frank Terbeck wrote: [...] Out of curiosity, is there a git-annex completion for bash? And if so, how does the bash crowd handle such third-party addons? bash does not complete git antab, or git annex getab but it does complete git annex get somefiletab with filenames

Bug#630987: Bug#630987: Tab-completion is totally broken

Axel Beckert wrote: [...] http://iki.fi/juhtolv/configs/shellrc/ Thanks. That may help later with debugging the issue. Actually, what I'd be way more interested in, is if the zsh defaults plus compsys trigger the problem, too: % zsh -f % autoload -Uz compinit % compinit ...and then, in that

Bug#623522: screen tab completion should allow /dev/ devices

f8337312651a496c7f16a1218fb276cc9439b6f7 Mon Sep 17 00:00:00 2001 From: Frank Terbeck f...@bewatermyfriend.org Date: Thu, 21 Apr 2011 19:47:00 +0200 Subject: PATCH: _screen: support /dev/ttyUSB0 [baud] arguments This fixes debian bug #623522: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623522 Regards, Frank --- Completion

Bug#623522: screen tab completion should allow /dev/ devices

Frank Terbeck wrote: Joey Hess wrote: Screen supports being run like: screen /dev/ttyUSB0 [baud], so it would be nice if zsh would not block tab completion in /dev. Agreed. I'll be committing the following upstream in a minute (or five): I've done that. We're approaching a 4.3.12 release

Bug#622933: zsh: Enable completions by default, unless skip_global_compinit is set

Daniel Hahler wrote: In Ubuntu, the attached patch was applied to achieve the following: - debian/zshrc: Enable completions by default, unless skip_global_compinit is set Daniel informed me of this patch on IRC. I think it's a reasonable thing to have. I'd just do it slightly

Bug#622933: zsh: Enable completions by default, unless skip_global_compinit is set

Frank Terbeck wrote: Daniel Hahler wrote: [...] ((#i)on|yes|enable|1) ;; [...] Comments? (#i) requires `extended_glob' to be set, which may or may not be the case. I could make it work properly but it's too much work. We should drop the (#i) and live with the fact that the check is case

Bug#622933: zsh: Enable completions by default, unless skip_global_compinit is set

Daniel Hahler wrote: (( ${+parameters[skip_global_compinit]} )) unset skip_global_compinit I suggest leaving this variable set, instead of unsetting it. This way it could get used in a user's zshrc file for example, like when we're on Debian/Ubuntu and skip_global_compinit is not set, then

Bug#620452: no place for packaged zsh libs

marc chantreux wrote: I would like to make a zshlib-foo.deb file to install a zsh written library in a path handled by the default $fpath. /usr/local/share/zsh/site-functions is for the local admin stuff. /usr/share/zsh/functions/* are for stuff distributed with zsh. i would really

Bug#613162: zsh: Loading colors script fails, bad set of key/value pairs

Frank Terbeck wrote: [...] Yes, I'll probably commit either this or (more likely) a shorter patch that uses emulate -L zsh on top of the function upstream tonight or sometime tomorrow. http://zsh.cvs.sourceforge.net/viewvc/zsh/zsh/Functions/Misc/colors?r1=1.6r2=1.7view=patch

Bug#613162: zsh: Loading colors script fails, bad set of key/value pairs

Frank Terbeck wrote: [...] My suspicion is that this is an effect of an option. Could it be, that you're setting the `ksharrays' option? I strongly suspect that you do. [...] This supports my claim: zsh% zsh -fc 'autoload -U colors; colors' zsh% zsh -f -o ksh_arrays -c 'autoload -U colors

Bug#613162: zsh: Loading colors script fails, bad set of key/value pairs

Benjamin Peter wrote: Frank Terbeck wrote: [...] My suspicion is that this is an effect of an option. Could it be, that you're setting the `ksharrays' option? I strongly suspect that you do. [...] # Arrays should start with zero! setopt KSH_ARRAYS :-) Thanks for your help of figuring my

Bug#613162: zsh: Loading colors script fails, bad set of key/value pairs

Benjamin Peter wrote: $ autoload -U colors $ colors colors:89: bad set of key/value pairs for associative array Commenting out the following line helps: /usr/share/zsh/functions/Misc/colors 89 colour=(${(kv)color}) # A case where ksh namerefs would be useful ... Any idea why this fails?

Bug#613162: zsh: Loading colors script fails, bad set of key/value pairs

Benjamin Peter wrote: [...] (dedeibel@jet)(262/pts)(14:25:13.02.11)- (%:~)- print ${#color} 4 Yeah. I was a little quick about this. This only prints the number of key-value pairs in the associative array. What we're actually looking for is this: % print ${#${(kv)color}} In any case, `4' is

Bug#613162: zsh: Loading colors script fails, bad set of key/value pairs

Benjamin Peter wrote: [...] (%:~)- (set -x; colors;) 21 | cat -v +/bin/zsh:3 colors +colors:4 typeset -Ag color colour +colors:6 color=( 00 none 01 bold 02 faint 22 normal 03 standout 23 no-standout 04 underline 24 no-underline 05 blink 25 no-blink 07 reverse 27 no-reverse 08 conceal 28

Bug#613162: zsh: Loading colors script fails, bad set of key/value pairs

Benjamin Peter wrote: On 02/13/2011 04:50 PM, Frank Terbeck wrote: [...] % printf '%s = '\''%s'\''\n' ${(kv)color} | sort Not sure if this does what it was inteded to. $ printf '%s = '\''%s'\''\n' ${(kv)color} | sort = '' ' ${(kv)color} | sortnone = '' Yes, for you it doesn't

Bug#603503: numerous infelicities in git completion

Joey Hess wrote: Michael Prokop wrote: 1. git log completes only branches, but not filenames. I try to do `git log Foo/Bartab` all the time. 2. git diff ditto Both seem to work now, although rather slowly in large repositories. The guy who wrote large parts of the git completion

Bug#611175: PATCH: Fix for vcs_info's svn detection

Let's try this again, shall we? Apparently, it's harder to use an email client than it looks. Also, as Mikael informs me on IRC, I screwed up the patch in the first mail... *sigh* ...now that CVS is back... Here's a fix for an issue with vcs_info's subversion detection, which was reported in the

  1   2   >