Le 03/12/2014 01:16, Dean Sniegowski a écrit :
I've noticed my bash autocomplete will frequently hang.
System info:
I'm running Ubuntu 14.04.1
Bash Autocomplete 2.1-4
Authentication using sssd configured for kerberos and ldap
Suspected Cause:
in _quote_readline_by_ref() has a line elif [[
Le 27/03/2013 20:28, Ville Skyttä a écrit :
Hello,
WDYT, would it be time to release 2.1? I think enough useful things have
been added since 2.0, and there's nothing intrusive and nothing larger
in progress AFAIK so now could be a good time to do it.
Agreed.
--
BOFH excuse #155:
Dumb terminal
Le 14/03/2012 20:21, Ville Skyttä a écrit :
On 2012-03-14 20:51, Guillaume Rousse wrote:
I need to force rpm completion file loading, from another completion
function (urpme), as it relies on one of the function defined there
(_rpm_installed_packages). How can I achieve that ?
Prepending
Le 07/11/2011 20:27, Ville Skyttä a écrit :
Ah, true for chkconfig, but for service that seems to be a Mandriva
specific thing/patch. It doesn't do xinetd stuff on Fedora, Debian,
OpenSUSE or CentOS.
I'd like to get those things out of the way for non-Mandriva setups for
service -- is checking
Le 07/11/2011 17:41, Ville Skyttä a écrit :
On 11/07/2011 05:12 PM, Igor Murzov wrote:
I pushed new variant of the fix to the service branch. Can you look into it?
I didn't look into the code that closely, but it works as expected in
all test cases I threw at it, cool.
The branch seems to be
Le 04/07/2011 23:18, Jonathan Nieder a écrit :
Hi,
Tim Connors wrote:
By placing a script in /etc/profile.d/, setting up of bash-completion
becomes completely non-optional. Previously, it was up to the user to
source /etc/bash_completion, but now it is not.
Yep.
Even worse, it's
Le 03/05/2011 21:44, David Paleino a écrit :
And one important thing we should be planning for is considering what is
the bash-completion API, i.e. what external completion authors can use
if they like and we'll try to keep that stuff stable, and what are
private things not intended to be used
Le 21/04/2011 11:08, Uwe Kleine-König a écrit :
With the current bash completion
sh reftab
doesn't complete ref to refresh though the match is unique.
For now I'm adding
complete -r sh
in my .bashrc which makes the completion work for me again.
Note you can always force
Le 08/04/2011 10:02, David Paleino a écrit :
So, for .deb-based systems, I believe it's ok. I'm missing info for the whole
RPM-based world though. :)
When Debian stable has version X, it means everyone else aleady uses X +1 :)
More seriously, I guess the change only applies to the main
Le 03/04/2011 14:33, David Paleino a écrit :
It's a Celeron 1,73GHz, bash-completion from git, 242 files in
bash_completion.d, Debian sid.
I tried with the slowest box I have easily access to (which has
bash-completion 1.2 with 52 files in /etc/bash_completion.d,
The issue seems clearly
Le 07/02/2011 20:01, Ville Skyttä a écrit :
The following commit has been merged in the master branch:
commit d066ace4cbca7f5da611f0fee2497e24e9d84f67
Author: Ville Skyttä ville.sky...@iki.fi
Date: Mon Feb 7 20:59:01 2011 +0200
Do file completion after gendiff output redirection.
Le 07/11/2010 10:46, Ville Skyttä a écrit :
On Saturday 06 November 2010, Guillaume Rousse wrote:
Le 26/10/2010 20:16, Ville Skyttä a écrit :
On Tuesday 26 October 2010, Ville Skyttä wrote:
On Tuesday 26 October 2010, Guillaume Rousse wrote:
I'm still interested in merging remaining similar
Le 07/11/2010 10:03, Ville Skyttä a écrit :
On Sunday 07 November 2010, Guillaume Rousse wrote:
Le 31/10/2010 23:59, Freddy Vulto a écrit :
The remaining error reported by the test suite however, was that perldoc
option-completion is now missing; it's not in the pure perl perldoc
completion
Le 26/10/2010 20:16, Ville Skyttä a écrit :
On Tuesday 26 October 2010, Ville Skyttä wrote:
On Tuesday 26 October 2010, Guillaume Rousse wrote:
I'm still interested in merging remaining similar patches (for rpm
database completion,
I don't personally find rpmdb completion too slow to warrant
Le 25/10/2010 20:50, Ville Skyttä a écrit :
Mandriva has applied a similar patch for some time already, although
their environment variable name was different ($COMP_AVAHI_BROWSE).
I'm still interested in merging remaining similar patches (for rpm
database completion, and scp remote
Le 27/08/2010 21:46, Ville Skyttä a écrit :
On Friday 27 August 2010, Freddy Vulto wrote:
I'm hesitating to add yet another configuration variable, especially
since contrib helpers are so tied together (we would also need a
BASH_COMPLETION_COMPAT_DIR_HELPER, ugh).
BTW if someone cares,
Hello list.
Our current policy is to group completions by upstream package, hence my
last commit merging iconv and getent into a single glibc file.
I've also attempted to do the same for killall completion, currently in
procps file, whereas it is shipped by psmisc package under linux.
However,
Le 14/08/2010 23:08, Freddy Vulto a écrit :
Guillaume,
The addition of `contrib/Makefile.am' in commit c030827f dynamic
creation of perldoc completion, to point to helper script is causing me
errors because bash is sourcing ./contrib/Makefile.am:
bash: static_bashcomp: command not
Le 10/05/2010 00:06, Ville Skyttä a écrit :
Again, one 00: too many at the beginning. Ideas?
Bash is treating ':' as a special character, starting a new completion
each time. See item E13 in http://tiswww.case.edu/php/chet/bash/FAQ
--
BOFH excuse #397:
T-1's congested due to porn traffic to
Le 30/04/2010 08:22, Alun Evans a écrit :
if I do:
cmd -TAB
I'd like to generate:
-f --file -o --output -v --verbose
but if I do:
cmd -f foo -TAB
or:
cmd --file foo -TAB
I'd like to see:
-o --output -v --verbose
I could cook something up, but I'm thinking this is a
Le 10/04/2010 12:30, Freddy Vulto a écrit :
I made a test case for this problem, see commit 3d4941f. I have to
change LC_CTYPE=C to see the problem, probably because my default locale
is en_US? You can run the test case(s) with:
./run ./unit/_filedir.exp
I was able to move the fix
Le 01/04/2010 22:58, Guillaume Rousse a écrit :
With pure ascii, $COMP_POINT = ${#COMP_LINE} = 11, meaning the test is
true, but with non ascii chars, $COMP_POINT = 13 and ${#COMP_LINE} = 12,
meaning the test is false. It seems like an utf8 issue, with bash (or
readline) miscouting string
Le 12/02/2010 09:42, Adrian Bridgett a écrit :
seconded. TBH I'd just like an option to turn off completion against
the network - it's not just the message but the fixe second hang that
really annoys me.
I second this: all slow completions should be configurable through
environement variables,
Le 20/01/2010 22:27, Freddy Vulto a écrit :
On 100116 13:51, Guillaume Rousse wrote:
Avoiding assumptions whenever possible ensure consistent results, that's
my point. The test you describe will fail, without added value to
anyone, when run by a user with a 'locanything' host in its
/etc
Le 16/01/2010 10:39, Crestez Dan Leonard a écrit :
On Sat, 2010-01-09 at 13:02 +0100, Guillaume Rousse wrote:
I guess it's because you have a large rpm db, right ? Should we not try
to provide a constant test environement, instead of relying of tester
one ? It may be difficult in some case
Le 09/01/2010 12:21, Ville Skyttä a écrit :
On Saturday 09 January 2010, Ville Skyttä wrote:
The following commit has been merged in the master branch:
commit 66f5c11ab7894125039fc366c80d651f06587c43
Author: Ville Skyttä ville.sky...@iki.fi
Date: Sat Jan 9 11:44:36 2010 +0200
Le 09/01/2010 19:54, Ville Skyttä a écrit :
On Saturday 09 January 2010, Guillaume Rousse wrote:
Le 09/01/2010 12:21, Ville Skyttä a écrit :
Opinions, should we fiddle with match_max where needed (like
lib/completions/rpm.exp above), or should we just bump it to a large
value (10
Le 03/01/2010 10:14, gibbo...@gmail.com a écrit :
COMPREPLY=()
cur=`_get_cword`
prev=${COMP_WORDS[COMP_CWORD-1]}
there is a new _get_pword.
cur = _get_cword
prev = _get_pword
Shouldn't we try to have variable and function names more consistent ?
Aka rename _get_cword and
Le 21/11/2009 16:15, Guillaume Rousse a écrit :
As reported by a mandriva user:
https://qa.mandriva.com/show_bug.cgi?id=54845
This is actually triggered by the completion code called with
COMP_CWORD=0, meaning prev=${COMP_WORDS[COMP_CWORD-1]} will trigger an
error.
BTW, this is not mandriva
For an unkwnown reason, git keep trying to push changes both in my local
branches 'master' and '1.x', and fails for this last one:
[guilla...@oberkampf bash-completion (master)]$ git push -v
Pushing to
git+ssh://guillomovitch-gu...@git.debian.org/git/bash-completion/bash-completion.git
To
Le 03/01/2010 20:12, Ville Skyttä a écrit :
On Sunday 03 January 2010, Guillaume Rousse wrote:
The following commit has been merged in the master branch:
commit f35923a50515c5bb0f3f843e7d6a99b979698e61
Author: Guillaume Rousse guilla...@oberkampf.msr-inria.inria.fr
Date: Sun Jan 3 18:13:31
Freddy Vulto a écrit :
This make me think a configuration file for the project, with all the
project-specific variables, and additional variables, such as this one,
would be useful.
It's not a bash-completion variable, so I'm not sure if we should set
this.
We could set it to its default
Todd Zullinger a écrit :
Freddy Vulto wrote:
There's a problem when completion words containing colons (:). For example,
when you do this in an empty directory:
$ touch abc:def
$ rm abc:TAB # Becomes: abc:abc\:def (see also *1)
The solution for bash-4 is to remove the colon from
As reported by a mandriva user:
https://qa.mandriva.com/show_bug.cgi?id=54845
--
BOFH excuse #32:
techtonic stress
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
Ville Skyttä a écrit :
The following commit has been merged in the master branch:
commit f194a2d753c520877e0a97d4812ec2f7eeb95889
Author: Ville Skyttä ville.sky...@iki.fi
Date: Thu Oct 22 11:50:20 2009 +0300
bash 3 support removal step 4: drop unneeded version checks.
diff --git
David Paleino a écrit :
Ville Skyttä wrote:
On Saturday 03 October 2009, David Paleino wrote:
I'm going to release it in one week -- i.e. next Saturday. This is not a
strict deadline, we might postpone it further if needed.
Remember to only cherry-pick things you ABSOLUTELY want/need in 1.1
David Paleino a écrit :
4-spaces wins.
Which means following vim/emacs headers, right ?
# -*- mode: shell-script; sh-basic-offset: 4; indent-tabs-mode: nil -*-
# ex: ts=4 sw=4 et filetype=sh
I'm about to reformat all files. If you have pending changes, you'd
better commit them before,
Ville Skyttä a écrit :
On Tuesday 15 September 2009, Guillaume Rousse wrote:
David Paleino a écrit :
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?
According
David Paleino a écrit :
On Sun, 20 Sep 2009 22:06:16 +0200, Guillaume Rousse wrote:
You're mixing two issues here.
The first one is where is the code to be developped and maintained:
either splitted in various upstream projects, or centralized in
bash-completion project.
The second one
Ville Skyttä a écrit :
For the last issue, which is to distribute in a single package, and
activate only when needed, I initially attempted to use triggers too.
However, we now have 175 various completions in contrib directories,
meaning 175 * 2 triggers (installation/uninstallation) to
David Paleino a écrit :
Hello,
I remember we decided to push all completions to respective upstreams, but
didn't decide anything more than that, at the time. -- or it could've been a
joke of my mind :)
On IRC the discussion was raised by the maintainer of the PLD package. He has a
few points,
David Paleino a écrit :
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?
According to the roadmap, there is still the indentation policy issue,
to decide and to
Hello.
I just commited a script, install-completions, loosely based on munin
system. It just sources all available completions from one given
directory, and if relevant, symlink them to another one.
It allows to install the whole bunch of completions in some place (such
as
Ville Skyttä a écrit :
On Monday 14 September 2009, Guillaume Rousse wrote:
The following commit has been merged in the master branch:
commit 5b760a88bbddd2bd3647ebdc1235661a29ca0030
Author: Guillaume Rousse guilla...@oberkampf.msr-inria.inria.fr
Date: Mon Sep 14 21:49:44 2009 +0200
add
Freddy Vulto a écrit :
On Fri, Jul 3, 2009 at 11:15 PM, Guillaume
Rousseguillaume.rou...@inria.fr wrote:
However, using this prefix for distinguishing helper function setting or
adding to COMPREPLY is fine. In this regard, we shoud rename the following
ones:
- _filedir - _add_filedirs
-
Freddy Vulto a écrit :
On Wed, Jun 24, 2009 at 10:29 PM, Guillaume
Rousseguillaume.rou...@inria.fr wrote:
mandatory means 'always present', not 'not empty'. I'd prefer to keep
options for optional argument (using getopt for internal functions is
already awful enough IMHO).
That's exactly the
Freddy Vulto a écrit :
On Thu, Jun 18, 2009 at 10:34 AM, Guillaume
Rousseguillaume.rou...@inria.fr wrote:
_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
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
David Paleino a écrit :
Agreed, go change the wiki now! ;)
Done, according to various replies.
--
BOFH excuse #443:
Zombie processes detected, machine is haunted.
___
Bash-completion-devel mailing list
Bash-completion-devel@lists.alioth.debian.org
Ville Skyttä a écrit :
Let me know if you've tested and had success with some of these and I'll go
ahead and apply to master.
They'll look OK for me. As I also prefer to test them by daily usage,
feel free to commit them.
--
BOFH excuse #215:
High nuclear activity in your area.
Freddy Vulto a écrit :
On Mon, Jun 8, 2009 at 8:01 PM, Ville Skyttäville.sky...@iki.fi wrote:
I have no problems with this plan (although I have a pile of fairly innocent
patches that I'd like to see go in the next release, more on that in a
separate mail). But the test suite sure would be
Guillaume Rousse a écrit :
Hello list.
According to our roadmap,
http://wiki.debian.org/Teams/BashCompletion/Proposals/Roadmap, we still
have to finish splitting completions in individual files, and also to
review existing completions.
We finished 2.b (rewieving), and we almost finished 2
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
While splitting completion, I just found we had two different
completions for nslookup:
- the generic known_hosts one
- a specific _nslookup function (now in bind-utils file)
The second one was apparently preferrable. But its only advantage is to
complete (even if apparently broken) on
Ville Skyttä a écrit :
On Sunday 17 May 2009, Guillaume Rousse wrote:
Hello list.
According to our roadmap,
http://wiki.debian.org/Teams/BashCompletion/Proposals/Roadmap, we still
have to finish splitting completions in individual files, and also to
review existing completions. I did a first
Hello list.
According to our roadmap,
http://wiki.debian.org/Teams/BashCompletion/Proposals/Roadmap, we still
have to finish splitting completions in individual files, and also to
review existing completions. I did a first pass on first task, but as
the second mostly concerns completions I
David Paleino a écrit :
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
Freddy Vulto a écrit :
On Tue, Mar 3, 2009 at 11:49 AM, Guillaume Rousse
guillaume.rou...@inria.fr wrote:
assuming `/usr/bin/vncviewer' is a symlink to `tightvncviewer' on
your machine?
No, it is not, that's what I'm trying to explain :) We only have one
only 'vncviewer' in the distribution
David Paleino a écrit :
On Tue, 24 Feb 2009 21:38:50 + (UTC), Freddy Vulto wrote:
Perhaps Mantis is an option? See: http://www.mantisbt.org/
It would've been if we have a MySQL server available on Alioth, which we don't
have. :/
I don't have experience with the other mentioned
Freddy Vulto a écrit :
On Thu, Feb 26, 2009 at 12:33 PM, David Paleino d.pale...@gmail.com wrote:
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
Freddy Vulto a écrit :
Guillaume, I've reviewed updated the to_review/vncviewer completion
and got carried away with the case-insensitive options... Can you
confirm it's still working all right? If there are no further
objections, I'll move the new code to contrib and will delete the old
Guillaume Rousse a écrit :
if [ $offset -gt 0 ]; then
+ # FAIL: _command_offset is not defined anywhere. Guillame?
_command_offset $offset
else
Guillaume, is this a Mandriva-specific helper?
Yes. More precisely, this is the result of a patch of mine splitting
Freddy Vulto a écrit :
Hello Guillaume,
I can't reproduce your problem, maybe it's distribution specific?
I've tried on Debian 4.0 with latest bash-completion from bzr and
`sudo vim TAB' and `sudo chown TAB' run fine.
Strange. Using trunk directly, without any mandriva-specific patches, it
David Paleino a écrit :
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:
David Paleino a écrit :
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
Yanko Kaneti a écrit :
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..
I confirm the problem.
function for example. And if we go for 4
spaces, rather than changing tab length, I'd rather move to spaces only
rather than tab + spaces:
# ex: ts=8 sw=4 sts=4 et filetype=sh
But I'd like to be first able to merge my own work before...
--
Guillaume Rousse
Service des Moyens Informatiques
INRIA
Guillaume Rousse a écrit :
See for instance various code currently not part of upstream
bash-completion package:
http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/bluez/current/SOURCES/
http://svn.mandriva.com/cgi-bin/viewvc.cgi/packages/cooker/bridge-utils/current/SOURCES/
http
Santiago M. Mola a écrit :
Hi,
Let's review some patches.
El lun, 12-01-2009 a las 23:55 +0100, Guillaume Rousse escribió:
Second, I'd prefer all potentially slow completion (rpm database
querying, scp remote completion) to be easily desactivable. For those
reason, we patch openssh
69 matches
Mail list logo
