[Bash-completion-devel] [bash-completion-Bugs][313514] ssh command completion failed

2012-01-17 Thread bash-completion-bugs 
Bugs item #313514, was changed at 2012-01-16 09:39 by Ville Skyttä
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detailatid=413095aid=313514group_id=100114

Status: Pending
Priority: 3
Submitted By: Neville Gao (figod-guest)
Assigned to: Nobody (None)
Summary: ssh command completion failed 
Distribution: Debian
Originally reported in: None
Milestone: None
Status: None
Original bug number: 


Initial Comment:
I'm using Debian testing (Wheezy), bash-completion v1.3. When I type ssh , 
and then type TAB key, there's an error saying sed: -e expression #1, char 97: 
invalid reference \2 on `s' command's RHS.

I think it is caused by some escaped backslash problems. I proposed a patch for 
reviewing in attached file.

--

Comment By: Ville Skyttä  (scop-guest)
Date: 2012-01-17 22:44

Message:
Please test with bash-completion 1.99 first.

--

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detailatid=413095aid=313514group_id=100114

___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel

[Bash-completion-devel] You Have An Incoming Payment Slated For Your Account

2012-01-17 Thread Kiwi Bank Limited 







View Your 
Statement Of Account






___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel

[Bash-completion-devel] [bash-completion-Bugs][311399] DBTS 313514: bash-completion fails with e.g., ls and newlines in file names

2012-01-17 Thread bash-completion-bugs 
Bugs item #311399, was changed at 2009-01-30 12:03 by Igor Murzov
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detailatid=413095aid=311399group_id=100114

Status: Open
Priority: 2
Submitted By: David Paleino (hanska-guest)
Assigned to: Nobody (None)
Summary: DBTS 313514: bash-completion fails with e.g., ls and newlines in file 
names  
Distribution: None
Originally reported in: Debian BTS
Milestone: None
Status: None
Original bug number: 313514


Initial Comment:
From: Anthony DeRobertis a...@suespammers.org
To: Debian Bug Tracking System sub...@bugs.debian.org
Subject: bash-completion fails with e.g., ls and newlines in file names
Date: Tue, 14 Jun 2005 01:37:41 -0400

Package: bash
Version: 3.0-15
Severity: minor
File: /etc/bash_completion

anthony@bohr:foo$ touch $(echo -e 'foo\nbar')
anthony@bohr:foo$ ls -b
foo\nbar
anthony@bohr:foo$ ls ftabtab
bar  foo  

Notice how instead of completing foo?bar (where ? = newline) it offers
to complete either foo or bar.


--

Comment By: Igor Murzov (garik-guest)
Date: 2012-01-18 03:45

Message:
The problem is caused by the `compgen` command which uses '\n' as a separator 
for generated completions, thus 'foo\nbar' is indistinguishable from 'foo' and 
'bar'. I can't see any sane way to workaround this issue reliably. The most 
sane fix probably is to avoid using `compgen -f` in _filedir() and use `find` 
or some other appropriate utility instead.

--

Comment By: David Paleino (hanska-guest)
Date: 2009-01-30 12:05

Message:
From: Michael Tweedale m...@ic.ac.uk
To: 313...@bugs.debian.org
Subject: Re: bash-completion fails with e.g., ls and newlines in file names - 
workaround
Date: Thu, 18 May 2006 12:29:44 +0100

Package: bash
Version: 3.1-4
Followup-For: Bug #313514

On  8 Nov 2005 at 11:29, Mike Dornberger wrote:
 Interesting point is, that it _only_ seems to break on 
 newlines.

It also chokes on filenames with an equals sign:
$ touch x=y
then
$ ls xTAB
completes correctly;
$ ls x=TAB
completes (bizarrely) to x=x\=y and
$ x=TAB
as expected completes to a list of all filenames in cwd 
(though if . is in $PATH maybe it should complete to x=y ?).

Best,
Michael

--

Comment By: David Paleino (hanska-guest)
Date: 2009-01-30 12:04

Message:
From: Mike Dornberger mike.dornber...@gmx.de
To: Debian Bug Tracking System 313...@bugs.debian.org
Subject: Re: bash-completion fails with e.g., ls and newlines in file names - 
workaround
Date: Tue, 8 Nov 2005 11:29:30 +0100

Package: bash
Version: 2.05b-26
Followup-For: Bug #313514

Hi,

this bug hit me today, too, when I wanted to delete filenames with
newlines.

Completion for mv, rm and ls (haven't tested others) show this bug, even if
you use M-* (insert-completions).

$ rm foM-*

results even to:

$ rm bar foo 

It does not fail on e. g. echo:

$ echo fotab

$ echo 'foo
bar' 

(M-* works here correctly, too.)

Interesting point is, that it _only_ seems to break on newlines. Doing

$ touch $(echo -e 'evil filename with\nan LF and other special chars ($bla) : 
, ')
$ rm evM-*

results in:

$ rm an\ LF\ and\ other\ special\ chars\ \(\$bla\)\ \:\ \,\ \ evil\ filename\ 
with 

As a little workaround one can either write

$ echo rm evtab

or

$ xrm evtab

then using C-a or Home and deleting echo  or x before execution. The
last one maybe only works if there isn't a xrm file/function/alias or
something. And oh, I just found out, you can even do

$ rm evM-/

(M-/ is by default bound to complete-filename. M-x BTW can be entered as ESC
x, too.)

Greetings,
 Mike


--

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detailatid=413095aid=311399group_id=100114

___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel

[Bash-completion-devel] [bash-completion-Bugs][313199] Completion for the `cd` command does not expand variables.

2012-01-17 Thread bash-completion-bugs 
Bugs item #313199, was changed at 2011-07-01 02:52 by Igor Murzov
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detailatid=413095aid=313199group_id=100114

Status: Closed
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: Completion for the `cd` command does not expand variables. 
Distribution: --Distribution-Agnostic--
Originally reported in: None
Milestone: None
Status: Fix Committed
Original bug number: 


Initial Comment:
Anonymous message posted by deadhead.russ...@gmail.com

Currently, bash_completion will auto complete variables for the `cd` command.  
However, these variables are not expanded making auto-completion not work for 
the remainder of the command.

Example:
Lets say I have a variable, `$variable` which is `/path/to` and I have the 
folder structure, `/path/to/directory/`.

cd $variable/directTAB

currently does nothing.  I expect it to expand the variable and complete it to:

cd /path/to/directory/

I have created a patch where variables are still auto completed.  However, if 
only one match is returned, the matched variable is expanded and the completion 
continues.

--

Comment By: Igor Murzov (garik-guest)
Date: 2012-01-18 04:05

Message:
No response from the user for two months, closing this bug.

--

Comment By: Igor Murzov (garik-guest)
Date: 2011-11-16 03:35

Message:
Should be fixed in commits:
http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=commit;h=ff8e52c9605fa0a40d642d1ddb57ada11213ac3c
http://anonscm.debian.org/gitweb/?p=bash-completion/bash-completion.git;a=commit;h=88b897e2241a728ca9d37fdcfa005930f8c59870


--

Comment By: Andrew Russell (deadhead-guest)
Date: 2011-07-02 03:44

Message:
I have modified the patch slightly such that auto-completing of variables that 
returns no matches does not auto-complete to the empty string.

This changes the following line:

+if [[ ${#variables[1]} -ne 0 ]]; then

To this new line:

+if [[ ${#variables[1]} -ne 0 ]] || [[ ${#variables[@]} -eq 0 ]]; 
then

--

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detailatid=413095aid=313199group_id=100114

___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel

[Bash-completion-devel] [bash-completion-Bugs][311400] DBTS 320390: Does not tab complete a file created after tab is pressed once

2012-01-17 Thread bash-completion-bugs 
Bugs item #311400, was changed at 2009-01-30 12:06 by Igor Murzov
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detailatid=413095aid=311400group_id=100114

Status: Open
Priority: 2
Submitted By: David Paleino (hanska-guest)
Assigned to: Nobody (None)
Summary: DBTS 320390: Does not tab complete a file created after tab is pressed 
once  
Distribution: None
Originally reported in: Debian BTS
Milestone: None
Status: None
Original bug number: 320390


Initial Comment:
From: Matt Kraai kr...@ftbfs.org
To: Debian Bug Tracking System sub...@bugs.debian.org
Subject: bash: Does not tab complete a file created after tab is pressed once
Date: Thu, 28 Jul 2005 15:30:15 -0700

Package: bash
Version: 3.0-15
Severity: minor

If I try to complete a file name before the file is created, once the
file is created, trying to complete the file name again displays the
name of the file instead of completing it:

 tty1: $ cat fTAB
 tty2: $ touch foo
 tty1: TAB
   foo
   $ cat f

It would be better if it completed the file name in this case.


--

Comment By: Igor Murzov (garik-guest)
Date: 2012-01-18 04:18

Message:
This doesn't work without bash-completion either. I assume this is not a 
bash-completion issue.

--

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detailatid=413095aid=311400group_id=100114

___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/bash-completion-devel