On Tue, 9 Jan 2007, Willie Wong wrote:
Hum non reproducible? If it never occurs again, I suggest you not
worry about it. If it occurs randomly... hardware problem?
The box is not new, but I have no reason to suppose it's starting to
fail. At least, ide-smart keeps producing happy
On Monday 08 January 2007 00:25, Willie Wong wrote:
On Sun, Jan 07, 2007 at 10:17:59PM +, Penguin Lover Jorge Almeida
squawked:
Not really all kind of completion, but I noticed that it froze on
trivial completions (the kind that should work even without
bash-completion).
Hold on, so
On 1/9/07, Mick [EMAIL PROTECTED] wrote:
On Monday 08 January 2007 00:25, Willie Wong wrote:
On Sun, Jan 07, 2007 at 10:17:59PM +, Penguin Lover Jorge Almeida
squawked:
Not really all kind of completion, but I noticed that it froze on
trivial completions (the kind that should work even
On Sun, 7 Jan 2007, Willie Wong wrote:
how about if you do
compgen -F _longopt
It should print out an unsorted list of all the files and subdirs of
the given dir. Does it freeze up?
It doesn't freeze, and it displays what you said. However, the first two
output lines are:
ash: compgen:
On Wed, 10 Jan 2007, Kent Fredric wrote:
Interesting to note, with Bash-3.2 2006-03-01 Bash-Completion,
you'll find if you check your latest /etc/skel/.bashrc which is
provided to new users now completely lacks the bash completion line,
Yes, the same goes for the stable version.
and upon
On 1/10/07, Jorge Almeida [EMAIL PROTECTED] wrote:
On Wed, 10 Jan 2007, Kent Fredric wrote:
Interesting to note, with Bash-3.2 2006-03-01 Bash-Completion,
you'll find if you check your latest /etc/skel/.bashrc which is
provided to new users now completely lacks the bash completion line,
On Tue, Jan 09, 2007 at 08:37:01PM +, Penguin Lover Jorge Almeida squawked:
On Sun, 7 Jan 2007, Willie Wong wrote:
It doesn't freeze, and it displays what you said. However, the first two
output lines are:
ash: compgen: warning: -F option may not work as you expect
bash: COMP_WORDS: bad
On Sun, Jan 07, 2007 at 12:19:58AM +, Penguin Lover Mike Williams squawked:
On Sunday 07 January 2007 00:03, Jorge Almeida wrote:
Always using that much resources? That doesn't sound right. What
completions were you trying when it freezes up?
Something trivial: less README (it froze
On Sun, Jan 07, 2007 at 12:25:49AM +, Penguin Lover Jorge Almeida squawked:
Already did it (commented out the line in ~/.bashrc and sourced this
file...) It doesn't freeze now, of course.
Which version of bash completion? And which version of bash?
(Just want to check if you are
On Sun, 7 Jan 2007, Willie Wong wrote:
On Sun, Jan 07, 2007 at 12:25:49AM +, Penguin Lover Jorge Almeida squawked:
Already did it (commented out the line in ~/.bashrc and sourced this
file...) It doesn't freeze now, of course.
Which version of bash completion? And which version of
On Sun, Jan 07, 2007 at 06:10:55PM +, Penguin Lover Jorge Almeida squawked:
Which version of bash completion? And which version of bash?
app-shells/bash-completion-20050121-r10
app-shells/bash-3.1_p17
Okay, so you are on stable I see.
$ complete -p less
complete -o filenames -F
On Sun, 7 Jan 2007, Willie Wong wrote:
On Sun, Jan 07, 2007 at 06:10:55PM +, Penguin Lover Jorge Almeida squawked:
how about if you do
compgen -F _longopt
It should print out an unsorted list of all the files and subdirs of
the given dir. Does it freeze up?
If it doesn't, we can almost
On Sun, Jan 07, 2007 at 10:17:59PM +, Penguin Lover Jorge Almeida squawked:
Not really all kind of completion, but I noticed that it froze on
trivial completions (the kind that should work even without
bash-completion).
Hold on, so the command completions, like say tar tabtab giving
you A
I gave bash_completion a try, and it seemed a Good Thing. Problem is it
was behaving like a pig, consuming all cpu ressources (99%) and freezing
the computer (temporarily). This has to be a misconfiguration issue.
I have both /etc/bash-completion and /etc/conf.d/bash_completion. Is
this normal?
On Sat, Jan 06, 2007 at 10:44:19PM +, Penguin Lover Jorge Almeida squawked:
I gave bash_completion a try, and it seemed a Good Thing. Problem is it
was behaving like a pig, consuming all cpu ressources (99%) and freezing
the computer (temporarily). This has to be a misconfiguration issue.
On Sat, 6 Jan 2007, Willie Wong wrote:
On Sat, Jan 06, 2007 at 10:44:19PM +, Penguin Lover Jorge Almeida squawked:
Any suggestion?
Always using that much resources? That doesn't sound right. What
completions were you trying when it freezes up?
Something trivial: less README (it froze at
On Sunday 07 January 2007 00:03, Jorge Almeida wrote:
Always using that much resources? That doesn't sound right. What
completions were you trying when it freezes up?
Something trivial: less README (it froze at RE)
bash itself autocompletes filenames by default.
Try turning off
On Sun, 7 Jan 2007, Mike Williams wrote:
bash itself autocompletes filenames by default.
I know, but I find bash_completion usefull for other types of completion
(e.g tar xzvf ..., it completes with tarballs only).
Try turning off bash-completion and try that again, on the exact same file.
18 matches
Mail list logo
