Bug#347801: vim-runtime: syntax highlighting for slrnrc doesn't know a few function names

Package: vim-runtime Version: 1:6.4-006+1 Severity: minor Tags: patch When I was reviewing my slrn configurationfile, I realized that vim did not recognize all functions bindable with setkey. The unknown functions were: readline functions: complete, cycle, delbol, delbow article function: toggle

Bug#405355: PATCH: _aptitude

Clint Adams <[EMAIL PROTECTED]>: > > +function _aptitude_release() { > > + #{{{ > > + local expl releases > > + releases=( > > +${${(M)${(f)"$( > +:#[ $'\t']#deb(|-src)*}/(#b)[ $'\t']#[^ $'\t']##[ $'\t']##[^ $'\t']##[ > > $'\t']##([^ $'\t']##)*/$match[1]} > > + ) > > + _wanted list expl relea

Bug#405355: zsh: updated _aptitude

Package: zsh Version: 4.3.2-25 Severity: wishlist Tags: patch Hi, I submitted an update for _aptitude to zsh-workers in October of last year, which has was ignored. I've been using this updated completion since then without problems. So, I'm resubmitting the patch to you, because I guess you are m

Bug#407294: cmus 2.1.0 available. Please update

Package: cmus Version: 2.0.4-1 Severity: wishlist Version 2.1.0 of cmus is available¹. Updating would fix #399965 as well as #378194. So, I guess that would be a good idea. Maybe you already know about this and just want to wait until after etch is released. If so, feel free to ignore me. :-) Re

Bug#400576: wyrd: respect setting of $VISUAL in default config

Package: wyrd Version: 1.4.1-2 Severity: minor Tags: patch The current default wyrdrc uses $EDITOR as its main source for information about the desired editor. Many people set editor to a line-oriented editor like 'ed' and $VISUAL to their prefered fullscreen editor. The included patch uses $VISU

Bug#419048: ITP: fdm -- fetching, filtering and delivering emails

Package: wnpp Severity: wishlist Owner: Frank Terbeck <[EMAIL PROTECTED]> * Package name: fdm Version : 1.1 Upstream Author : Nicholas Marriott <[EMAIL PROTECTED]> * URL : http://fdm.sf.net * License : ISC Programming Lang: C Description

Bug#419089: groff -mdoc warns about unknown keyword '-ragged' in .Bd macro.

Package: groff Version: 1.18.1.1-12 Severity: normal When packaging fdm¹, lintian told me about a warning in one of the program's manpages: [snip] fdm: manpage-has-errors-from-man usr/share/man/man5/fdm.conf.5.gz Unknown keyword `-ragged' in .Bd macro (#590) [snap] I can reproduce this using bo

Bug#394818: zsh: _tar_archive and GNU tar fails to complete uncompressed archives

Package: zsh Version: 4.3.2-21 Severity: normal This bug was reported upstream in ZW#22584¹ and is fixed in the upstream CVS. Please include the updated version in the debian package. Regards, Frank ¹ -- System Information: Debian Release: tes

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#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 : >> [...] Various parts >> of the shell rely on system limits such as PATH_MAX

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 wrote: >> > ❦ 15 juillet 2013 23:27 CEST, Felipe Sateler : [...] >> >> Unfortunately my completion foo

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 lin

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 . > Btw, instead of shipping your

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 t

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 lin

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                                       |$'

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#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

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 yod

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 conveni

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#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: > > https://launchpadlibrarian.net/71869810/buildlog_ubuntu-oneiric-i386.fdm_1.6-4build1_FAILEDTOBUILD

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#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

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#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 s

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

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

Robert Millan wrote: > 2011/11/9 Frank Terbeck : >> +    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 kfreeb

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 variabl

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#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 u

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=

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 reporte

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 correc

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 work

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

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/incl

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 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 Int

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 sp

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#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: /usr/share/zsh/functions/

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: /usr/share/zsh/functions/

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: /usr/share/zsh/functions/Compl

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: /usr/share/zsh/func

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: /usr/share/zsh/functions/Co

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: /usr/share/zsh/fun

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: /usr/share/zsh/fu

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: /usr/share/zsh/functions/

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: /usr/share/zsh/funct

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: /usr/share/zsh/

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: /usr/share/zsh/functions/Compl

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 zsty

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-comple

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 inst

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

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 crea

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 and

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 proble

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/

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 w

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 b

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 " displays "completing -f" and and nothing else. I'd > also expect to get "completing files" there. Zsh does not supply a completion function for

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=zsh&arch=m68k&ver=5.0.6-3&stamp=1412524530 > > ../../Test/C02cond.ztst: test failed. > The following may (or may not) help identifying

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, plea

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

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 invoca

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 c

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. Re

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#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! Comme

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 c

Bug#460302: usr/include/tdb.h uses sig_atomic_t without including signal.h

Is this bug going to be dealt with anytime soon? Regards, Frank -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#367823: zsh: segfault when completing arrays

Package: zsh Version: 4.3.2-8 Severity: normal Howdy. zsh 4.3.2 crashes with sig11 when doing the following: [snip] % zsh -f % autoload compinit; compinit % array=( 5 4 3 2 1 ) % print $array[4] ^- place your cursor here and hit [snap] I've tested this on a sarge system with zsh

Bug#367823: zsh: segfault when completing arrays

Peter Stephenson <[EMAIL PROTECTED]>: > Clint Adams wrote: [...] > > Should zlemetaline be 0 or should zleline + zlemetacs be non-zero? > > I suspect it's just a typo... > > Index: Src/Zle/zle_params.c [...] > - return dupstrpfx((char *)zleline + zlemetacs, zlemetall - zlemetacs); > + retu

Bug#523673: fdm: new upstream release

Ritesh Raj Sarraf : [...] > Even though fdm's popcon stats are very low, I gave it a shot. Well, popcon is no real measurement. :) > And must say, it is really a nice software. > > Couldn't find any bugs in it, :-) That sounds like you actually looked for bugs, which makes this even better. >

Bug#525121: fdm: leave mail on server

Ccing the fdm-users mailing list, for additional input on the 'only' option, which I have no real experience with; and maybe inside about a possible new upstream release. Please reply to all addresses in To: and Cc: in order to keep all involved parties and the debian BTS in the loop. Here is th

Bug#525121: fdm: leave mail on server

Nicholas Marriott : > fdm doesn't keep track of mail it has seen unless you tell it to. Due > to limitations in POP3 it requires a separate cache file (IMAP does > not require one). Look for new-only and old-only in the manual, IIRC > they have been there since about 1.4... I've been slacking on fd

Bug#526614: fdm dies trying to deliver via | sendmail

[ Ccing the fdm-users mailing list. Please reply to all addresses in ] [ To: and Cc: in order to keep all involved parties and the debian ] [ BTS in the loop. ] Ian Zimmerman : > Package: fdm > Version: 1.5-3 > Severity: normal > > I tried to ma

Bug#526614: fdm dies trying to deliver via | sendmail

Nicholas Marriott : > Yes, it is probably because it is setuid. fdm calls kill(pid, 0) to see if the > process has actually started. This isn't actually needed, it is a debugging > aid. In any case, if it gets EPERM it is probably safe to assume the process > does exist. Please try this diff: Ian,

Bug#526614: fdm dies trying to deliver via | sendmail

I will _not_ go ahead and ask for an upload to stable without this patch being tested. And since the original reporter backed out before doing that... Anyway, I'll attach the patch provided by Nicholas - tweaked a little to work with quilt - to this message. Anyone who wants to test it, is welcome

Bug#531690: fdm: duplicate messages delivery to the actual mailbox fails sometimes

Ritesh Raj Sarraf : > I have discussed this issue with upstream and we believe there is a bug > in fdm when delivering acutal messages to mailboxes for which, in its > cache, it detects that it is a duplicate. This issue is intermittent and > hard to reproduce. Since the discussion about that prob

Bug#538194: fdm doesn't handle EXDEV when linking files.

[ Ccing the fdm-users mailing list. Please reply to all addresses in ] [ To: and Cc: in order to keep all involved parties and the debian ] [ BTS in the loop. ] A new bug report via the debian BTS, which includes a suggestion for a fix. The refe

Bug#497663: Tab completion for vim is broken

Clint Adams <[EMAIL PROTECTED]>: > On Thu, Sep 04, 2008 at 12:05:05PM +0300, Arto Jantunen wrote: > > >> Typing vim and pressing tab produces the following output: > > >> > > >> _vim:31: unmatched ' > > >> > > >> Commenting out lines 31-40 in > > >> /usr/share/zsh/functions/Completion/Unix/_vim f

Bug#456871: fdm: diff for NMU version 1.4-1.1

[EMAIL PROTECTED]: > The following is the diff for my fdm 1.4-1.1 NMU. Okay, but see below > The fixed tdb-dev has just been uploaded. I know, I was subscribed to that bug. > --- fdm-1.4/debian/control > +++ fdm-1.4/debian/control [...] > -Build-Depends: debhelper (>= 5), libssl-dev, zlib1g-dev

Bug#456871: fdm: diff for NMU version 1.4-1.1

Thomas Viehmann <[EMAIL PROTECTED]>: > On 2008-03-09 16:02:37.00 Frank Terbeck <[EMAIL PROTECTED]> wrote: [...] >> The new package is ready and I will ask my mentor to upload it as soon >> as the fixed tdb-dev package hits the mirrors and I can run some >> test

Bug#595057: Denial of service on systems running fdm

Hubert Kario wrote: > Package: fdm > Version: 1.5-3 > Severity: critical > Justification: breaks unrelated software > > When recieving e-mail with attachments sent from my ISP webmail fdm > starts eating all avaiable memory. > > Just after 10 seconds it allocates over 300MiB, when over 5GB are > al

Bug#611175: zsh: VCS_INFO wrongly detects svn repositories

Lennart Weller wrote: > Currently zshs VCS_INFO function wrongly detects svn repositories if > an .svn directory exists in the current path. Which also applies to > home directories containing for example a ~/.svn/authors file. That's a good point... > Instead of checking only for the directory i

Bug#611175: zsh: VCS_INFO wrongly detects svn repositories

Lennart Weller wrote: > On 27.01.2011 16:58, Frank Terbeck wrote: >> That sounds reasonable. Do you know how stable the "entries" file is >> within the .svn directories with respect to versions? Ie. Does it exist >> in old versions as well as in recent ones

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

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 th

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' i

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

Benjamin Peter wrote: [...] > (%:~)- (set -x; colors;) 2>&1 | 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 conce

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&#

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_arr

  1   2   >