Re: [Bash-completion-devel] bash completion for gdb doesn't work on filenames
On Mon, 12 May 2008 21:45:05 +0100 (BST), Reuben Thomas wrote: On Sun, 11 May 2008, David Paleino wrote: It works for me: [..] This works for me. However, $ cd /usr $ gdb src[TAB] [no response] Still unreproducible here, sorry: $ cp /bin/echo /usr/src/ $ cd /usr/ $ gdb src[TAB] $ gdb src/ $ gdb src/e[TAB] $ gdb src/echo GNU gdb 6.8-debian [..] Please check if you have bash-completion installed (yes, that's the package name!) :) I do. I'm sorry if that seemed like a joke -- it's just that bash-completion has been recently split from bash -- it might be not installed. Would you please report the output of: $ grep \$Id: /etc/bash_completion Thanks, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] bash-completion: side-by-side comparison in upgrade process doesn't return
tags 478659 unreproducible severity 478659 minor thanks Hi Sami, On Wed, 30 Apr 2008 09:03:55 +0200, sami sami wrote: Package: bash-completion Version: 20060301-4 Severity: normal - Upgrading bash-completion hangs (100% CPU use) and doesn't return when invoking side-by-side comparison with existing conffile, I finally stop it with ctl+c and installed it without side-by-side comparison. - classical comparison hangs too but works fine. This seems like a bug in the diff tool you're using, not a bash-completion one. In fact, I can't actually reproduce it. Would you please give use more info? Can you still reproduce it? Thanks, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] bash: File completion bug with executables inside a control structure
fixed 131101 20060301-4 thanks Hi Ajay, hi Peter, On Sun, 27 Jan 2002 13:12:54 +0530, Ajay Shah wrote: The . directory is not on my PATH. I happened to have an executable named 'pauseplay' in the . directory. In bash, if I say $ pause[TAB] bash behaves correctly -- there is no executable starting with 'pause' on my $PATH. But if I say $ while [ 1 ] ; do pause[TAB] bash wrongly completes this! :) He should force me to say $ while [ 1 ] ; do ./pau[TAB] which is consistent with $PATH. On 16 Jul 2002 19:57:41 +1000, Peter Moulder wrote: A hacky fix is to define a custom completion for do and then (and perhaps xargs, env, su etc. at the same time). [..] This has been fixed in newer versions of bash (and bash-completion, which has been split from bash in February 2008). In particular, you won't find it in 20060301-4 (the current testing/unstable version), but I can't really say which was the first version fixing this. Thanks for your report, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] bash: tab completion fails with awk error when first arg is gdb and second arg is subshell expansion
fixed 314363 20060301-4 thanks It's been fixed a long time ago upstream :) David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] bash completion acts weird on dpkg-source
tags 366899 = confirmed thanks (using possible new address for Jonas) On Sat, 17 May 2008 11:04:47 +0200, Frank Küster wrote: David Paleino [EMAIL PROTECTED] wrote: What you're trying to do is using /usr (or trunk) as output directories, while dpkg-source (and its completion), correctly thinks they're Debian Source Packages (and that's why it adds a space at the end -- trunk and not trunk/; /usr and not /usr/). No, that's not what I'm trying to do. I'm trying to unpack a dsc that is in a different directory: ACK (sorry I didn't think that). Tagging the bug as confirmed -- hope we can fix it :) Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#486702: bash-completion: Fails to upgrade
On Tue, 17 Jun 2008 21:16:23 +0200, Helge Kreutzmann wrote: Package: bash-completion Version: 20060301-4 Severity: important (I think this is serious, but I'm not sure so I leave this as important; the version is taken from dpkg -l). I think important is ok -- I'll leave other team members decide. :) I tried to update bash (via apt-get dist-upgrade) and it prompted me with the following debconf screen (output reformatted): Package configuration Modified configuration file A new version of configuration file /etc/bash_completion is available, but the version installed currently has been locally modified. What would you like to do about bash_completion? install_new keep_current diff sdiff shell Ok (Previously there was a non-debconf-prompt about those kind of changes). Yes, I suppose this is related with the use of ucf (Update Configuration File), I didn't do that, so don't ask me how it works :) Since I wanted to see a diff, but did not know what sdiff meant I tried it by selecting. After pressing enter, nothing happened anymore, the installation was stuck. To be sure, I let it run for 1 hour. After presseing Ctrl-C I got the following message: dpkg: error processing bash-completion (--configure): subprocess post-installation script killed by signal (Interrupt) Errors were encountered while processing: bash-completion E: Sub-process /usr/bin/dpkg returned an error code (1) This seems like a bug in ucf itself -- I don't believe bash-completion is faulty here. CCing ucf maintainer (hi Manoj). However, did you retry to upgrade? Please do, and report if anything changed. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] RFC: dh_bash-completion (was: Re: ./current r1110 [..])
Hi all, On Tue, 17 Jun 2008 22:28:54 +0200, David Paleino wrote: revno: 1110 committer: David Paleino [EMAIL PROTECTED] branch nick: current timestamp: Tue 2008-06-17 22:28:54 +0200 message: added extra/dh_bash-completion to ease future rewrite of bc. added: extra/ extra/dh_bash-completion I've added this little script to the package. As the subject says: comment freely on this :) The reason why I added the script is to ease the installation of completion files by other packages. Instead of manually creating /etc/bash_completion.d/ and installing the file, just Build-Depend on bash-completion (or a -dev package we would create, but that's overkill to me) and make a debian/bash-completion file. :) I believe the package should be released (the Debian bugs closed would be ~20...), and it has some improvements which would benefit also non-Debian users. We should release the package as upstream as well, and that's why I set the RELEASE number to 20080617 (i.e. today, but it might also be tomorrow... or anywhen we release) Luk, you're the only DD (AFAIK) in the team, could you please see if the package is OK and upload it? Thanks. If you have time, could you also please make an upstream tarball (i.e. debian/ stripped off)? I could write a simple Makefile for that, but I haven't any more time tonight to do this (I could do this tomorrow evening) Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#487441: bash-completion: unexpected EOF with version 20080617
On Sat, 21 Jun 2008 18:28:34 -0300, Nelson A. de Oliveira wrote: On Sat, Jun 21, 2008 at 6:19 PM, David Paleino [EMAIL PROTECTED] wrote: On Sat, 21 Jun 2008 18:09:49 -0300, Nelson A. de Oliveira wrote: Package: bash-completion Version: 20080617 Severity: normal This hasn't been released yet, you know this, right? :) How did you manage to get it? :p I download packages from incoming sometimes :-) I see Luk uploaded the package less than half an hour ago... that's why I'm not seeing this :) bash: /etc/bash_completion: line 9335: unexpected EOF while looking for matching ``' bash: /etc/bash_completion: line 9394: syntax error: unexpected end of file I've already seen that error... it was some incomplete sed regular expression... I'll work on it, I promise :) Sure, thank you! Bad news: I've looked throughout almost 80% of the file, and found no missing '`'... I believe it'll take some time... I'll have to read the whole source code... and ~9400 lines aren't that pleasant :s Someday we'll make it modular... (ahah!) David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Debian revision number
On Sun, 22 Jun 2008 00:22:24 +0200, Luk Claes wrote: David Paleino wrote: Why did you set the Debian version number without a revision? Is there a particular reason? Yes, we don't have an upstream changelog AFAICS, so stripping the debian dir is not an option IMHO... [..] Will keep it native for now... and will upload a fixed package right away. Ok, thanks. Please take a look also at rev1118? That would enable us start filing bugs against packages, without the need of a new upload just for dh_bash-completion... ;) Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Debian revision number
On Sun, 22 Jun 2008 00:32:02 +0200, David Paleino wrote: On Sun, 22 Jun 2008 00:22:24 +0200, Luk Claes wrote: [..] and will upload a fixed package right away. Please take a look also at rev1118? Please, see rev1119 :) David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#487449: Fw: Bug#487449: bash-completion: Wrong directory name completion
Forwarding my reply to Nelson -- I had mistaken the BTS address
Inizio messsaggio inviato:
Data: Sun, 22 Jun 2008 01:07:44 +0200
Da: David Paleino [EMAIL PROTECTED]
A: Nelson A. de Oliveira [EMAIL PROTECTED], [EMAIL PROTECTED]
Oggetto: Re: Bug#487449: bash-completion: Wrong directory name completion
On Sat, 21 Jun 2008 19:45:08 -0300, Nelson A. de Oliveira wrote:
Package: bash-completion
Version: 20080617.1
Severity: normal
Hi again!
Since I won't sleep if you (or anyone else) are unable to use bash-completion
because of my lazy testing, here's a quick patch I believe fixes the problem
(r1121):
=== modified file 'bash_completion'
--- bash_completion 2008-06-21 22:51:09 +
+++ bash_completion 2008-06-21 23:05:48 +
@@ -241,13 +241,13 @@
#set -f # disable pathname expansion (globbing)
if [ ${1:-} = -d ]; then
- COMPREPLY=( [EMAIL PROTECTED]:-} $( compgen -d -- $cur ) )
+ COMPREPLY=( [EMAIL PROTECTED]:-} $( compgen -d -- $cur ) )
#eval $glob# restore glob setting.
return 0
fi
xspec=${1:+!*.$1} # set only if glob passed in as $1
- COMPREPLY=( [EMAIL PROTECTED]:-} $( compgen -f -X $xspec -- $cur
) \
+ COMPREPLY=( [EMAIL PROTECTED]:-} $( compgen -f -X $xspec -- $cur ) \
$( compgen -d -- $cur ) )
#eval $glob# restore glob setting.
}
Goodnight,
David (who is going to sleep... seriously.)
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Ubuntu (new upstream) bash-completion
On Sun, 22 Jun 2008 22:46:56 +0200, Luk Claes wrote: 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... [..] 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 probably want to have the merge ready before? Done. Please see rev1145. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Ubuntu (new upstream) bash-completion
On Mon, 23 Jun 2008 12:04:24 +0200, David Paleino wrote: On Sun, 22 Jun 2008 22:46:56 +0200, Luk Claes wrote: 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... [..] 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 probably want to have the merge ready before? Done. Please see rev1145. Not ready yet. It triggers the infamous bash: /deb/bzr/bash-completion/current/bash_completion: line 9384: unexpected EOF while looking for matching ``' bash: /deb/bzr/bash-completion/current/bash_completion: line 9454: syntax error: unexpected end of file again. Going to catch the bug :) David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bash bug, not Bash-completion's.
reassign 387408 bash retitle 387408 command completion not working with ACLs thanks Hello (CCing bash maintainer), this particular bug, even if it's regarding completion, is of bash, not bash-completion. Bash-completion, in fact, only handles what comes after the command, which is instead completed by bash. Matthias, please try to solve this bug ;) Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#498474: TAB always outputs -sh: ( compgen -f -X -- '...' ): No such file or directory
tags 498474 unreproducible moreinfo
thanks
Ciao Lucio,
On Wed, 10 Sep 2008 12:28:49 +0200, Lucio Crusca wrote:
Whenever I type a prefix and then hit TAB, I see the folowing on the console:
-sh: ( compgen -d -- 'Mai' ): No such file or directory
-sh: ( compgen -f -X -- 'Mai' ): No such file or directory
That -sh is looking weird to me.
If you look at the source code, those lines should be in the _filedir() function
(marked with *):
_filedir()
{
local IFS=$'\t\n' xspec
_expand || return 0
local toks=( ) tmp
while read -r tmp; do
[[ -n $tmp ]] [EMAIL PROTECTED]
* done ( compgen -d -- $(quote_readline $cur) )
if [[ $1 != -d ]]; then
xspec=${1:+!*.$1}
while read -r tmp; do
[[ -n $tmp ]] [EMAIL PROTECTED]
* done ( compgen -f -X $xspec -- $(quote_readline $cur) )
fi
COMPREPLY=( [EMAIL PROTECTED] [EMAIL PROTECTED] )
}
As you can see, that -sh is not appearing anywhere.
Did you hack our code? ;) :P
where Mai is the prefix I've keyed in.
The output of ls is:
$ ls
log Maildir
The bug happens with any command, be it cd MaiTAB, rm -rf MaiTAB, ls
MaiTAB or others. It happens even when there's no file starting with the
prefix.
I think the bug is a grave one because my bash-completion is actually
unusable.
I'm sorry but... well... I just can't reproduce it:
$ pwd
/tmp
$ mkdir bug
$ cd bug/
$ pwd
/tmp/bug
$ touch log; mkdir Maildir
$ cd MaiTAB
$ cd Maildir/^C
$ rm -rf MaiTAB
$ rm -rf Maildir/^C
$ ls MaiTAB
$ ls Maildir/^C
$
My suggestion here is to try reinstalling bash-completion:
# apt-get --reinstall install bash-completion
Hope this helps,
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#427758: [COMPLETION] filenames starting with =
tags 427758 -unreproducible tags 427758 confirmed notfixed 427758 20080617 found 427758 20080705 thanks Hi Robert, sorry for the late reply, I missed your mail :( On Tue, 24 Jun 2008 21:28:16 +0200, Robert Millan wrote: On Fri, May 16, 2008 at 11:15:50PM +0200, David Paleino wrote: I can't reproduce this with bash-completion/20060301-4. Here's what I have: $ touch =foo $ echo =TAB [lists all files -- possibly a bug, but not this one] Create an empty directory, then put =foo in it. This ensures a list of files isn't offered, and you get the expansion directly, exposing this bug. Ok, I got it now. Bug confirmed, we'll work on it ASAP! (in these days I fixed another bug regarding special characters, but it seems like this one is still there... and I don't have much time now :( ) Thanks for your report, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#498474: Bug#498474: Bug#498474: Need information on which packages have installed completion scripts
On Wed, 10 Sep 2008 22:09:32 +0200, Hanska wrote: [..] Argh!!! WTF?! What happened?!... ok, you just discovered my hidden identity ;) :D That's me, however. David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#499780: Bug#499780: bash-completion: gdb argument returns an error when a path is not existing
tags 499780 confirmed pending thanks Hello Sylvestre, On Mon, 22 Sep 2008 11:55:27 +0200, Sylvestre Ledru wrote: There is a small bug when calling the completion on gdb when a path in $PATH does not exist: $ export PATH=/usr/local/bin:/usr/bin:/bin:/usr/games:/path/which/does/not/exist $ gdb tab = find: `/path/which/does/not/exist': No such file or directory A patch fixing this bug is attached to this bug report. Fixed in bzr rev1183. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#366899: bash-completion: function _dpkg_source contains a inappropriate exit statement
clone 366899 -1 retitle -1 function _dpkg_source contains a inappropriate exit statement thanks On Mon, 20 Oct 2008 20:03:57 +0200, A.Politz wrote: Package: bash-completion Version: 20080705 Followup-For: Bug #366899 This would be a different bug anyhow, please reply to the proper bug. _dpkg_source contains a inappropriate exit statement, which forces the shell to exit. I suppose this should be 'return' instead. Reproduce: Open a bash-shell , type '_dpkg_sourceRET'. Why are you calling _dpkg_source() directly? David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#366899: bash-completion: function _dpkg_source contains a inappropriate exit statement
On Fri, 24 Oct 2008 19:12:01 +0200, Andreas Politz wrote: David Paleino wrote: On Mon, 20 Oct 2008 20:03:57 +0200, A.Politz wrote: _dpkg_source contains a inappropriate exit statement, which forces the shell to exit. I suppose this should be 'return' instead. Reproduce: Open a bash-shell , type '_dpkg_sourceRET'. Why are you calling _dpkg_source() directly? David I have written a wrapper around bashs completion mechanism in order to use it programatically. Uhm, interesting. Would you please keep bash-completion-devel@lists.alioth.debian.org informed? It would be interesting to integrate what you're doing upstream. What are you using to achieve that? However, fixed in bzr, thanks for filing the bug. (I'll close the proper bug as soon as control@ does its job.) David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#503691: bash-completion: does not complete files and directories as arguments
On Mon, 27 Oct 2008 16:52:29 +0100, Norbert Preining wrote: Hi David, Hello Norbert, as discussed in Palermo, here my bug report. It makes me crazy that so many programs taking files or directories as arguments cannot be completed. Yes, I do remember our discussion! Thanks for reminding me though! Example: cowbuilder --create --distribution etch --basepath /var/cache/pbuTAB does NOT complete to /var/cache/pbuilder/, although the directory is there. Same with our TeX packing scripts: perl tpm2deb-source.pl make-orig-tar --master=/src/TeX/MasTAB or perl tpm2deb-source.pl make-orig-tar --master /src/TeX/MasTAB in both cases it never completes to /src/TeX/Master-2007.0 which is there. I assume that in lack of any information, in former times bash completion did path name completion, but now it does nothing. That is not good. Yes, right. I've just tried with a non-existant command, and... $ ls wicd_1.5.4-1_all.deb wicd_1.5.4-1.dsc wicd_1.5.4-1_i386.upload wicd_1.5.4-1.diff.gz wicd_1.5.4-1_i386.changes wicd_1.5.4.orig.tar.gz $ foobar TAB wicd_1.5.4-1_all.deb wicd_1.5.4-1_i386.changes wicd_1.5.4-1.diff.gz wicd_1.5.4-1_i386.upload wicd_1.5.4-1.dsc wicd_1.5.4.orig.tar.gz $ foobar wicd_1.5.4 it seems working, really. However, with existing commands it does not work, as you reported. I'll take a look at it, :) Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#503691: bash-completion: does not complete files and directories as arguments
On Fri, 31 Oct 2008 22:16:22 +0100, David Paleino wrote:
On Mon, 27 Oct 2008 16:52:29 +0100, Norbert Preining wrote:
Example:
[..]
Same with our TeX packing scripts:
perl tpm2deb-source.pl make-orig-tar --master=/src/TeX/MasTAB
or
perl tpm2deb-source.pl make-orig-tar --master /src/TeX/MasTAB
in both cases it never completes to /src/TeX/Master-2007.0 which is
there.
I assume that in lack of any information, in former times bash
completion did path name completion, but now it does nothing. That is
not good.
Yes, right.
I've just tried with a non-existant command, and...
[..]
it seems working, really.
It seems working also with a simple Perl script:
$ cat /tmp/foo.pl
#!/usr/bin/perl
use Getopt::Std;
%opts=();
getopts(f:,\%opts);
print -f $opts{f}\n if defined $opts{f};
$
$ perl /tmp/foo.pl -f /tTAB
$ perl /tmp/foo.pl -f /tmp/TAB
claws-mail-1000kde-neo/ ssh-fEkPrD3081/
foo.pl ksocket-neo/ .X0-lock
Galaxium/ orbit-neo/ .X11-unix/
gconfd-neo/plugtmp/ .xfsm-ICE-07FKJU
gpg-YWdQy5/pulse-L9K88eMlGn7C/
.ICE-unix/ serverauth.kTXVHqDjyx
$ perl /tmp/foo.pl -f /tmp/fTAB
$ perl /tmp/foo.pl -f /tmp/foo.pl
-f /tmp/foo.pl
$
However, with existing commands it does not work, as you reported. I'll take a
look at it, :)
perl is obviously an existing command. And my line seems totally similar to
the one you reported. I'll continue having a look :)
Kindly,
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#502804: Bug#502804: syntax errors when sourcing bash-completion with POSIX enabled
On Sat, 1 Nov 2008 00:10:04 +0100, Freddy Vulto wrote: Here's another improved patch. Adding an hyphen `-' to [EMAIL PROTECTED]' will circumvent an error Unbound variable when `set -u' is in effect. Committed (bzr1198), thanks. David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#504141: bash-completion: Improved known_hosts completion with -F support, hosts indented or comment-trailed
Hello Freddy,
On Sat, 01 Nov 2008 00:36:46 +0100, Freddy Vulto wrote:
Attached are improvements to _known_hosts, ssh, scp and sftp:
- Added support for `-F configfile' to _known_hosts. I've done this
especially to make it easier to configure an ssh testsuite when writing
automated tests.
I'm committing those changes. However, I believe I found a typo in your
ssh/scp modifications:
+ if [ ${#1} -gt 2 ]; then
+ optconfigfile=$i
+ else
Shouldn't that be $1, instead of $i? AFAICT, $i is not defined anywhere, while
$1 perfectly makes sense there.
Committed with these corrections in bzr rev1199.
- Allow `Host(Name)' in ssh config file to be indented
Committed in bzr rev1200.
- Allow `Host(Name)' in ssh config file to have trailing comment. Note that
SSH allows a comment after `Host' but not after `HostName'. In the latter
case you'll get an error message when trying to scp/ssh/sftp:
garbage at end of line; #.
Committed in bzr rev1201.
Thanks for helping us,
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#504141: bash-completion: Improved known_hosts completion with -F support, hosts indented or comment-trailed
On Sat, 1 Nov 2008 20:49:06 +0100, Freddy Vulto wrote: Hello David, Hello Freddy, CCing the team :) Yes, you're right about the $i, that should be $1. :-) I'm glad I manually applied your patch then ;) That reminds me: Wouldn't it be good practice to run bash-completion with `set -u' active (error on uninitialized variables)? In the upstream bash-completion Changelog I can see Unbound variable errors already have been fixed around 2003, so it shouldn't be too hard to make bash-compliant with `set -u' again. At least errors like mine would be catched early on. So I'm in favor of honouring `set -u', are you/your team? I would be in favour of too. Currently, the one who most actively works on Bash-Completion is me. The team consists also of Luk Claes, but he's really busy with the Lenny freeze right now; Mike Forbes and Steve Kemp -- but I don't know where they actually are :-( I'm hoping to be of further assistance in the future. That's great to hear :) I'm developing a bash-completion fork with split files and automated tests (see: (www.fvue.nl/wiki/Bash_completion_library)). Besides the split-files, the code is almost the same as original bash-completion or the Debian fork. Right now I'm catching up with Ubuntu/Debian patches and writing automated tests for them. Uhm, why a fork? ;-) Are you using some kind of automated tests? No, not really, but we thought of something like that in our adoption plan. The original upstream author was Ian MacDonald, you know, and we just took the project over because he had no time. We had lots of plans, but initially focused on solving bugs. And we're still there :-( The automated tests are also suitable for the Debian package (see ./runCompletionDebian in bash_completion_lib-1.2.8.tar.gz). Will take a look, thanks. Maybe we can share the test suite and/or find other ways of cooperation? Why not? We could also merge the projects, if you wish. We were thinking of a dynamic loading strategy -- and it seems like you got it :) However, there's a sentence in your wiki which is false: ---8--- Debian package Debian maintains a fork of the original bash_completion with additional improvements. ---8--- We're not maintaining a fork. We're upstream :) (and, in fact, we also release the .tar.gz for other distributions to package it) Can I apply for a bash-completion bzr account? Sure. Go to http://alioth.debian.org , register, and look for the bash-completion project. Ask for membership, and, hopefully, Luk will see your request and accept you into the group. I'm going to look at the bash-completion-lib source, and will make a bzr branch for it. Will send you a mail when I complete this task, I hope I can keep all the history :) Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] reassign 495883 to bash-completion
reassign 495883 bash-completion ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#506560: say how to start using
unmerge 482383 506560 thanks On Sun, 23 Nov 2008 00:37:57 +0800, [EMAIL PROTECTED] wrote: No no no. Your merge is wrong. I don't want bash_completion enabled by default. In no way. It bloats my shell, and makes it do unexpected things. Ok, understood. Fixed in bzr rev1207: ---8--- [..] Debian/GNU Linux or Ubuntu, etc. You still need to source it from either /etc/bashrc or ~/.bashrc (or any other file sourcing those). You can do this by simply using: # Use bash-completion, if available if [ -f /etc/bash_completion ]; then . /etc/bash_completion fi (if you happen to have *only* bash = 2.04, see further if not) [..] ---8--- Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] reassign 506560 to bash-completion
reassign 506560 bash-completion ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#506560: say how to start using
On Sun, 23 Nov 2008 01:23:20 +0800, [EMAIL PROTECTED] wrote: DP Fixed in bzr rev1207: DP ---8--- DP [..] DP Debian/GNU Linux or Ubuntu, etc. You still need to source it from either DP /etc/bashrc or ~/.bashrc (or any other file sourcing those). You can do DP this by simply using: DP # Use bash-completion, if available DP if [ -f /etc/bash_completion ]; then DP . /etc/bash_completion DP fi DP (if you happen to have *only* bash = 2.04, see further if not) DP [..] --- 8--- Looks like wherever you put that is not enough for clods like me to notice. You need a README.debian file... No. That README is installed as /usr/share/doc/bash-completion/README.gz -- and that's the first place one would look at. And no, that information is not Debian-specific, so a README.Debian is totally useless here. I'm going to also update the website, but the bug is fixed to me. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Ubuntu bash-completion 20060301-4ubuntu2
On Tue, 25 Nov 2008 12:02:32 +0100, David Paleino wrote: Changes: bash-completion (20060301-4ubuntu2) jaunty; urgency=low . * Added qdbus completion (LP: 257903) Rev1210 in our bzr repository. David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bazaar hookless email notification
Hello all, you might be asking how come my commits send e-mails to [EMAIL PROTECTED], and others' don't. Here's the secret: $ crontab -l @reboot /var/lib/gforge/chroot/home/users/adeodato/bzr-hookless-email/alioth_helper.sh bash-completion -d $ Please consider adding this line (it has been wrapped by the mail client, it's a *single* line) to your cronjobs on alioth.debian.org. This way we all are informed on every commit done on the bzr repository. Kindly, David P.S.: /me thinks on moving from bzr to SVN: we adopted bzr to ease contributions from Ubuntu, but we didn't have any AFAIK, and SVN is far easier to maintain to me (i.e. hooks, branches, ...) -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#506973: bash-completion: soft link completion is broken
tags 506973 confirmed thanks Hello Noah, On Wed, 26 Nov 2008 16:00:52 +, Noah Slater wrote: [..] Bash completion fails to account for soft links properly: [EMAIL PROTECTED]: ~ $ mkdir -p dir-a/dir-b [EMAIL PROTECTED]: ~ $ ln -s dir-a/dir-b dir-c [EMAIL PROTECTED]: ~ $ touch doc-a [EMAIL PROTECTED]: ~ $ touch doc-b [EMAIL PROTECTED]: ~ $ cd dir-c [EMAIL PROTECTED]: ~/dir-c $ cat ../doc- doc-a doc-b This is because it considers dir-c as a sibling of dir-a, not as dir-a/dir-b. :( I don't know whether this is fixable or not. Will have a look. Thank you for your report. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] New bash-completion upstream, Fedora patches
On Tue, 6 Jan 2009 21:03:46 +0200, Ville Skyttä wrote: Hello, Hello Ville, I noticed today that there's a new bash-completion upstream at alioth.debian.org - this is great, it's about time! Eheh :) And we're having a newer upstream in our bzr repository ;) I am the long time Fedora bash-completion maintainer and we are shipping a whole slew of patches and additions in the Fedora package (quite a few of them written by yours truly) which I'd very much rather see applied upstream. I've just rebased them against the 20080705 release. That is great! If you want to give me commit access to the repository, I can take care of committing them (as well as future improvements) myself. My alioth account is scop-guest. If you'd rather not give that access, let me know and I'll send an URL to the patches to you. Are these patches tested enough? How long have they been applied in the Fedora package? We don't want another plethora of bugs *gh* ;) However, please file a request to join the group: http://alioth.debian.org/projects/bash-completion/ Also, please subscribe to the mailing list (you can see it CCed, just join it at lists.alioth.debian.org ) -- it would be really cool to have some sort of cross-distribution development (we already have a gentoo maintainer in our IRC channel, #bash-completion on irc.oftc.net). Thank you for your help! Kindly, David Paleino Bash-Completion Team -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [MERGE] Small fixes from Mika Fischer
On Wed, 07 Jan 2009 20:56:04 +, James Westby wrote: Hi, Hello James, There were a couple of small patches in the Ubuntu BTS, so I dropped them in a branch. Please review and merge lp:~james-w/bash-completion/small-fixes Fixes merged, rev1221. Thank you. One of the patches came from https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/194419 where there are several problems under failglob reported, and a couple of patches suggested to fix some of them. It seems like failglob and completion don't get along to well, is there some way that can be fixed across the board. I'm happy to file a bug report on the issue if you feel that would be appropriate. Please, do, so we can keep track of bugs without going crazy :) Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] New completions: inline or separate files?
On Sun, 11 Jan 2009 15:22:45 +0100, Santiago M. Mola wrote: El dom, 11-01-2009 a las 15:16 +0200, Ville Skyttä escribió: When adding completions for new, generally available commands, is it preferred to inline them in bash_completion or to add new files to contrib/? I gather there's a more or less active plan to split bash_completion into smaller files, maybe adding new completions as separate ones would make this process a bit easier? In Gentoo, we split all inline completions to a separate file named 'base'. I expect upstream bash-completion to follow a similar path in the future. In my opinion, if 'generally available commands' are really basic commands like the ones provided by coreutils, proc-utils, etc, I'm for adding them inline. Otherwise, I'd prefer them in separate files. That's what we're doing with new completions: put them in contrib/. Also, when fixing existing completions, I also split them in separate files in contrib/. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] New directory layout
On Tue, 13 Jan 2009 02:16:51 +0100, Santiago M. Mola wrote: Hi all, Hello Santiago, hello all, Based on the current aproach on Gentoo and on comments from other distros, I'd like to propose a new directory layout for bash-completion. Ok, let's see :-) El lun, 12-01-2009 a las 23:55 +0100, Guillaume Rousse escribió: We also have a slightly initialisation system, with a file in /etc/profile.d sourcing a system-wide /etc/sysconfig/bash-completion configuration file, then a ~/.bash-completion to set up relevant options. This let sysadmin configure bash completion globally, or not, while still allowing individual users to do it in the last case. In Gentoo, we install all bash-completion modules to /usr/share/bash-completion/. In Debian, we have them in /etc/bash_completion - /etc/bash_completion.d/. But, since those are not really configuration files, and are rather arch-independent data, I'd vote for those to go to /usr/share/bash-completion/. +1 for Gentoo ;-) Modules are enabled system-wide when they're symlinked from /etc/bash_completion.d/ and users can enable extra modules creating symlinks in ~/.bash_completion.d/. We have a Gentoo-specific tool for handling these symlinks, but I guess each distro would take its own aproach, which could be a) providing a configuration interface, b) enabling all modules by default (like some already do), c) let the user do it himself. I really like the idea of per-user completions, read further on my reply to Ville. However, the symlinks-in-/etc/bash_completion.d/ approach doesn't seem very robust, either. In Debian we have alternatives, i.e. symlinks for executables (generally speaking, also for libraries) in /etc/alternatives/ pointing to /usr/bin/foo or /usr/lib/libfoo.so. Said that, I can't see how we (Debian) could sanely handle that with our distribution-specific tool. Maybe we could also provide some distribution-agnostic tool to handle those symlinks? (something like a2ensite and a2enmod for apache2 -- but I don't really know whether those are Debian-specific) I think installing modules to /usr/share/bash-completion is more consistent than the current state (I don't think bash-completion modules can be considered anything near to configuration files). Agreed. Also, this provides more flexibility for distros and users. And it seems it's needed since enabling/disabling modules system and user wide is a quite common demanded feature. Agreed. With respect backwards compatibility, there's not too much to say: if someone installs a module directly to /etc/bash_completion.d, it'll obviously work. ACK. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#511790: Completion of package names broken
Hello Chris, On Wed, 14 Jan 2009 14:33:29 +0100, Christoph Anton Mitterer wrote: Hi. Completion of package names seems to be broken at least (!!) when I do the following: dpkg -L or dpkg -S does not find base-passwd at all?! Well, dpkg -S isn't meant to complete on package names. From man dpkg: -S, --search filename-search-pattern... Search for a filename from installed packages. So you should really give a pattern there. With regard to dpkg -L, you're right, it was completing only on non-essential packages, fixed in bzr rev1255: http://bzr.debian.org/loggerhead/bash-completion/current/revision/1255? Kindly, David Paleino -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#511789: completion of ssh known hosts has some minor problems
Hello Chris, On Wed, 14 Jan 2009 14:32:20 +0100, Christoph Anton Mitterer wrote: When completing hosts listed in known hosts files from ssh (and perhaps from other locations like /etc/hosts, too) also includes hosts that are commented like: #do.not.use.this.host.example.com Fixed, also allowing for preceding whitespace characters (i.e. and \t), rev1257: http://bzr.debian.org/loggerhead/bash-completion/current/revision/1257? Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Mandriva handling of bash completion
On Sat, 17 Jan 2009 13:28:22 +0100, Guillaume Rousse wrote:
Guillaume Rousse a écrit :
See for instance various code currently not part of upstream
bash-completion package:
[..]
I didn't had much input of those completions sofar. As Ville seems to
prefer post-commit review, I will introduce them one by one in contrib
directory. I just asked for project membership.
Please, commit them into to_review/.
We don't really want to release/install unreviewed completions :-) (because
ones installed into contrib/ would automatically get installed
into /etc/bash_completion.d/ / /usr/share/bash-completion/contrib/ right now)
(it could also be useful to update the wiki with completions needing review,
I'm going to make a dedicated page for it)
Just a question, tough, as everyone seems to be OK for moving to a
installation-based system for activating completion functions, should we
really keep the have(foo) { } condition in each file ?
IMHO yes. It ensures loading the function only when the command is really
available.
In such a scenarion, if a completion file get sourced, it his because it has
been enabled, meaning the command is available.
Not really. Actually, if you don't use have foo {}, the function gets
loaded, even if you don't have the command.
Also, we haven't really settled on the new directory layout, so I'd prefer to
just keep things the old way for now.
I have no real clue about the exact cost calling this function, but avoiding
useless tests at each new shell startup seems a good idea for me.
Well, executing have() doesn't seem to much expensive ;-)
~ $ have() {
unset -v have
PATH=$PATH:/sbin:/usr/sbin:/usr/local/sbin type $1 /dev/null have=yes
}
~ $ time have ssh
real0m0.000s
user0m0.000s
sys 0m0.000s
~ $ echo $have
yes
~ $
Sure, it is just one command, and not the whole bunch of completions, but I
don't really think some seconds fractions really hurt.
Also, but this is something we should work on at a later time IMHO, there's
also the bash-completion-lib fork, which seems to dinamically load
completions when the command is typed. But that's just food for thought.
Kindly,
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Keeping support for bash 3.0?
On Sat, 17 Jan 2009 20:20:14 +0200, Ville Skyttä wrote: Hello, Hello Ville, What's the status of keeping support for bash 3.0, do we have people around here who strongly think that it should be preserved and/or who regularly test with older versions? AFAICT, me and Luk had plans on removing those bits after fixing as much as possible existing bugs. Oh, well, we also had plans about improving the loading mechanism altogether :-) Personally, I don't have access to a box that has bash 3.0 any more and thus I'm not able to test with those versions any more nor would mind them being dropped, but I'm not insisting dropping either. I second dropping 3.0 features, but I believe the completions would really need a deep look :-) What prompted me to ask this question was an interesting looking patch posted to Red Hat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=479936 I suppose there would be possibilities for further cleanups/optimizations/simplifications if bash 3.0 was the oldest supported version. Would you mind setting up a wiki page for this, as well? Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Mandriva handling of bash completion
On Sun, 18 Jan 2009 12:14:51 + (UTC), Freddy Vulto wrote: Merging Debian-completion with bash-completion-lib is possible (and I'm in favor). Here're already a few things to consider: 1. Completions reside in a somewhat arcane directory-structure: Yes, I already saw that the last time I saw your code (i.e. some months ago) :-) Also, I saw your proposal has been added to http://wiki.debian.org/Teams/BashCompletion/Proposals/NewDirectoryLayout , great! [..] 4. Helper functions reside in a subdirectory `include'. Helper functions can be loaded by calling `comp_include', e.g. ./completions/complete-nohostcomplete/ssh does: comp_include _dequote _known_hosts Any reason for this? Since those are helper functions, I suppose they might as well go where comp_include is defined (i.e. I don't think you define comp_include in each completion file) [0] [0] didn't have the time to have a look at the code, and probably won't have until the end of the week :/ If merging proves difficult, maybe we can start with sharing the DejaGNU test suite. The test suite is already split into two parts: loading and completing, and I'm already using the test suite for completions of both Debian-completion and bash-completion-lib. I think the best solution would be to extract the test suite from bash-completion-lib and make it a separate project? You answered yourself: But maybe I'm jumping to a conclusion too fast. If completion-lib merges with Debian-completion maybe there's no need to keep a separate test suite. Did I already say I was in favor of merging and make completion loading 5-10 times faster(!) It's not just a matter of speed (though that is very welcome, and I'd support it even if it was 1.1 times faster ;-)), but just a matter of smartness. It's not smart loading everything on login, but it is doing it when the command is actually being completed. So it's really needed, apart from speed performance. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] _expand, scp and quoting
On Sat, 24 Jan 2009 21:52:45 +0200, Ville Skyttä wrote: Hello, Hello Ville, http://bzr.debian.org/loggerhead/bash-completion/current/revision/1170? Thanks for looking at old changes too! :-) I don't think the above change is actually wrong but it has broken at least scp ~/TAB completion. This is because the ls in _scp ends up being run as ls -aF1d '~/*' 2/dev/null ...and obviously ls '~/*' practically never matches anything because of the single quotes bash inserted. Before the above change there were no quoting problems because ~ was expanded to /home/foo which bash didn't need to enclose in single quotes. We'd want the ls to be run without the quotes, like ls -aF1d ~/* 2/dev/null ...but I don't know how to get bash to do that. Ideas? Line 84, contrib/ssh -- but I suppose you already know that. On the other hand, I wonder what's the point of the ls -aF1d and sed spaghetti when completing _local_ files for scp in the first place. Wouldn't _filedir do just fine? Yes, or at least I believe so. I'd wait for others to comment on this as well. The fact is (I can't remember it right now, studying for exams and can't recall if it's doable or not -- and that's why I can't decipher what that sed hack is doing either): can we reliably find whether it's a local path? Sure one can say that /\w+.*/something/ surely isn't remote and also ~/.*, and we can handle just those two. My two tired-from-back-to-home-trip cents, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] procfs stores process name in a truncated form in /proc/pid/stat
clone 497540 -1 reassign -1 src:linux-2.6 retitle -1 procfs stores process name in a truncated form in /proc/pid/stat thanks On Thu, 22 Jan 2009 00:13:39 +0200, Yanko Kaneti wrote: It would be nice if this worked but current release of procps trim the command name to 15 even if the ps comm column is specified with additional width. And these days there are many commands with names longer than 15 e.g. gnome-blah-blah.. Hello, while fixing #497540 we stumbled upon a bug in procps. Trying to fix completion for killall, we wanted to use ps axo comm instead of ps axo command, but that truncates process names at 15 characters. It could've been a procps bug, but the truncated form is really stored in /proc/pid/stat: # cat /proc/12571/stat 12571 (hald-addon-stor) S 12519 12518 12518 0 -1 4194304 347 0 0 0 4 0 0 0 20 0 1 0 520073 3391488 260 4294967295 134512640 134528780 3220600864 3220600436 3084521718 0 0 4097 0 0 0 0 17 0 0 0 0 0 0 # (that should've really been hald-addon-storage) This obviously breaks a number of applications depending on procfs to get the process name. Is there a reason for this 15-characters-limitation? Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] ./current r1300: - Restored `_display()' completion for `display' by removing
On Sun, 01 Feb 2009 23:05:33 +0100, Freddy Vulto wrote: revno: 1300 committer: Freddy Vulto fvu...@gmail.com branch nick: bash-completion-devel timestamp: Sun 2009-02-01 23:05:33 +0100 message: - Restored `_display()' completion for `display' by removing completion-by-extension for `display' (#311429) - Removed duplicate completion option `-borderwidth' for `display' modified: bash_completion Freddy, please also change debian/changelog accordingly. We're currently using that as upstream changelog, but planning to have a proper ./ChangeLog in the near future. If you have a Debian system, you might want to install the devscripts package, and use the handy dch/debchange tool (run from ./) to add your section. If you wish to do that manually, please add a section to the end of the changelog entry like: [ Freddy Vulto ] * item1 * item2 You can leave the trailer line intact, I'll update it once we make a release. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] proposal fort bash-completion
On Sun, 1 Feb 2009 19:43:25 -0400, Alexander Butenko wrote:
Hey David,
Hello Alexander,
First of all thanks for this scripts, they are realy awesome.
I just took up upstream development and formed a team around it ;-)
The only issue with them that all functions located in one file.
We are already aware of this problem. And are working for this.
The first solution is splitting bash_completion into smaller
files in bash_completion.d/, and we're already doing that. Also, we're planning
to change directory layout, so don't relay on /etc/bash_completion being
there :-)
The above is a temporary solution though, since it will only ease
maintainance, with no benefits over loading time. That's why we're also
planning on merging bash-completion-lib, by Freddy Vulto, which has a rather
different (and way faster) approach to completions.
If you can't wait for us to merge it, you might want to give it a try. Be
warned that its directory layout is completely different from what you're used
to, i.e. you should know what you're doing when putting files there :-).
Otherwise, please wait for our official release first, :-)
I love to see my shell right away when i launch it, but after im including
bash-completion script into mine profile its starts like way slower.
Sure, coz it takes time to parse 300kb of text :)
Well, each function is being preceded by a have foo { }, thus it's really
loaded only if you have that command. Yes, it's still parsed though :/.
It's kind of sub-optimal, really, that's why we are planning to merge
bash-completion-lib.
You might want to subscribe to bash-completion-devel@lists.alioth.debian.org
to see what's going on, or follow our project's proposals at
http://wiki.debian.org/Teams/BashCompletion .
Kindly,
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Choosing D?VCS: survey
Hello, some of you already know (mainly those on IRC), some don't. I've set up a survey to choose a D?VCS. The options are Git, Svn, Bzr. http://alioth.debian.org/survey/survey.php?group_id=100114survey_id=27 Please don't vote multiple times, or I'll need to void the survey and start it over again. The voting deadline is Sat Feb 7, 23.59 UTC (2009-02-07T23:59Z if you prefer). Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Hosting bugs on Launchpad? (was: Re: Launchpad: Claim existing team)
On Mon, 02 Feb 2009 13:55:55 -, Launchpad wrote: David Paleino (dpaleino) tried to claim the Launchpad team named Bash Completion Maintainers (bash-completion-devel) (which is associated with bash-completion-devel@lists.alioth.debian.org). This is because Launchpad automatically created the team when we uploaded our last package to Debian. But there was no human behind it. Now, since Alioth's tracker is a bit awkward, the idea of using Launchpad came to my mind. It has some pros and cons, though: Pros: - public API (though experimental) -- we might do some sort of script to automatically tag bugs when we fix them in bzr, ...; - actively maintained -- Alioth's GForge is not, and that's because not many projects are really using it as upstream bug tracker; - bug linking with distributions BTS -- a bug X can be linked to Debian's Y, Gentoo's Z, Fedora's K. (I've seen this with bugs linked both to Ubuntu and Debian bugs, but I suppose we could add Gentoo/Fedora/other bug tracking systems as well, or ask for those) - blueprints (like our /Proposals/ subsection in the wiki) - other? Cons: - not (completely?) free software :/ -- this is not a MAJOR blocker to me, but I'm having some doubts. I'm a free software guy -- but Alioth's tracker kinda sucks too. - additional registration required -- existing developers *must* register to Alioth to commit to bzr/git/svn (whatever comes out from the survey), but they would need to register to Launchpad to handle bugs. Yes, we could argue that we could host the code on Launchpad, but it only has bzr -- and we're doing the survey to see if we can move from that, aren't we? ;-) - other? I've registered a testing project at https://staging.launchpad.net/ , to see which features we could use, and how they are like. Kind regards, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] ./current r1326: Improved strace completion, undefined _command_offset() found.
Hello, On Thu, 05 Feb 2009 11:15:13 +0100, David Paleino wrote: revno: 1326 committer: David Paleino d.pale...@gmail.com branch nick: current timestamp: Thu 2009-02-05 11:15:13 +0100 message: Improved strace completion, undefined _command_offset() found. modified: to_review/strace === modified file 'to_review/strace' --- a/to_review/strace2009-01-19 20:51:24 + +++ b/to_review/strace2009-02-05 10:15:13 + [..] @@ -25,6 +25,7 @@ done if [ $offset -gt 0 ]; then + # FAIL: _command_offset is not defined anywhere. Guillame? _command_offset $offset else Guillaume, is this a Mandriva-specific helper? Ciao, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] New directory layout
On Tue, 13 Jan 2009 02:16:51 +0100, Santiago M. Mola wrote: Hi all, Based on the current aproach on Gentoo and on comments from other distros, I'd like to propose a new directory layout for bash-completion. I drafted a directory layout. Please have a look: http://wiki.debian.org/Teams/BashCompletion/Proposals/NewDirectoryLayout/1 Unfortunately, I didn't find a reasonable way to include Freddy's proposal about version-numbered-directories. Freddy: if you have ideas on how to do that, update that page, but please try not to change the overall thing. Otherwise, please draft your own layout :) Ciao, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Choosing D?VCS: survey
On Sun, 8 Feb 2009 19:29:47 +0100, David Paleino wrote: I've just requested the creation of a git repository tree for us: https://alioth.debian.org/tracker/index.php?func=detailaid=311449group_id=1atid=21 As soon as it gets created, I'll set up proper post-receive mails (always remember to `git push' now!), and import our bzr repository in it. git clone \ git+ssh://user@git.debian.org/git/bash-completion/bash-completion.git Please do not use bzr anymore. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Hosting bugs on Launchpad?
On Mon, 02 Feb 2009 21:23:03 +0100, Guillaume Rousse wrote: David Paleino a écrit : Cons: - [..] - additional registration required -- existing developers *must* register to Alioth to commit to bzr/git/svn (whatever comes out from the survey), but they would need to register to Launchpad to handle bugs. Yes, we could argue that we could host the code on Launchpad, but it only has bzr -- and we're doing the survey to see if we can move from that, aren't we? ;-) The last point is really ennoying. I'd prefer to learn how to use current Alioth BTS, even if not really the best one, than to split development in two different places. Forgot to say, Launchpad accepts OpenID logins. So if you have an openid, you don't really need to register with Launchpad. David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] alias completion: is apprending '=' by default really useful ?
On Tue, 10 Feb 2009 23:14:07 +0100, Guillaume Rousse wrote: Alias completion currently completes on alias name, always appending '=' sign to them. It might be useful if the intent is actually to define, but if the goal is just to inspect current definition, it's not, and requires additional user effort to edit its current command line. According to minimal completion principle, I'd rather drop it. Please do. At least IMHO. Additionaly, it can even get considered harmful, as if the user confirms the command line too quickly, it will wipe out alias in question... It happened to me too. :/ David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] bash_completion.sh executable?
On Fri, 13 Feb 2009 00:05:57 +0200, Ville Skyttä wrote: Hi David, others, Hello Ville, Is there a reason why bash_completion.sh is executable? It's sourced, not executed, so I think not. Can't really say, by heart. I've fixed the permissions already once in bzr, but it was (seemingly intentionally) unfixed shortly afterwards: http://git.debian.org/?p=bash-completion/bash-completion.git;a=commit;h=d49c7c4d88314cce7987651cd208de3d5882c4a8 http://git.debian.org/?p=bash-completion/bash-completion.git;a=commit;h=fe41b80fba17cbbe843b757e7c43e09d0bb6a522 David, I mailed you when I saw this happened, but I don't remember hearing back. Did I miss something? Uh, I remember chmod'ing a+x it again. But then I remember your mail and reverting it back. Maybe I forgot it? Please revert the change. Ciao, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Roadmap proposal
On Fri, 13 Feb 2009 14:14:29 + (UTC), Freddy Vulto wrote: [..] maybe we'd better release bash_completion-2 (or ..200902xx) [..] I was starting a branch for the release process... what version number you believe is sane? I'd start at 1.0, (so as not to be necessarily linked to the bash version), and the date format is kinda weird to me. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Roadmap proposal
On Sat, 14 Feb 2009 11:25:08 + (UTC), Freddy Vulto wrote: David Paleino d.paleino at gmail.com writes: On Fri, 13 Feb 2009 14:14:29 + (UTC), Freddy Vulto wrote: [..] maybe we'd better release bash_completion-2 (or ..200902xx) [..] I was starting a branch for the release process... what version number you believe is sane? I'd start at 1.0, (so as not to be necessarily linked to the bash version), and the date format is kinda weird to me. 1.0 is fine with me too - better than date format, as long as the major number is going to be increased once we drop bash-2 support. Sure it will. Can you elaborate on which releases you have in mind? Well, let me elaborate on the release process I have in mind first. 1.0 is what we have now (master). As soon as other people reply with ok (I won't wait for everyone to reply, but just two people out of 7 isn't fair), I will: 1) branch bash-completion-version, that's feature-frozen. Only bugfixes go there (cherry-picked from master). 2) we establish a freeze period. Let's say two-three days? Up to a week, however, just to find bugs and fix them on time. 3) we release the tarball, update the webpage, put it on Alioth, [..]. Maybe a make-tarball script would be good (i.e. copying debian/changelog to CHANGES, removing debian/, fixing things, using sed to dynamically substitute version number, ...) The releases I have in mind are: 1.0: first (well, second) official release from the new upstream team. New directory layout here? 1.x: bugfixes, completions split, ... -- merging bash-completion-lib here? 2.0: new major release: drop bash-2 features. 2.x: bugfixes [..] Obviously, major version numbers change for major changes. For example, the bash-completion-lib merge would deserve a 2.0 to me, but we can discuss version numbering anytime. /me wishes we move to Launchpad for bugtracking, so we can set blueprints, milestones, ... Ciao, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Reply-To for -commits list
On Thu, 12 Feb 2009 23:58:46 +0200, Ville Skyttä wrote: I think it would be good to set Reply-To to bash-completion-devel for all messages on the -commits list. This is based on the assumption that discussion about commits should take place on -devel, not -commits (I'm not sure if people can post to the latter directly anyway). Done. David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bash-completion-devel unsubscribe notification
On Sun, 15 Feb 2009 17:29:00 +, mailman-boun...@lists.alioth.debian.org wrote: l...@debian.org has been removed from Bash-completion-devel. Goodbye Luk, and thank you for handling the upstream takeover at the beginning. :) Ciao, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Using launchpad as bugtracker?
On Mon, 23 Feb 2009 19:56:31 +0200, Ville Skyttä wrote: On Monday 23 February 2009, David Paleino wrote: Hello, what do you think of using Launchpad as bugtracker? No strong objections, but I'd prefer something that can naturally link bugs with commits in the SCM (and have the links go both ways in the BTS and SCM web interfaces), Well, Alioth isn't doing that now :/. and generally one logical site for all project activities. Well, we can just use Alioth for webpages/wiki/git and LP for bugs/blueprints (that would then be moved away from the wiki, but that's another story) I haven't really used launchpad, but a quick Google search didn't tell me that git/gitweb would be available there. Yes, but I believe we could ask LP people to add it? Who knows? :) /me joins #launchpad on some network and asks. [..] Crosslinking distro bugs in launchpad sounds like a nifty feature, Well, that's what I tried to partially implement in Alioth with Originally reported in and Original bug number fields. But in LP if the remote bug changes status, it gets tracked. :) perhaps enough to trump lack of nice BTS-SCM integration if those are the things to choose from. Perhaps, but this is an important decision and I won't take that all alone. Thank you for your reply, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Using launchpad as bugtracker?
On Mon, 23 Feb 2009 19:07:55 +0100, David Paleino wrote: On Mon, 23 Feb 2009 19:56:31 +0200, Ville Skyttä wrote: I haven't really used launchpad, but a quick Google search didn't tell me that git/gitweb would be available there. Yes, but I believe we could ask LP people to add it? Who knows? :) /me joins #launchpad on some network and asks. Ok, after some talking with a guy, LP is definitely not going to support git. Too much work in its maintainance, integrating with LP, [..]. But, *but*: 19:24 beuno hanska, there will be git imports, so you will be able to use the branches in LP 19:25 hanska beuno: yes, that needs some manual activity though 19:25 beuno no, we have continuos imports 19:25 beuno we already have them for svn and cvs 19:25 hanska ah, that's good then This means that we could continue working on Alioth's git, the code would then automatically imported into Bzr and: 19:30 hanska beuno: is it possible to mangle the bugstatus from commit messages? 19:31 hanska like Added patch for foo (LP: #12345), or kinda? 19:32 beuno hanska, marking bugs as fixed from commit messages is in the pipeline 19:32 beuno hanska, not sure when it's set to land, but it's somewhere on the roadmap before July as well 19:32 hanska beuno: ok, great, thank you. So we would eventually get some kind of SCMBTS integration. But also, before July, it is possible that Alioth upgrades to FusionForge (a GForge fork) -- maybe we could expect more features there? Going to ask Alioth admins. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] vncviewer
On Wed, 25 Feb 2009 23:05:33 +0100, Freddy Vulto wrote: Do we have a standardized way in bash-completion for selecting alternative completions? No :/ I believe we could do something a _get_alternative() function: in Debian/Ubuntu/thelike it would check the symlinks in /etc/alternatives/, in other distributions we might ask whether they have something similar (also using external tools is good, just need to be sure they're there) -- and then, complete vncviewer depending on the alternative. something like case $alternative in: tightvnc) complete -f _tightvnc vncviewer ;; vncfoobar) complete -f _vncfoobar vncviewer ;; esac Obviously, $alternative would be handled by some other code there. Just my two cents, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#519238: Bug#519238: bash-completion: syntax error in /etc/bash_completion
Ciao Norbert, On Wed, 11 Mar 2009 10:47:58 +0100, Norbert Preining wrote: Package: bash-completion Version: 20080705 Severity: normal /etc/bash_completion: line 273: syntax error near unexpected token `' /etc/bash_completion: line 273: ` done ( compgen -d -- $(quote_readline $cur) )' Uhm. How do you call bash? If you call it as /bin/sh, that may be the cause: /bin/sh makes bash POSIX-compliant, thus disabling some features. Please grep /etc/passwd for your username, and check that the shell is /bin/bash, not /bin/sh (and yes, we should do some more checking there, but I don't know whether it's possible or not -- I believe yes though, but I'm just back from my uni classes and I don't really have all bash builtins in my brain :P) If that fixes it for you, I'll close the bug. Ciao, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [Bash-completion-commits] [SCM] bash-completion branch, master, updated. 0f2656669fbdf627a3ddf11bdb72e3ec9cef68fd
On Mon, 30 Mar 2009 23:50:53 +0300, Ville Skyttä wrote: On Monday 30 March 2009, Guillaume Rousse wrote: Guillaume Rousse a écrit : The following commit has been merged in the master branch: commit 0924d059c6c845069b10482882c821088ccaeefa Merge: 91daa8de58a6e88d5a4b55621e2e7d5e732c65ea dc88329e8eea8424f2e1dc7efc50a80e240708c4 Author: Guillaume Rousse guillomovi...@zarb.org Date: Mon Mar 30 22:02:55 2009 +0200 Merge branch 'master' into guillomovitch This seems to be a commit related to my own local branch, I don't understand why it does generate a mail here... I just hop I don't screw up anything in master branch. Happened to me too once, I don't claim to understand it either but it didn't seem to have any bad effects. The web UI doesn't show any changes the usual way either, just Simple merge, just as it did for me as well. But git log is a mess, and cherry-picking isn't easy. What are you guys using? What's your development workflow? There shouldn't be any merges in master. So log messages like: Merge branch 'master' of git+ssh://scop-gu...@git.debian.org/git/bash-completion/bash-completion should'nt really exist, sorry :) Also, when merging changes from my own branches into master branch, Guillaume, first of all, why do you make local branches? :) how can I merge multiples commits into single ones, so as to ditch invalid intermediate steps ? My suggestion is different from what Ville proposes, and cleaner, I believe. The trick should be using -n in git-cherry-pick. Example: mybranch $ [hack] git commit [aaa] My log mybranch $ [hack] git commit [bbb] My log 2 master $ git cherry-pick -n aaa master $ git cherry-pick -n bbb master $ git commit I never tried this, but should work :P I don't know, but the way I do it is that I clean up my commits locally before pushing them using git commit --amend. For example: # hack bash_completion git add bash_completion git commit # hack bash_completion more, related to the previous commit git add bash_completion git commit --amend # then edit the commit message if appropriate The result of the above is a clean single local commit. Right. You do this in master? After this, do you do a simple push? I'd like to have a clean log, so as in future we could have some automagical tool generating a changelog from git log (as git-dch now does for debian/changelog) -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [Bash-completion-commits] [SCM] bash-completion branch, master, updated. 0f2656669fbdf627a3ddf11bdb72e3ec9cef68fd
On Tue, 31 Mar 2009 22:26:41 +0300, Ville Skyttä wrote: On Tuesday 31 March 2009, David Paleino wrote: Ah. Well, I read somewhere that rebasing, when working on shared, published repsoitories, is *evil*. OTOH, I can't recall why it's bad It's bad if done *in* a published repository because it essentially rewrites history. I don't see anything wrong with it when done only in local working copies which aren't published/shared anywhere. Ok. -- and I never used it, really. Why are you using it? In which cases? Whenever I have local commits that haven't for whatever reason made it to the upstream repository which has moved on. Granted, I use it mostly with projects where I don't have commit access, dunno if I've used it with bash- completion. Ok, was just looking for the reason of those messages :/ -u, --update-head-ok By default git-fetch refuses to update the head which corresponds to the current branch. This flag disables the check. This is purely for the internal use for git-pull to communicate with git-fetch, and unless you are implementing your own Porcelain you are not ^^ supposed to use it. ^^ Is there any reason why you -u? Yes, muscle memory. When I started learning git, I probably read some instructions that said git pull -u corresponds to say cvs update and have not bothered to re-check that habit afterwards. I'll look into dropping the habit. Great, thank you :) thanks to yours truly. My what? Nothing :). Yours truly == me in a message written by me. http://dictionary.reference.com/browse/yours+truly http://en.wikipedia.org/wiki/Valediction#Yours_truly.2C Ah. I knew yours truly was a closer in a letter/e-mail, like Yours truly/sincerely/foo, David. Funny idioms, really :P Yours truly (:P), David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [Bash-completion-commits] [SCM] bash-completion branch, frozen/1.0, updated. 79ef58feca717e6872f4696fd7e7db8f7dc57d0b
On Tue, 31 Mar 2009 20:13:33 +0300, Ville Skyttä wrote: On Tuesday 31 March 2009, David Paleino wrote: diff --git a/CHANGES b/CHANGES index 3f31302..d7365ff 100644 --- a/CHANGES +++ b/CHANGES @@ -141,6 +141,12 @@ bash-completion (1.0) * Remove obsolete --buildarch and --buildos rpm(build) completions. * Add rpmbuild --target completion. * Use -profile help to get mplayer and friends -profile completions. + * Split yum and yum-arch completion into contrib/yum. + * Install yum-arch completion only if yum-arch is installed. + * Update list of yum commands and options. + * Add yum repolist, --enable/disablerepo, and --disableexcludes completions. These four added lines should not have been added to 1.0 because the actual changes they describe are not in 1.0, they're only in master. Fixed :) Please next time do separate logical commits :P (I usually do: 1 feature/bugfixing/whatever + 1 changelog line → commit) Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [Bash-completion-commits] [SCM] bash-completion branch, master, updated. 0f2656669fbdf627a3ddf11bdb72e3ec9cef68fd
On Wed, 1 Apr 2009 16:32:06 -0400, Todd Zullinger wrote: David Paleino wrote: What are you guys using? What's your development workflow? There shouldn't be any merges in master. I'm curious, why not? There are plenty of merges in the git.git logs. Just gut feelings, probably there aren't any problems with merges :) I just encountered problems when trying to cherry-pick, but I shouldn't probably cherry-pick merges :P... The trick should be using -n in git-cherry-pick. Example: mybranch $ [hack] git commit [aaa] My log mybranch $ [hack] git commit [bbb] My log 2 master $ git cherry-pick -n aaa master $ git cherry-pick -n bbb master $ git commit One disadvantage of using cherry-pick a lot is that it creates a new commit, rather than an exact copy of the original commit. This can affect git's merge tracking abilities and makes it harder to tell that all commits from a given branch have been merged fully into another branch. Ooh, right. I don't know if it'd be useful at all, but the MaintNotes¹ and maintain-git.txt² docs have a lot of good information in them. Thank you for the links! David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Debian development split out
Hello *, after the release, I'm preparing the Debian package :). I tried to work with different branches, but it's quite difficult (i.e. I'd need a debian/ branch, which merges from 1.0, but our tools also need a tarball, [..]). So I decided to split Debian packaging out of the main repository. The main repository will soon have debian/ and extra/ dropped also from master. The new repository is at: git://git.debian.org/git/bash-completion/debian.git If you want, you can setup per-distribution repositories there, if you want (there's a nice setup-repository script in /git/bash-completion/ on Alioth). As soon as I get the repository fully working, I'll start dropping (and merging the relevant things) Debian-specific things in master. If you happen to fix Debian bugs, please still do that in CHANGES (i.e. Debian: #nnn, or Ubuntu: #nnn). Thank you, David Paleino -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#518561: bash-completion: does not include hosts known through mDNS/DNS-SD (avahi)
On Fri, 06 Mar 2009 23:03:26 -0500, Servilio Afre Puentes wrote: Package: bash-completion Version: 20060301-4ubuntu1 Severity: normal Tags: patch In a LAN this can be very useful. Is someone using Avahi? Anyone able to test the patch? :) David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#522545: Bug#522545: bash-completion: configuration file conflict with mtx
# explanation for this later...
clone 522545 -1
reassign -1 mtx
retitle -1 please update bash-completion
owner -1 bash-completion-devel@lists.alioth.debian.org
user -1 bash-completion-devel@lists.alioth.debian.org
usertags -1 move-completions-upstream
thanks
Hello Bdale,
On Sun, 05 Apr 2009 18:41:15 -0600, Bdale Garbee wrote:
On Sat, 2009-04-04 at 21:03 +0200, David Paleino wrote:
processing
/var/cache/debtorrent/ftp.pl.debian.org_debian_dists_unstable_main_binary-all/pool/main/b/bash-completion/bash-completion_1.0-1_all.deb
(--unpack): trying to overwrite `/etc/bash_completion.d/mtx', which is
also in package mtx
Is the version in mtx updated? If not, I'd suggest mtx's maintainer (CCed)
to grab the one from bash-completion's git repo.
http://git.debian.org/?p=bash-completion/bash-completion.git;a=blob_plain;f=contrib/mtx;hb=a4c9bdc1774d234f322d214cf7636c10bd2db1c0
So, what's the right strategy for these? I added the file in Feb 2004
on request from Jon Middleton, per Debian bug #227456. I haven't given
it a single thought since then...
Does it make sense for me to continue to include the bash completion
file in the mtx package,
Please do so, as already replied by Luk.
or should I instead stop including it and add a suggests on bash-completion
to the package dependencies?
Please don't.
We're planning to purg bash-completion from third-party files -- we're going
to give only a framework people can use to write completions. Yes, we'll also
help writing completions (or do that on our own), but those will be
maintained/packaged/submitted upstream (not sure about maintained, but this is
another question).
As suggested by Luk, I've given the completion a look. I'm attaching a general
patch, since I don't have one of those devices mtx controls :) (so I'm not
really able to parse mtx status for tapes and drives)
The most notable thing is:
-cur=${COMP_WORDS[COMP_CWORD]}
+cur=`_get_cword`
(the rest of the patch is preventive)
Also, I kindly ask you to use dh_bash-completion: we're soon going to change
directory layout structure (yes, we'll have some compatibility level), and I'll
update dh_bash-completion accordingly when this happens. dh_bash-completion(1)
is your friend :)
(basically, your package needs no modifications to use it. Just the patch I'm
attaching ;) -- the above quoted fragment *must* be applied)
Thank you,
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
mtx.diff.gz
Description: GNU Zip compressed data
signature.asc
Description: PGP signature
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] RFC: Better long option with argument completion
On Mon, 13 Apr 2009 14:23:09 +0300, Ville Skyttä wrote:
Hello,
Hello Ville,
Currently completion of long options that take arguments is pretty bad.
Yes, definitely.
For an example, many completions list things like --foo= in their compgen
-W strings which end up completed as --foo\= which is annoying, especially
the trailing space. Some completions use internal workarounds for this
which is suboptimal from maintenance point of view.
With bash 4.x I suppose we could use compopt -o nospace but I suggest doing
something about this already now.
Agreed.
So I came up with the attached patch. The idea is that for all long options
that take an argument and can take it in both --foo=bar and --foo bar
forms, we only list --foo (not --foo=) in completions, run it through
_split_longopt, and code the completion logic as if --foo bar had been
passed and it'll work for both --foo=bar and --foo bar.
The patch looks good to me, just one *curiosity* (i.e. only curiosity, nothing
to fix :P): why are you quoting
+ prev=${cur%%?(\\)=*}
+ cur=${cur#*=}
? I'm in favour of *always* quoting things, just to be safe, but was just
curious if there was a specific reason here. I never found a longopt with
embedded space :)
Additionally, using the return value of _split_longopt we can return 0
early to avoid doing potentially weird/slow things with last resort default
completions later when a --foo=bar thing is being completed and we don't have
specific completions for the required argument for --foo (the assumption
being that if --foo= is specified, --foo requires an argument).
Good, that would speed up things a bit.
The attached patch contains _split_longopt and a few modifications to
existing completions to illustrate its usage and how it helps and what kind
of cleanups and improved features it allows.
Comments? I would like to commit _split_longopt soon and start changing
existing completions to use it.
I'm fully in favour of it.
As soon as you'll commit the patch (if there are no other objections), I'll
start fixing completions too. :)
Thank you for your work,
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] wget completion
On Tue, 14 Apr 2009 09:31:55 +0200, David Paleino wrote: On Tue, 14 Apr 2009 00:19:21 +0200, gibbo...@gmail.com wrote: A small 'up' as I spent again some hours to get rid of these ':' completion problem [..] Maybe the 'scp' completion author would have an advice ? [..] Did you try setting cur=`_get_cword :` ? :) IIRC that should work correctly. Ah, ok, I haven't read the rest of the thread, Freddy already suggested that. :/ I'll try to have a look at your completion ASAP, probably this evening (CET). Ciao, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [SCM] bash-completion branch, master, updated. 95cd673b5cbd5658cbf56a56a4113722aab92177
On Tue, 14 Apr 2009 18:24:23 +, Ville Skyttä wrote:
@@ -884,8 +885,14 @@ _mount()
| grep ^$cur ) )
else
# probably Linux
- COMPREPLY=( $( awk '! /^[ \t]*#/ {if ($2 ~ /\//) print $2}' \
+ if [ $prev = -L ]; then
[..]
+ elif [ $prev = -U ]; then
+ [..]
+ else
+ [..]
+ fi
Why not case..esac? :)
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#524190: bash-completion: SSH completion of know hosts doesn't handle multiple host files
forwarded 524190 https://alioth.debian.org/tracker/?func=detailaid=311595 tags 524190 upstream confirmed thanks Hello Thomas, On Wed, 15 Apr 2009 13:41:55 +0200, Thomas Nilsson wrote: Package: bash-completion Version: 1:1.0-2 Severity: normal Tags: patch Thank you for the patch! From a quick look, I believe we'll merge it upstream. I'll ask for comments to other team members though. [..] The eval line used to expand $HOME etc, is dangerous (probably only for the users of a system if you have a BOFH). With multiple entries the next entry will be tried to be executed; This is a known issue, already reported in our upstream tracker (see the URL above). Thank you for reporting, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [Bash-completion-commits] [SCM] bash-completion branch, master, updated. 5ece6956cf2410185616dfec92b301d28fafcec3
On Thu, 16 Apr 2009 09:22:20 +0200, Freddy Vulto wrote: On Thu, Apr 16, 2009 at 8:43 AM, David Paleino d.pale...@gmail.com wrote: Use \n instead of \r\n as line separator Hello David, Hello Freddy, Actually `main.xml' is generated: maybe we'd better put in the git ignore list or specify a tmp directory. Removed it, and put in .gitignore `main.txt' is the main file to edit. Heh, that was the one already containing ^M (i.e. \r\n) characters :) The `a2x' command in `makeHtml.sh' converts `main.txt` to `main.xml` and further to html. Okay, I'll study asciidoc a bit. Thank you, David (who has to complete the bash-completion talk presentation *now*) -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#524961: bash-completion: Tab completion of svk command line forgets to escape filenames
tags 514961 confirmed pending patch thanks On Tue, 21 Apr 2009 17:16:50 +1000, Brendon Higgins wrote: Package: bash-completion Version: 1:1.0-2 Severity: normal Hi, Hello, Try this: touch filename with spaces svk add filenTAB The completion I get is svk add filename with spaces. Note that the completion does not escape the spaces in the filename. When you try to run the command, svk looks for the files filename, with, and spaces and, of course, fails. This was a bug in svk completion. Fixed in git 7c023ab. You should expect the completion to be svk add filename\ with\ spaces like everything else. If you can't wait for the new release :), please change $default with $filenames in /etc/bash_completion.d/svk (and re-login) Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Spam on this list
On Fri, 8 May 2009 20:45:57 +0300, Ville Skyttä wrote: Hello, Hello Ville, There seems to be some spam coming through to this list. Unfortunately yes. Is the list subscribers-can-post-only? If not, why not? It's not. I suppose Luk decided to make it this way to make users freely report to the list, without having to subscribe. Also, I believe there could be problems with the sending of Debian bugreports/DEHS mails/whatever (this address is set as Maintainer of the Debian package) -- but I'm not very sure and I should check. David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Question on subversion completion
On Mon, 11 May 2009 15:44:49 +0200, Niels Thykier wrote: Hi Bash-completion team + subversion maintainer Hello, [..] Namely why is debian shipping with two different bash_completions for subversion? I have one from bash_completion v1:1.0-2 and one from subversion v1.5.6dfsg-1(determined via apt-file): Because we had a subversion completion, but didn't check whether it was complete or not. Thus we renamed it as _subversion. [..] On my system it seems that the _subversion file overrules the subversion (I only checked the _svn function, and assumed this precedence held for the other svn-commands). AFAICT _ should come before s, so subversion should really overrule _subversion... but I didn't really try this, so sorry if it happened the opposite -- I'll fix it in the next Debian revision (and consequently upstream) David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#529510: checks for GNUish userland fail on GNU/kFreeBSD, GNU/kOpenSolaris, etc
tags 529510 fixed-upstream thanks Hello, On Tue, 19 May 2009 18:13:12 +, Robert Millan wrote: The checks for GNUish userland are made unportably by using a hardcoded list of uname values. It should use GNU/* and match other systems like GNU/kFreeBSD or GNU/kOpenSolaris. Also, the check for sed relies on comparing uname with Linux but it's actually a userland issue. Patch attached. Thanks, patch applied upstream: http://git.debian.org/?p=bash-completion/bash-completion.git;a=commitdiff;h=4fadb6887aa48cb4b835209a2733010f5f94c3cb I will be preparing a new Debian revision ASAP. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#529357: bash-completion: Fail to complete file with something between square brackets
tags 529357 unreproducible thanks Hello Leandro, I can't really reproduce the bug here, with the current development version: On Mon, 18 May 2009 17:19:36 -0300, Leandro Lucarella wrote: l...@azazel:~$ touch /tmp/'[' l...@azazel:~$ ls /tmp/\[ # 'ls /tmp/['tab written $ touch [ $ ls [TAB $ ls \[TAB [ $ ls \[ l...@azazel:~$ touch /tmp/'[]' l...@azazel:~$ ls /tmp/\[ # 'ls /tmp/['tab written [ [] $ touch [] $ ls [TAB $ ls \[TAB [ [] $ ls \[ l...@azazel:~$ touch /tmp/'[2]' l...@azazel:~$ ls /tmp/\[ # 'ls /tmp/['tab written [ [] $ touch [2] $ ls [TAB $ ls \[TAB [[] [2] $ ls \[ l...@azazel:~$ vi /tmp/\[ # 'vi /tmp/['tab written [ [] $ vi [TAB $ vi \[TAB [[] [2] $ vi \[ l...@azazel:~$ cd /tmp/\[ # 'cd /tmp/['tab written [ [] Not tested -- and that shouldn't have worked for you. `cd' should only complete on directories, and with touch you didn't create directories: $ cd [TAB $ cd [ l...@azazel:~$ touch /tmp/'[a]' l...@azazel:~$ ls /tmp/\[ # 'ls /tmp/['tab written [ [] $ touch [a] $ ls [TAB $ ls \[ $ ls \[TAB [[] [2] [a] $ ls \[ As you can see, '[2]' and '[a]' fails to complete. The other files with '[' and '[]' work well. I can't really see this behaviour, thus marking this bug as unreproducible. Would you please try the current development version? http://git.debian.org/?p=bash-completion/bash-completion.git;a=blob_plain;f=bash_completion;hb=HEAD Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [Bash-completion-commits] [SCM] bash-completion branch, master, updated. 4fadb6887aa48cb4b835209a2733010f5f94c3cb
On Thu, 21 May 2009 00:48:42 +0300, Ville Skyttä wrote: On Wednesday 20 May 2009, David Paleino wrote: The following commit has been merged in the master branch: commit 4fadb6887aa48cb4b835209a2733010f5f94c3cb Author: David Paleino d.pale...@gmail.com Date: Wed May 20 22:08:53 2009 +0200 Fix checks for GNUish userland, thanks to Robert Millan (Debian: #529510) Shouldnt USERLAND be unset at the end of bash_completion when it's no longer needed like other such variables? Yes, sorry, I missed that (and I manually applied the patch just to avoid missing pieces... lol). Fixed now. Spelling it in lowercase might also make it clearer that it's not a global variable that should persist. Well, I applied it as Robert sent it because it was consistent with $UNAME -- but we could lowercase both, I have no hard feelings on that. David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [SCM] bash-completion branch, master, updated. 65d9348f3e5a31adf38ace19a3c1d4e6a302fe9e
Hello, On Sat, 23 May 2009 08:45:49 +, Ville Skyttä wrote: The following commit has been merged in the master branch: commit 65d9348f3e5a31adf38ace19a3c1d4e6a302fe9e Author: Ville Skyttä ville.sky...@iki.fi Date: Sat May 23 11:45:39 2009 +0300 Fix man completion (was broken by recent $UNAME/$USERLAND changes). How was that broken? man(1) completion is working here, and I haven't yet pulled this commit. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [SCM] bash-completion branch, master, updated. 65d9348f3e5a31adf38ace19a3c1d4e6a302fe9e
On Sun, 24 May 2009 10:48:10 +0300, Ville Skyttä wrote: On Saturday 23 May 2009, David Paleino wrote: Hello, On Sat, 23 May 2009 08:45:49 +, Ville Skyttä wrote: The following commit has been merged in the master branch: commit 65d9348f3e5a31adf38ace19a3c1d4e6a302fe9e Author: Ville Skyttä ville.sky...@iki.fi Date: Sat May 23 11:45:39 2009 +0300 Fix man completion (was broken by recent $UNAME/$USERLAND changes). How was that broken? man(1) completion is working here, and I haven't yet pulled this commit. $USERLAND is not set inside _man() when it runs (and it shouldn't be): $ man + local cur prev sect manpath manext mansect UNAME + manext='@([0-9lnp]|[0-9][px]|man)?(.@(gz|bz2|lzma))' + mansect='@([0-9lnp]|[0-9][px])' + COMPREPLY=() ++ _get_cword ++ [[ 0 -eq 0 ]] ++ printf %s '' + cur= + prev=man + [[ man == -l ]] + _expand + [[ '' == \~*/* ]] + [[ '' == \~* ]] + [[ '' == */* ]] ++ uname -s + UNAME=Linux + UNAME=Linux + '[' = GNU -o Linux = FreeBSD -o Linux = Cygwin ']' bash: [: too many arguments It could be that it worked before USERLAND was unset at the end of bash_completion by another commit which I requested, perhaps you weren't running with a version that had that commit applied? Well: $ grep BASH .bash* .bashrc:export BASH_COMPLETION=/deb/git/bash-completion/bash_completion .bashrc:export BASH_COMPLETION_DIR=/deb/git/bash-completion/contrib $ And I tried man completion from within that session. Nevermind :), David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [SCM] bash-completion branch, master, updated. 65d9348f3e5a31adf38ace19a3c1d4e6a302fe9e
On Sun, 24 May 2009 11:07:40 +0300, Ville Skyttä wrote: On Sunday 24 May 2009, David Paleino wrote: $ grep BASH .bash* .bashrc:export BASH_COMPLETION=/deb/git/bash-completion/bash_completion .bashrc:export BASH_COMPLETION_DIR=/deb/git/bash-completion/contrib Hmm, interesting, I should set up something like that for myself too. But how does that work; do you have another line somewhere in your profile which sources $BASH_COMPLETION that you set in the above? Those variables are used by bash_completion itself (see at the very beginning of the file). There you go: $ grep git/bash-completion ~/.bashrc export BASH_COMPLETION=/deb/git/bash-completion/bash_completion export BASH_COMPLETION_DIR=/deb/git/bash-completion/contrib . /deb/git/bash-completion/bash_completion $ (surely I could've done . $BASH_COMPLETION) This way, you're always using the latest git commit you have locally pulled. Hope this helps, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#529510: [db5f45a] Fix for Bug#529510 committed to git
tags 529510 +pending thanks Hello, The following change has been committed for this bug by David Paleino d.pale...@gmail.com on Sat, 30 May 2009 19:15:45 +0200. The fix will be in the next upload. = debian/patches/01-529510.patch added, checks for GNUish userland fail on GNU/kFreeBSD, GNU/kOpenSolaris, etc (Closes: #529510) = You can check the diff of the fix at: http://git.debian.org/?p=/srv/git.debian.org/git/bash-completion/debian.git;a=commitdiff;h=db5f45a ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#522656: [ce427fa] Fix for Bug#522656 committed to git
tags 522656 +pending thanks Hello, The following change has been committed for this bug by David Paleino d.pale...@gmail.com on Sat, 30 May 2009 19:29:03 +0200. The fix will be in the next upload. = 03-522656.patch added, evince supports compressed dvi files (Closes: #522656) = You can check the diff of the fix at: http://git.debian.org/?p=/srv/git.debian.org/git/bash-completion/debian.git;a=commitdiff;h=ce427fa ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#495883: [e2b2513] Fix for Bug#495883 committed to git
tags 495883 +pending thanks Hello, The following change has been committed for this bug by David Paleino d.pale...@gmail.com on Sat, 30 May 2009 19:31:37 +0200. The fix will be in the next upload. = 04-495883.patch added, aptitude: add build-dep to bash_completion (Closes: #495883) = You can check the diff of the fix at: http://git.debian.org/?p=/srv/git.debian.org/git/bash-completion/debian.git;a=commitdiff;h=e2b2513 ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Mail from Debian BTS
On Mon, 1 Jun 2009 20:45:56 +0300, Ville Skyttä wrote: Hello, Hello Ville, I find the amount of mail originating from the Debian BTS to this list quite excessive. For example, I've received at least 9 mails about Debian bug 531337 yesterday/today, some of which are pretty much gibberish to me (some kind of machine generated processing reports), and others look pretty much like duplicates. Yes, sorry, it was a post-receive hook in git, and I've already disabled it altogether soon after seeing the bunch of mails arriving. One mail would have been enough, and I'm not sure if even that is necessary; no other distro BTS does that either. Is there a way to at least decrease the amount of the Debian BTS mail, if getting rid of it altogether on this list is not found desirable by others? I'd rather welcome if other distributions drive their mails here too. I'm really sorry for the mess happened, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Extending dh_bash-completion
Thanks Iain :) On Tue, 02 Jun 2009 22:34:09 +0100, Iain Lane wrote: On Tue, 2009-06-02 at 22:56 +0200, Federico Hernandez wrote: Hi! Hello Federico, I was thinking of extending the functionality in dh_bash-completion. While packaging my first package (task on revu - still waiting for some reviews - shameless plug) I discovered that dh_bash-completion expects a file called debian/bash-completion to be copied to /etc/bash_completion.d/name-of-package. Yes, or... So it behaves differently to, let's say, dh_installdocs which either can use filenames arguments or copies the files mentioned in debian/docs to the documentation directory. ..this. There was a bug filed about this, and dh_bash-completion tries to understand whether debian/bash-completion is a shell fragment (and installs it into the proper directory), or a list of filenames (and installs those). I want now to extend dh_bash-completion do behave in the same way. I would assume the following 3 cases: 1) There is a file called debian/bash-completion. Then copy that file to /etc/bash_completion.d/name-of-package. Does that already. 2) dh_bash-completion is called with arguments. Copy the arguments (files) to /etc/bash_completion.d using packagename_filename as the new destianation names. Can't really tell whether it does this or not, I should check (too tired now to do it :)) 3) There is a file called debian/completions. Copy the files mentioned there to /etc/bash_completion.d using packagename_filename as the new destionation names. Why diverging with completions instead of bash-completion? However, it already does this. *And*, I don't really agree to change the completion names. However, those changes you're asking were uploaded on Fri, 03 Apr 2009 14:21:43 +0200, with version 1:1.0-1 in Debian. The bug is http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512917 . The fact is: Ubuntu hasn't synced bash-completion for a while (we also changed version numbering scheme in the meanwhile!) Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Dropping _subversion (was: Re: [Bash-completion-commits] [SCM] bash-completion branch, master, updated. 81e48606d011a96393ae2ae713bc6cda0fb18249)
On Fri, 5 Jun 2009 18:47:18 +0300, Ville Skyttä wrote: On Friday 05 June 2009, Guillaume Rousse wrote: David Paleino a écrit : The following commit has been merged in the master branch: commit 81e48606d011a96393ae2ae713bc6cda0fb18249 Author: David Paleino d.pale...@gmail.com Date: Fri Jun 5 08:30:26 2009 +0200 Don't install _subversion anymore Which means it isn't distributed either... I'd prefer to keep it available in the archive. What's the reason for not installing it anyway? If there is a good one, I think it should at least be mentioned in the change log. Didn't we agree that upstream one was better than our? Wasn't that also the reason to install it as _subversion, i.e. to avoid filename collision with upstream's? Anyway, we could also revert that commit, no hard feelings about it. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] [Bash-completion-commits] [SCM] bash-completion branch, master, updated. 81e48606d011a96393ae2ae713bc6cda0fb18249
On Fri, 05 Jun 2009 09:55:42 +0200, Guillaume Rousse wrote: David Paleino a écrit : The following commit has been merged in the master branch: commit 81e48606d011a96393ae2ae713bc6cda0fb18249 Author: David Paleino d.pale...@gmail.com Date: Fri Jun 5 08:30:26 2009 +0200 Don't install _subversion anymore Which means it isn't distributed either... I'd prefer to keep it available in the archive. Maybe we should find a way to distribute it in the tarball, but not install it on make install? David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] unalias sed? (was: Re: [Bash-completion-commits] [SCM] bash-completion branch, master, updated. b14fdb74b3b7fd7a707bc2afea55c10ea521d4f0)
On Fri, 5 Jun 2009 18:41:07 +0300, Ville Skyttä wrote: On Friday 05 June 2009, David Paleino wrote: Hi David, Hello Ville, The following commit has been merged in the master branch: commit 6170eb0001510426ccc7461e60e46c68992bcd14 Author: David Paleino d.pale...@gmail.com Date: Fri Jun 5 08:13:46 2009 +0200 Don't assume sed being GNU sed, use gsed whenever available (Debian: #501479, Alioth: #311393) [...] @@ -3673,3 +3673,6 @@ unset UNAME USERLAND default dirnames filenames have nospace bashdefault plusdir set $BASH_COMPLETION_ORIGINAL_V_VALUE unset BASH_COMPLETION_ORIGINAL_V_VALUE + +# remove aliases we set earlier +unalias sed Like I explained in Alioth #311393, I believe the unalias here is wrong - it results in our aliased sed being in effect only for the duration of reading bash_completion and the split files, not at runtime when sed gets actually invoked and we for now want it to cope with GNU sed extensions. Ok, good. What about: alias mysed=sed have gsed alias mysed=gsed ? (we can obviously change mysed to something else, it's just to clarify the solution) Did I miss something? It's me who actually missed your point, sorry. Commit reverted, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Dropping _subversion
On Sat, 6 Jun 2009 00:44:18 +0300, Ville Skyttä wrote: On Friday 05 June 2009, David Paleino wrote: On Fri, 5 Jun 2009 18:47:18 +0300, Ville Skyttä wrote: What's the reason for not installing it anyway? If there is a good one, I think it should at least be mentioned in the change log. Didn't we agree that upstream one was better than our? Wasn't that also the reason to install it as _subversion, i.e. to avoid filename collision with upstream's? I don't recall any of that, perhaps I wasn't yet following upstream bash- completion when that was discussed [0]. And I'm certain a lot of bash- completion users don't do that either, therefore this information would be very good to have in CHANGES to avoid confusion (that's what I did when I removed hg). Added. Anyway, we could also revert that commit, no hard feelings about it. Like Guillaume, I'd prefer if it was kept around in the dist tarball for a while even if not installed by default. Add it to EXTRA_DIST in Makefile.am? Done now :) [0] Actually I've several times had the intention to ask why it was named _subversion with the underscore but never did; anyway now I know ;) Eh, sorry, I don't know where that discussion was made, maybe also on IRC only between me and Luk? Or maybe some bugreport? Can't really recall :( David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#531343: bash-completion: Regression - 'man' does not complete on *.3pm files
tags 531343 fixed-upstream thanks Hello, On Sun, 31 May 2009 19:38:10 +0100, Paul LeoNerd Evans wrote: Package: bash-completion Version: 1:1.0-2 Severity: normal The tab-complete for 'man' used to complete on local *.3pm files as perl manpages; it doesn't any more $ ls blib/libdoc/*.3pm blib/libdoc/IO::Async.3pm blib/libdoc/IO::Async::Notifier.3pm ... $ man blib/libdoc/tabtab [ no response ] It would be useful if it would do this again please... $ mkdir -p foo/bar/baz/ $ touch foo/bar/baz/Foo.3pm $ man foTAB fold form_driverform_new_page font2c form_field form_opts font2psf form_field_attributes form_opts_off fontinst form_field_buffer form_opts_on fonts-conf form_field_infoform_page fonttosfnt form_field_justform_post foo/ form_field_new form_request_by_name fopen form_field_optsform_requestname fopencookieform_fieldsform_request_name fork form_fieldtype form_sub forkptyform_field_userptr form_term form form_field_validation form_userptr format form_hook form_win form_cursorform_init fort77 form_data form_new fortune $ man fooTAB $ man ./foo/TAB $ man ./foo/bar/TAB $ man ./foo/bar/baz/TAB $ man ./foo/bar/baz/Foo.3pm Seems working here, with the latest git revision :) Marking the bug fixed-upstream. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#544024: Completion with backslashes broken
On Fri, 4 Sep 2009 23:06:06 +0300, Ville Skyttä wrote:
On Thursday 03 September 2009, Norbert Preining wrote:
On Do, 03 Sep 2009, EspeonEefi wrote:
--- /etc/bash_completion.orig 2009-09-03 08:21:15.229720217 -0400
+++ /etc/bash_completion 2009-09-03 08:21:36.473719600 -0400
@@ -213,6 +213,10 @@
# results in the original argument
quote_readline()
{
+ if [ ${BASH_VERSINFO[0]} -gt 3 ]; then
+ echo $1
+ return
+ fi
local t=${1//\\/}
echo \'${t//\'/\'\\\'\'}\' #'# Help vim syntax highlighting
}
Thanks, that at least fixed the problem for me. I have added
these 4 lines for now and hope for what upstream is doing.
Practically the same thing. There's just no release with this fix out yet.
http://git.debian.org/?p=bash-completion/bash-
completion.git;a=commitdiff;h=1421e55aac075e13491cd212b796bdd453214a2c
http://git.debian.org/?p=bash-completion/bash-
completion.git;a=commitdiff;h=4475d3634923de7a169c67aaa197f388bb418de8
I hope we can get a release out in September :)
Kindly,
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] New version 1.1 -- release date
Hello people, I'm having exams, so I can't really be of help in preparing a release for 1.1 *now*. I thought we can make a release on Sep 30/Oct 1 -- what's your opinion on this? Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#417864: debconf: bash completion does not work with dpkg-reconfigure
Version: 1:1.0-3 Hello, seems like this has been fixed in more recent versions of bash-completion -- I can't reproduce it with 1.0, thus closing the bug. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Bug#523611: bash-completion for man should recognise -l
Version: 1:1.0-3 Hello, I'm closing this bug since it has been fixed somewhen in the past (can't get the exact commit, since the file has been moved around in the repository after the fix had been pushed), and is no more reproducible with the package currently available in Debian. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] Completing on comma-separated list
Hello people, On Fri, 18 Sep 2009 22:54:49 +, David Paleino wrote: The following commit has been merged in the master branch: commit c200e468d61b88bcf4d14253daf42c066929bfa9 Author: David Paleino d.pale...@gmail.com Date: Fri Sep 18 23:59:41 2009 +0200 Added completion for lintian/lintian-info [..] +#-@(T|-tags)) +## This option wants a comma-separated list +## Disabled because completion doesn't work right after the comma. +#compopt -o nospace lintian +#COMPREPLY=( $( compgen -S',' -W '$( grep ^Tag /usr/share/lintian/checks/*.desc | cut -d\ -f2 )' -- $cur ) ) +#return 0 +#;; lintian(1) (that's a Debian QA tool) expects a comma-separated list, and the above completion fails. Any idea how to accomplish this? The expected behaviour would be (| cursor, tab): $ lintian -T tag1, tag2,tag3, $ lintian -T tag1,# The first one gets correctly completed tag1, tag2,tag3, # I don't really care whether it repeats tag1 $ While it currently does: $ lintian -T tag1, tag2,tag3, $ lintian -T tag1, $ lintian -T tag1,| The same goes with some other options, which I didn't notice accepted a comma-separated list (it doesn't matter whether there is a trailing comma, even if it would be nice to drop it) Any idea on how to achieve this? Otherwise, I can offer completion just for the first item, then go back to options completion. Kindly, David -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] Bug#547361: please add bash completion
reassign 547361 bash-completion
retitle 547361 please add completion for lintian and lintian-info
tags 547361 confirmed
thanks
On Sat, 19 Sep 2009 11:58:48 -0700, Russ Allbery wrote:
David Paleino d.pale...@gmail.com writes:
On Fri, 18 Sep 2009 17:38:00 -0700, Russ Allbery wrote:
I'm going to completely forget to update this file for additional
checks or collection scripts. Is there any way, in bash completion
rules, to make the completion of those arguments be based on the files
installed in /usr/share/lintian/{checks,collection} instead?
There is, but I couldn't find anywhere where the aliases are defined,
i.e. chg for changelog-file, for instance. Could you give me a
pointer?
Those aren't, unfortunately. I think they're of somewhat questionable
utility, though.
Raphael told me on IRC they are in the .desc files, and indeed they are :):
$ grep ^Abbrev /usr/share/lintian/checks/*.desc | cut -d\ -f2
I'd be good with either listing the aliases manually and combining that
with the file names or just having the file names available. I suspect
most people will use the file names anyway, and I wonder from time to time
if we should just drop the aliases, although that means breaking backward
compatibility. If you list the aliases, I'll try to remember to update
them, but I think missing some will be less important than missing a whole
class of checks if I forget.
I can now provide aliases. *But*, since lintian options only accept
comma-separated lists, this is a bit harder to achieve. I asked help to other
bashcomp team members to see whether they have ever done something like that.
Also, we're probably going to change plans about pushing completions to
respective upstreams -- that would cause maintainance headaches to us (or no
maintainance at all!), so we'll probably change our decision.
So, I'll try to fix the completion and I'll eventually provide one (even with
limited capabilities, better than nothing), but I'm reassigning the bug to
bash-completion until we definitely decide where to put completions :)
Sorry for the noise ;)
David
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
[Bash-completion-devel] dd completion not working (was: Fwd: [arch-general] dd and bash_completion)
On Thursday 24 September 2009 17:50:31 you wrote: Hello, Hello, next time please use the mailing list address (and, Luk is not anymore involved in bash_completion) The dd bash completion file does not seem to work at all. I spent some times trying to debug/hack it today, but I was not familiar with bash completion at all, and I have not been successful. I don't have much time right now, so I'm forwarding it to the mailing list where other developers are subscribed too. I could look at it when I get some free time though (not in the next five-six days, really) :) Thank you, David -- Forwarded message -- From: Thomas Göbel goebel.tho...@gmx.net Date: Wed, Sep 23, 2009 at 1:15 PM Subject: [arch-general] dd and bash_completion To: arch-gene...@archlinux.org Hi all, i noticed that bash_completion and dd do not work together. Tiping dd if=/hTAB will not complete to if=/home. Without bash_completion everything works fine. Maybo someone knows how to fix this? Tom -- () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: This is a digitally signed message part. ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Re: [Bash-completion-devel] dd completion not working (was: Fwd: [arch-general] dd and bash_completion)
Freddy Vulto wrote: On Thu, Sep 24, 2009 at 6:36 PM, David Paleino d.pale...@gmail.com wrote: This is due to COMP_WORDBREAKS containing =: I guess this bug turns up on bash-4 only? This can be fixed by adding `=' as an argument to `_get_cword' so that _get_cword on bash-4 doesn't split words on `='. Done so in commit f871fe4. It didn't really fix the completion, for me at least. [..] If you use COMP_CWORDS, this is what you get on bash-4: $ dd if=TAB This is even more broken earlier: $ dd ifTAB $ dd if\= And completion fails. With your fix, we only get right completions if you only TAB after the = (and write it manually). Thanks for your work! David (getting lost in the complexity of _get_cword()) -- . ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://snipr.com/qa_page `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 ___ Bash-completion-devel mailing list Bash-completion-devel@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
