[Bash-completion-devel] Bug#487571: marked as done (bash-completion: fails to complete vim /et[tab])

Your message dated Mon, 23 Jun 2008 05:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#487571: fixed in bash-completion 20080617.3 has caused the Debian Bug report #487571, regarding bash-completion: fails to complete vim /et[tab] to be marked as done. This means that you cla

[Bash-completion-devel] Bug#487616: marked as done (bash-completion: sed error when autocompleting for emacs)

Your message dated Mon, 23 Jun 2008 05:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#487571: fixed in bash-completion 20080617.3 has caused the Debian Bug report #487571, regarding bash-completion: sed error when autocompleting for emacs to be marked as done. This means tha

[Bash-completion-devel] Bug#487535: marked as done ([bash-completion] )

Your message dated Mon, 23 Jun 2008 05:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#487571: fixed in bash-completion 20080617.3 has caused the Debian Bug report #487571, regarding [bash-completion] to be marked as done. This means that you claim that the problem has been

[Bash-completion-devel] Accepted bash-completion 20080617.3 (source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 23 Jun 2008 07:24:21 +0200 Source: bash-completion Binary: bash-completion Architecture: source all Version: 20080617.3 Distribution: unstable Urgency: low Maintainer: Bash Completion Maintainers <[EMAIL PROTECTED]> Changed-By: L

[Bash-completion-devel] Bug#487609: marked as done (bash-completion: sed error when autocompleting for evince)

Your message dated Mon, 23 Jun 2008 05:32:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#487571: fixed in bash-completion 20080617.3 has caused the Debian Bug report #487571, regarding bash-completion: sed error when autocompleting for evince to be marked as done. This means th

[Bash-completion-devel] Processed: merging 487571 487609 487616

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.30 > merge 487571 487609 487616 Bug#487571: bash-completion: fails to complete vim /et[tab] Bug#487609: bash-completion: sed error when autocompleting for evince Bug#487616: bash-completi

[Bash-completion-devel] Bug#487616: bash-completion: sed error when autocompleting for emacs

Package: bash-completion Version: 20080617.2 Severity: normal I enter $ emacs \t and get sed: can't read /e: No such file or directory sed: can't read c/bash_comple: No such file or directory sed: can't read io: No such file or directory Kevin -- System Information: Debian Release: lenny/sid

[Bash-completion-devel] Bug#487571: bash-completion: Attached patch fixes this problem

Package: bash-completion Version: 20080617.2 Followup-For: Bug #487571 This attached patch also fixed this problem for me. (Not only /etc/ was affected; vim seemed broken. ls and cd could use completion without trouble before, so be careful how you test the problem report and bug fix.) Thanks fo

[Bash-completion-devel] Bug#487571: bash-completion: Bug and patch confirmation.

Package: bash-completion Version: 20080617.1 Followup-For: Bug #487571 I just wanted to confirm both the bug and the patch (I have the bug and it's fixed applying the patch). Thank you. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (99,

[Bash-completion-devel] Bug#487609: bash-completion: sed error when autocompleting for evince

Package: bash-completion Version: 20080617.2 Severity: normal currently bash autocompletion fails for evince and kpdf. the error is: sed: -e expression #1, char 20: unterminated address regex to reproduce this, do $ touch file.pdf $ evince fi autocompletion seems to work just fine for appli

Re: [Bash-completion-devel] Ubuntu (new upstream) bash-completion

On Sun, 22 Jun 2008 22:46:56 +0200, Luk Claes wrote: > David Paleino wrote: > > > Sorry for all the work this will bring (and, what's worst, I'm going on VAC > > next week, and won't have any internet connection for ~2 months... :() > > That's really unfortunate as the freeze is near and we prob

[Bash-completion-devel] Processed: merging 487535 487571

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.30 > merge 487535 487571 Bug#487535: [bash-completion] Bug#487571: bash-completion: fails to complete vim /et[tab] Merged 487535 487571. > End of message, stopping processing here. Ple

Re: [Bash-completion-devel] Ubuntu (new upstream) bash-completion

David Paleino wrote: > On Fri, 20 Jun 2008 03:31:34 -, Ubuntu Merge-o-Matic wrote: > >> This e-mail has been sent due to an upload to Ubuntu of a new upstream >> version which still contains Ubuntu changes. > > After reading its changelog, I believe we should really merge those changes... Th

Re: [Bash-completion-devel] New upload ready

David Paleino wrote: > Luk, when you can, take a look at rev1120. It adds a new package, > dh-bash-completion, which provides /usr/bin/dh_bash-completion... you know the > story. > > I've marked this as 20080617.2. I disabled the new package for now as you might have seen as it would end up in NE

[Bash-completion-devel] Processed: tagging 487571

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.30 > tags 487571 confirmed pending Bug#487571: bash-completion: fails to complete vim /et[tab] There were no tags set. Tags added: confirmed, pending > End of message, stopping processin

Re: [Bash-completion-devel] Ubuntu (new upstream) bash-completion

On Fri, 20 Jun 2008 03:31:34 -, Ubuntu Merge-o-Matic wrote: > This e-mail has been sent due to an upload to Ubuntu of a new upstream > version which still contains Ubuntu changes. After reading its changelog, I believe we should really merge those changes... Guys, I'm sorry for the buggy ver

[Bash-completion-devel] Bug#487571: bash-completion: fails to complete vim /et[tab]

Package: bash-completion Version: 20080617.2 Severity: normal Hi There seems to be another issue in bash-completion 20080617.2 with expanding arguments for "vim /et[tab]". $ bash -x $ vim /et+ local IFS cur xspec + IFS='\t\n' + COMPREPLY=() ++ _get_cword ++ local i ++ local LC_CTYPE=C ++ local

[Bash-completion-devel] Bug#487544: marked as done (bash-completion: bash completion does not work at all)

Your message dated Sun, 22 Jun 2008 18:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#487449: fixed in bash-completion 20080617.2 has caused the Debian Bug report #487449, regarding bash-completion: bash completion does not work at all to be marked as done. This means that y

[Bash-completion-devel] Bug#487449: marked as done (bash-completion: Wrong directory name completion)

Your message dated Sun, 22 Jun 2008 18:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#487449: fixed in bash-completion 20080617.2 has caused the Debian Bug report #487449, regarding bash-completion: Wrong directory name completion to be marked as done. This means that you cl

[Bash-completion-devel] Accepted bash-completion 20080617.2 (source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 22 Jun 2008 19:47:23 +0200 Source: bash-completion Binary: bash-completion Architecture: source all Version: 20080617.2 Distribution: unstable Urgency: low Maintainer: Bash Completion Maintainers <[EMAIL PROTECTED]> Changed-By: L

[Bash-completion-devel] Bug#487544: Bug#487544: bash-completion: bash completion does not work at all

forcemerge 487544 487449 tags 487449 patch thanks On Sun, 22 Jun 2008 17:03:13 +0200, Norbert Preining wrote: > Package: bash-completion > Version: 20080617.1 > Severity: grave > Justification: renders package unusable > > > With that release the bash completion stopped working completely. Thi

[Bash-completion-devel] Processed: Re: Bug#487544: bash-completion: bash completion does not work at all

Processing commands for [EMAIL PROTECTED]: > forcemerge 487544 487449 Bug#487544: bash-completion: bash completion does not work at all Bug#487449: bash-completion: Wrong directory name completion Forcibly Merged 487449 487544. > tags 487449 patch Bug#487449: bash-completion: Wrong directory name

[Bash-completion-devel] Bug#487544: bash-completion: bash completion does not work at all

Package: bash-completion Version: 20080617.1 Severity: grave Justification: renders package unusable With that release the bash completion stopped working completely. An example: $ ls a/ foo/ bar/ $ ls a/foo/ aa bb $ ls a/bar/ cc dd $ ls a

[Bash-completion-devel] Bug#487535: [bash-completion]

Package: bash-completion Version: 20080617.1 Severity: normal bash-completion seems to be broken with vi and vim. As far as I can see, it works normally with nano, cat, etc... example: trying to do "# vi /e[tab]" = # vi /esed: can't rea