Re: [Bash-completion-devel] hostname completion issues

2009-06-18 Thread Guillaume Rousse

Freddy Vulto a écrit :

On Wed, Jun 17, 2009 at 10:26 PM, Ville Skyttäville.sky...@iki.fi wrote:

Some recent changes (known hosts stuff?) have broken ssh hostname completion
quite badly for me in git master.

...

This is with bash 3.2.39(1)-release.  Anyone else seeing this?  Anyone working
on known hosts completion?


Yes, I'm having the same problem.  I think it's caused by my recent
changes concerning _known_hosts_real.  From a quick look it appears
the `getopts' in _known_hosts_real isn't catching the -h $cur
option.  I'll have a further look as soon as I have some more time.
_known_hosts_real was supposed to have a mandatory host argument, by 
contrast to _known_hosts. Otherwise, there is no use to split those two 
functions, we could use a single one.


And I favor the splitted solution because:
- calling directly the function with the proper behaviour is faster than 
having this function test its argument at runtime to select which 
behavior to use
- distinguishing between completion functions (those directly attached 
to a command) and helper functions (those called by completion 
functions) make the code easier to maintain
- bash isn't wise enough to to distinguish between an empty string 
argument and an non-existing one: calling the '_known_host -a' function 
with no current host will call '_known_host_real -h  -a', and result 
in completion for hosts called -a*


--
BOFH excuse #97:

Small animal kamikaze attack on power supplies

___
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] Processed: Re: Bug#531343: bash-completion: Regression - 'man' does not complete on *.3pm files

2009-06-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 531343 fixed-upstream
Bug#531343: bash-completion: Regression - 'man' does not complete on *.3pm files
There were no tags set.
Tags added: fixed-upstream

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

___
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

2009-06-18 Thread David Paleino
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


[Bash-completion-devel] Processed: tagging 524190, tagging 524190, forcibly merging 524190 525293

2009-06-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 524190 - patch
Bug#524190: bash-completion: SSH completion of know hosts doesn't handle 
multiple host files
Tags were: confirmed upstream patch
Tags removed: patch

 tags 524190 + fixed-upstream
Bug#524190: bash-completion: SSH completion of know hosts doesn't handle 
multiple host files
Tags were: confirmed upstream
Tags added: fixed-upstream

 forcemerge 524190 525293
Bug#524190: bash-completion: SSH completion of know hosts doesn't handle 
multiple host files
Bug#525293: bash-completion: scp completion clutters screen with error 
permission denied
Forcibly Merged 524190 525293.


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


___
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] Processed: closing 242298

2009-06-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 close 242298
Bug#242298: Request change standard .bashrc to help newbies
'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing.
Bug#116082: bash: Some debconf questions for defaults in .bash* files?
Bug#128997: bash-completion: debconf question for the addition to 
/etc/bash.bashrc?
Bug closed, send any further explanations to Jaap Haitsma j...@haitsma.org


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

___
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] Processed: tagging 518561

2009-06-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 tags 518561 fixed-upstream
Bug#518561: bash-completion: does not include hosts known through mDNS/DNS-SD 
(avahi)
Tags were: patch
Tags added: fixed-upstream


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

___
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#128997: acknowledged by developer (closing 242298)

2009-06-18 Thread Adrian Bunk
reopen 128997
thanks

Please read http://www.debian.org/Bugs/server-refcard which contains an 
explanation why to not use close.

Looking at the bug, your actions (tags -wontfix, tags +wontfix, close) 
also don't give me any clue why you suddenly changed your opinion 
from why shouldn't we fix this? and closed my bug.

Unless I miss anything, this issue in my 7 years old (sic) bug is still 
present, and something can be improved here.

cu
Adrian


On Thu, Jun 18, 2009 at 11:06:04AM +, Debian Bug Tracking System wrote:
 This is an automatic notification regarding your Bug report
 #128997: bash-completion: debconf question for the addition to 
 /etc/bash.bashrc?,
 which was filed against the bash-completion package.
 
 It has been marked as closed by one of the developers, namely
 David Paleino d.pale...@gmail.com.
 
 You should be hearing from them with a substantive response shortly,
 in case you haven't already. If not, please contact them directly.
 
 Debian bug tracking system administrator
 (administrator, Debian Bugs database)




___
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] Processed: Re: Bug#128997 acknowledged by developer (closing 242298)

2009-06-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

 reassign 128997 bash
Bug#128997: bash-completion: debconf question for the addition to 
/etc/bash.bashrc?
Bug#116082: bash: Some debconf questions for defaults in .bash* files?
Bug#242298: Request change standard .bashrc to help newbies
Bug reassigned from package `bash-completion' to `bash'.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

___
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] Hardcoded /sbin/lsmod

2009-06-18 Thread Mark Rosenstand
Hi,

Sorry for not reporting this through the bug tracker, I'm a bit short on time
but thought this is trivial enough to fix through a simple mail.

The path to lsmod seems to be hardcoded in 1.0 and git, making
modprobe -r completion bomb out on my system with a vanilla
module-init-tools 3.9 (./configure --prefix=/usr --exec-prefix=)

___
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] Hardcoded /sbin/lsmod

2009-06-18 Thread Raph
Seriously I don't know, but maybe to avoid the problem hitted
when you do, as unprivilieged user (U.P.):
/sbin/iptables -j TAB
I think it's a deep problem I don't remember having heard about :
the completion of commands which :
1) are in {,/usr}/sbin
2) but are usable read-only by an U.P.
It's sometimes usefull for a U.P. to use modprobe TAB
(Notice the $PATH and ifconfig in ubuntu for example)

That's why I think the current have() is not enough if the
current behavior is considered as a problem.
What about this kind of have() :
- return 0 if found
- return 1 if not found
- return 2 if we needs another $PATH than the user's original one
In this later case, we may use something like $(have -p $cmd) to get the
absolute path echoed and use it if needed.

Or a backward compatible solution :
- echo the absolute path of the command if found
- return 1 otherwise

my 2c

Raph

On Thu, Jun 18, 2009 at 05:43:41PM +0200, Mark Rosenstand wrote:
 Hi,
 
 Sorry for not reporting this through the bug tracker, I'm a bit short on time
 but thought this is trivial enough to fix through a simple mail.
 
 The path to lsmod seems to be hardcoded in 1.0 and git, making
 modprobe -r completion bomb out on my system with a vanilla
 module-init-tools 3.9 (./configure --prefix=/usr --exec-prefix=)
 
 ___
 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 mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel