Hi, I forgot to append to the existing [EMAIL PROTECTED] array at bug 2 (line
9572). Attached is an improved diff.
=== modified file 'bash_completion'
--- bash_completion 2008-10-10 19:01:59 +
+++ bash_completion 2008-10-20 16:03:48 +
@@ -270,15 +270,23 @@
_expand ||
; #.
Regards,
Freddy Vulto
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
=== modified file 'bash_completion
-Ispacetab' a slash is added to directory names, whereas with
`perl -Itab' no slash is added
- with `perl -Itab' an additional space is added after each directory name
completion, making it difficult to assemble a path using completion
Attached diff addresses these problems.
Regards,
Freddy
Fixes:
- allows `configfile' to contain spaces:
- with `ssh -Ftab' and `scp -Ftab' you received an error message of
_known_hosts: bash: option requires an argument -- F
=== modified file 'contrib/ssh'
--- contrib/ssh 2008-11-01 11:25:38 +
+++ contrib/ssh 2008-11-05 20:48:19 +
@@ -31,17
Package: bash-completion
Version: 20080705
Severity: normal
If UserKnownHostFile or GlobalKnownHostsFile in ssh config file contains
multiple subsequent spaces, e.g. 'spaced hosts' (two spaces), _known_hosts
fails. Solution is to quote the sed output. See attached diff.
Regards,
Freddy
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(!)
Freddy Vulto
http://fvue.nl/wiki/Bash_completion_library
___
Bash-completion-devel
Package: bash-completion
Version: HEAD
Severity: minor
Completion for `cpio' is defined twice: first as `complete -F _longopt cpio'
and then it is overridden with `complete -F _cpio cpio'. I think the first
definition can be removed:
--- bash_completion.orig2009-01-24
---
Regards, Freddy Vulto
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
David Paleino d.paleino at gmail.com writes:
On Fri, 13 Feb 2009 00:11:41 +0200, Ville Skyttä wrote:
On Wednesday 04 February 2009, David Paleino wrote:
On Wed, 04 Feb 2009 21:59:25 +0100, Guillaume Rousse wrote:
I'd insert the following items between 1 and 2, or between 2 and 3:
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
Freddy Vulto fvulto at gmail.com writes:
Debian is giving me whole other problems though:
$ sudo rpm -q TABrpm: To install rpm packages on Debian systems, use
...
bash: bad substitution: no closing `)' in $(
compgen -d -- $(quote_readline $cur) | {
while
' completion as separate files, the `tightvnc' package
could install a file in $BASH_COMPLETION_DIR containing:
. /etc/bash_completion/contrib/tightvncviewer
complete -F _tightvncviewer vncviewer
Regards,
Freddy Vulto
http://fvue.nl
___
Bash
-level solution indeed.
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
shouldn't want this.
- doubts about completion of main argument, ideas :
f -- tp://
h -- ttp
http -- s:// | ://
w | http://w; | https://w; -- www.
Seems useful to me.
Greetings,
Freddy Vulto
http://fvue.nl
---8-
--- wget.sh.orig2009-03
:// https://),...)
--- h) COMPREPLY=( $( compgen -o nospace -W 'http' -- $cur ) );return 0;;...
[/parenthesis]
Or use bash parameter expansion (see also diff):
COMPREPLY=( $( compgen -W http{,s}://{,www} ftp://; -- $cur ) )
Regards,
Freddy Vulto
http://fvue.nl
---8
On Tue, Apr 14, 2009 at 8:50 PM, Ville Skyttä ville.sky...@iki.fi wrote:
Yeah... why not :). Anyone want to write a style guide? Here's a start for a
table of contents, in no particular order:
I'm in the process of writing documentation for the test suite and I'd
like to propose using
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,
Actually `main.xml' is generated: maybe we'd better put in the git
ignore list or specify a tmp directory. `main.txt' is the main file
to edit. The `a2x' command
On Fri, Apr 17, 2009 at 9:52 PM, Ville Skyttä ville.sky...@iki.fi wrote:
This is my first experience with asciidoc (tried 8.4.3), and I must say I'm
not too impressed. Does this mean one needs to know the DocBook DTD and be
able to write the docs in a asciidoc/plaintext format that kind of
).
This can be done with:
$ asciidoc -d book main.txt
Or just generating a particular section, e.g.:
$ asciidoc -d book styleguide.txt
Hope this helps in gaining confidence using AsiiDoc.
Greetings,
Freddy Vulto
___
Bash-completion-devel
Guillaume, about commit: d5fd1c34120c6bae2cf459e386aa08c6bc7ad223:
split split _known_hosts into _known_hosts and _known_hosts_real,
instead of using an option to set current word
I'm having troubles with _known_hosts_real. I already added:
[ $ocur ] cur=$ocur || unset -v cur
at the end,
On Thu, Jun 11, 2009 at 10:05 PM, Guillaume
Rousseguillaume.rou...@inria.fr wrote:
David Paleino a écrit :
Agreed, go change the wiki now! ;)
Done, according to various replies.
I'll keep on working on the test suite in the mean time, supposing the
`test' `doc' directories are not standing
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?
On Thu, Jun 18, 2009 at 10:34 AM, Guillaume
Rousseguillaume.rou...@inria.fr wrote:
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
-
-newline ( \t\n) to expand
hostnames which are separated by whitespace.
Thanks for reporting,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo
.
Then we could have something as:
case f)
_compfset filedir $cur
The `_compfadd', `_compfset' and `_compgen_...' functions can be
adorned with additional options for prefixes and suffixes, as bash's
`compgen': [-P prefix] [-S suffix].
What do you think?
Regards,
Freddy Vulto
http
I just noticed `ssh -F TAB' doesn't escape spaces in filenames.
Further investigation showes that _filedir only works if `-o
filenames' is in effect:
$ touch 'a b'
$ _foo() { cur=$(_get_cword); _filedir; }
$ complete -F _foo foo
$ foo aTAB
$ foo a b # Incorrect, space isn't
filenames' is in effect - changing
it's behaviour on the fly.
*1)
http://gnu.april.org/software/bash/manual/html_node/Programmable-Completion-Builtins.html
Greetings, Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel
UserKnownHostsFile /dev/null
UserKnownHostsFile /dev/null
EOF
$ ssh -F/tmp/config TAB
$ ssh -F/tmp/config bash: /dev/null: Permission denied
...
After the patch, completion should succeed without any error Permission
denied:
$ ssh -F/tmp/config TAB
...
Regards,
Freddy
))}
word_start=`expr $tmp : '.*['${WORDBREAKS}']'`
done
cur=${cur:$word_start}
echo $cur
}
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
instead of album first
(3) album s doesn't complete
Maybe an experimental _get_cword was checked-in the month after
#474094 was closed (2008-05-11)?
Regards,
Freddy Vulto
http://www.fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel
# of expected failures 2
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
I'm looking further into _get_cword, but COMP_CWORDS appears to behave
differently depending on the bash-version. Can other people confirm
this? Try this script:
---8--
_cword() {
echo
echo COMP_CWORD: $COMP_CWORD
echo COMP_CWORDS:
for
no problems on bash-3
bash-4...
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Commit f733e71e should fix things:
_get_cword is restored with the version from commit f6497298 as
__get_cword3() for bash3.
bash-4 now uses __get_cword4() which should solve scp's remote path
completion on bash-4.
Freddy
___
Bash-completion-devel
this difference.
Greetings,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
of it, but completing one-letter options makes little
sense indeed.
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
' prefixes.
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
tags 550634 confirmed fixed-upstream
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
On 11:31, Ville Skyttä wrote:
On Thursday 05 November 2009, Ville Skyttä wrote:
I'd like to propose two coding style guidelines:
No comments? Silence means acceptance?
+1 Another +1 to add the rationale to the documentation as well.
___
and see if libreadline5 can
be patched or do a bugreport.
But at least cron is now working for me again; I'll have a look at the other
actual test suite failures.
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash
differently in different situations, would be a better choice.
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion
On 091121 10:18, Freddy Vulto wrote:
However, next issue is that the `finger' test is using the first host which
now
happenes to be `::1' and is causing troubles.
...
But other tests (e.g. ssh) are now failing as well, so we'd better fix this
for
real? Assuming this should happen
}; # __space_suffix_completions()
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
should set
this.
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
On 091210 15:55, Todd Zullinger wrote:
Freddy Vulto wrote:
On 091209 22:25, Guillaume Rousse wrote:
Why doesn't remove the colon from COMP_WORDBREAKS works with bash
3?
COMP_WORDBREAKS is a bash-4 variable, see:
http://www.gnu.org/software/bash/manual/html_node/Bash
/ # For reference, works on both bash-3 bash-4
c
$ compgen -f a\\\'b/ # Workaround for bash-4
a\'b/c
$ compgen -f a\\\'b/ # Workaround for bash-3
a\'b/c
---8
Regards,
Freddy Vulto
http://fvue.nl
,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
On 100109 13:21, Ville Skyttä wrote:
Expect's default buffer size is too small - 2000 bytes according to the man
page here - for cases where we have a lot of completions. In addition to
rpm,
there are at least pkg_info, portupgrade, portinstall, and probably quite a
few other tests that
On 100103 12:43, Guillaume Rousse wrote:
Shouldn't we try to have variable and function names more consistent ?
Aka rename _get_cword and _get_pword to _get_cur and _get_prev, or
rename cur and prev to cword and pword ?
Maybe we can put this to the roadmap and join this with the effort of
On 100114 20:56, Ville Skyttä wrote:
On Sunday 10 January 2010, Freddy Vulto wrote:
On 100103 12:43, Guillaume Rousse wrote:
Shouldn't we try to have variable and function names more consistent ?
Aka rename _get_cword and _get_pword to _get_cur and _get_prev, or
rename cur and prev
append expected $item
if {[llength $items] 1} {append expected {\s+}};
+# For chunks 1, allow head whitespace
+if {$i $size} {set expected \\s+$expected}
}; # for
if {[llength $items] == 1} {
expect {
Regards,
Freddy Vulto
On 100117 15:40, Ville Skyttä wrote:
Oh, crap. They ship that as the system default awk?
I'm afraid so. I've Ubuntu-9.04 (Jaunty Jackalope) and Debian-5.0.3 (Lenny)
running, and they both report:
$ awk -W version
mawk 1.3.3 Nov 1996, Copyright (C) Michael D. Brennan
FWIW, from
is the lowest version of bash against which I run
nightly tests, so if we decide on a lower version, I could compile this
and run tests against this as well, but as said: I'd rather move
forward and develop towards bash-4 then below bash-3.2(.39).
Regards,
Freddy Vulto
http://fvue.nl
]} {
source lib/completions/perldoc.exp
}; # if
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
On 10:38, Guillaume Rousse wrote:
Le 20/01/2010 22:27, Freddy Vulto a écrit :
What are your ideas on creating a constant test environment? Would chroot be
useful?
It seems a bit oversized, and requires root privileges morevoer. I was
more thinking about abusing environment variables
On 09:48, Guillaume Rousse wrote:
Le 03/02/2010 19:00, David Paleino a écrit :
Do we have consensus for 79?
OK for me.
Ok for me too.
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
On 03:05, Crestez Dan Leonard wrote:
http://wiki.debian.org/Teams/BashCompletion/Proposals/Roadmap mentions
something about merging bash-completion-lib's test suite and it's not
marked at done. Mangling library.exp with sed would probably not help.
Merging is done actually: I updated the wiki.
On 100204 08:41, Crestez Dan Leonard wrote:
What about some guidelines for TCL test code? I only found one style
guide floating around: http://wiki.tcl.tk/708 .
Good to have one. I added a reference to this Tcl Style Guide to the
documentation.
___
On 100131 22:29, Guillaume Rousse wrote:
Le 04/01/2010 20:49, Freddy Vulto a écrit :
On 100103 13:23, Guillaume Rousse wrote:
Also, why do we need to move actual completion test to
lib/completion/ssh.exp, instead of leaving it in completion/ssh.exp ?
I've had a quick look, it doesn't seems
On 100205 11:43, Freddy Vulto wrote:
On 100204 08:41, Crestez Dan Leonard wrote:
There are actually only two things that bug me:
1) Ending blocks with }; # if
2) ...
Just to be sure, does that mean we're also not commenting
end-of-functions anymore, like:
proc assert_complete
/*.
By the way, skeleton test files for a command can be generated easily by
executing:
$ ./generate command
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http
Ville Skyttä ville.skytta at iki.fi writes:
On Friday 05 February 2010, Freddy Vulto wrote:
Just to be sure, does that mean we're also not commenting
end-of-functions anymore, like:
proc assert_complete {} {
}; # assert_complete()
I wouldn't mind dropping them
On 100116 11:38, Ville Skyttä wrote:
On Friday 15 January 2010, Freddy Vulto wrote:
Maybe we'd also better merge _get_cword and _get_pword together to a new:
_get_cwords_by_ref 'nonwordbreakchars' cur [prev [prevprev] ...]
with `prev', `prevprev', etc. being optional arguments
too complicated let alone possible.
But for now, what are the opinions about a _get_comp_words_by_ref [OPTIONS]
[VARNAMES] as proposed above?
Greetings,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel
On 100211 09:11, Ville Skyttä wrote:
On Wednesday 10 February 2010, Freddy Vulto wrote:
On 100210 18:16, Ville Skyttä wrote:
Maybe this is what you meant above put in other words, but removing the
-re {a\\\'b/c} { block from compgen.exp or hacking the regexp so that
it does not match
On 100211 23:44, Ville Skyttä wrote:
No objections, go ahead. I'm not worried at all about adding to the time
taken by the tests if it makes them more reliable.
I think we need to find a mean/middle. I'd like to run the tests as
fast as possible when running the tests manually during
via the bash-completion-devel
mailing list as a reply to an issue update?
David, do you know if making attachments can be allowed to Alioth bug
commenters?
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel
On 100217 19:29, Crestez Dan Leonard wrote:
DejaGnu claims to have a powerful configuration system and it's been
used in very complex situations. Could anyone point me to a
straight-forward way to add an option like this?
Maybe you can pass the BASH_XTRACEFD via the --tool_opts option of
On 100220 23:08, Crestez Dan Leonard wrote:
Anyway; here's what I came up with. I'll commit this later unless there
are any objections (like breaking crontabs).
+1
(I still need to install bash-4.1, but the more reason now)
___
Bash-completion-devel
On 100221 12:42, Ville Skyttä wrote:
On Sunday 21 February 2010, Crestez Dan Leonard wrote:
I pushed this is in the expect-fixes branch in git. It would be great if
you could confirm my findings; I don't want to cause regressions.
On bash-4.0 and 4.1 it runs ok, the speed improvement is
On 100223 19:28, Ville Skyttä wrote:
Confirmed. Ditto with bash 3.2.25.
I notice the difference when just typing a ^C. On bash = 4 it is echoed
as ^C, but on bash-3 it is echoed as a newline. I think I'll ask the
bug-bash mailing list. If we could just make bash-3 echo the ^C...
This is the thread:
http://www.mail-archive.com/bug-b...@gnu.org/msg07023.html
Looks like we can/should use this for bash-4:
echo 'set echo-control-characters on' ~/.inputrc
bind 'set echo-control-characters on'
but need another solution for bash-3. I did a short try with the
# of expected failures 2
# of unsupported tests 191
..., bash-4.0.28(1)-release
real1m15.654s
user0m9.761s
sys 0m12.065s
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel
completions) and therefore I'll undo your commit in commit caaf588.
Or do you have a completion example where things go wrong?
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
On 100312 14:19, David Paleino wrote:
I'll report as soon as I see that happening again.
...
On a side note: maybe it's better if I avoid committing anything, for
...
No offense taken/intended. Don't hesitate to commit as far as I'm
concerned (just don't let bash-completion endanger your exams
On 100210 21:48, Freddy Vulto wrote:
Maybe we can make the varnames non-optional, and also provide shortcuts by
using the arguments, indicating which fixed varnames to return:
Done so in commit bdca37a in branch `use-_get_comp_words_by_ref':
Improve _get_comp_words_by_ref to return `words
' is hard to catch...
Greetings,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
of \005 (^E) and also another regression I
noticed, regarding this test which used to FAIL but is now PASSing because we
removed the `$' (match on end) somewhere (I think in match_items):
expected: foo bar
real: foo bar cee
Greetings,
Freddy Vulto
http://fvue.nl
.
Greetings,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
. Can you confirm this works for you as well?
Greetings,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
On 100412 20:40, Ville Skyttä wrote:
I don't remember seeing any objections, so done in git now.
It's working great, except for 3 failing completions on my Debian test
machine: grub, screen and xhost.
Problem with grub is that on my Debian it's in /usr/sbin/grub, so when
the test-user is
,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
Merged branch 'use-_get_comp_words_by_ref' to 'master'.
It's not showing up in the 'Bash-completion-commits' because the message
is too big:
---Forwarded mail---
Date: Thu, 10 Jun 2010 21:53:41 +
From:
On 12:13, David Paleino wrote:
Freddy, do you want me to make it into 1.2 as well?
If possible, yes? The work is done, so I think it's good to get it out.
The new `_get_comp_words_by_ref' definitely requires bash = 3.1, but as
I understand the requirement of bash = 3.2.0 is already going to be
, but it ended up
in a local mail queue :-( Here it is finally:
---8---
Date: Wed, 9 Jun 2010 22:32:27 +0200
From: Freddy Vulto fvu...@gmail.com
To: bash-completion-devel@lists.alioth.debian.org
I've been trying to find the perfect
[tab]
completion again.
Greetings,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/bash-completion-devel
On 100511 00:54, Ville Skyttä wrote:
Maybe we should start thinking about
adding a begin and end hook to every completion for things like this;
put it at the end of the roadmap?
No objections here.
Added objective for version 3.0 to the roadmap:
Provide begin and end hook to every
On 100425 13:18, Ville Skyttä wrote:
Does bash officially reserve any variable/function prefix to itself?
At least BASH_* and COMP_* are used in it
I've put the question on the bug-bash mailing list, see:
http://www.mail-archive.com/bug-b...@gnu.org/msg07539.html
If we're going to use
My commit message to commit-list is being held because of size limit.
This is the commit:
(testsuite) Drop ending block comments
Instead of writing `}; # if', write just `}' as was discussed here:
: bashcomp_DATA: command not found
bash: EXTRA_DIST: command not found
bash: CLEANFILES: command not found
Can you have a look?
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
http
) - match one or more occurrences of patterns
@(pattern-list) - match exactly one of the given patterns
!(pattern-list) - match anything except one of the given patterns
Greetings,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
On 100820 00:46, Ildar Mulyukov wrote:
Please apply the patch to GIT HEAD.
Oops. Doing a `git push' right now...
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
on the roadmap, ok
team?
I'm putting this last as an objective for version 3.0. See:
http://wiki.debian.org/Teams/BashCompletion/Proposals/Roadmap
Regards,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel
it mandatory for BASH_COMPLETION_DIR to have a
(symlinked) `helpers' subdir? More enforcements are coming if we're
going to merge bash-completion-lib...
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel
a `make', and I think it
would be better if we can defer `make' substitutions to the install phase so
that the bash_completion source stays simpler.
Greetings,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel mailing list
Bash-completion-devel
On 100914 21:15, Ville Skyttä wrote:
The attached patch provides some automatic case insensitivity to _filedir and
_filedir_xspec by automatically matching all-uppercase versions of the passed
patterns as well as the original ones. The idea is that if this goes in, all
glob arguments to
]} {
fail ERROR Unexpected output from bash command \$title\
}
send_user ERROR Unexpected output from bash command \$title\:\n$results
I'll add these comments (commit ba41910).
Greetings,
Freddy Vulto
http://fvue.nl
___
Bash-completion-devel
Ville Skyttä ville.skytta at iki.fi writes:
The notification mail for a change I just committed is being held for
moderator approval for the commits list due to its size, so here's a separate
heads up about it:
http://git.debian.org/?p=bash-completion/bash-
On 101103 21:23, Ville Skyttä wrote:
On my system ls.exp ends up testing ls ~avahi-autoipd and avahi-autoipd's
home dir does not exist, perhaps that's why it passed. Maybe the test case
should be modified so that it checks the existence of the chosen user's home
dir and if it does exist,
1 - 100 of 108 matches
Mail list logo
