On Thursday 11 October 2007 16:51:23 Vincenzo Ciancia wrote:
On 11/10/2007 Aaron C. de Bruyn wrote:
I don't think it's a good argument to say that people need to have
user-friendly hand-holding at the command prompt. If I want to run 'evince
somefile.asp' I should be able to. I don't
Op maandag 15-10-2007 om 17:46 uur [tijdzone +0100], schreef Ian
Jackson:
I too find the programmable completion very annoying.
And I find them very useful, except where they have bugs (e.g. sudo
-e, which should work like 'sudoedit'). IMHO tab-completion should
complete to what's supposed to
I too find the programmable completion very annoying.
And I find them very useful, except where they have bugs (e.g. sudo
-e, which should work like 'sudoedit'). IMHO tab-completion should
complete to what's supposed to be there in most cases, maybe even giving
hints if there is a choice
On Mon, 2007-10-15 at 17:46 +0100, Ian Jackson wrote:
So I submit that programmable completions should be off by default.
As long as it stays on off by default for zsh, where it *always* has
been context-specific.
Scott
--
Scott James Remnant
[EMAIL PROTECTED]
signature.asc
Description:
On Mon, 2007-10-15 at 17:52 +0100, Scott James Remnant wrote:
On Mon, 2007-10-15 at 17:46 +0100, Ian Jackson wrote:
So I submit that programmable completions should be off by default.
As long as it stays on off by default for zsh, where it *always* has
~~~
On 12/10/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Thu, Oct 11, 2007 at 06:43:15PM -0700, Aaron C. de Bruyn wrote:
If I modify them, doesn't that mean they will get overwritten by the
next update to the bash package?
not if you modify them in your own .bashrc
So anyone who disliked anything in the system bashrc 10 years should
have skipped all updates since?
Why do I have to opt out of bug future fixes and improvements just
because somebody else prefers their way of tab-completion?
I have to disagree here.
bash has tons of configuration files:
On Fri, Oct 12, 2007 at 02:15:07PM +0100, Fergal Daly wrote:
On 12/10/2007, Forest Bond [EMAIL PROTECTED] wrote:
Hi,
On Fri, Oct 12, 2007 at 09:07:17AM +0100, Fergal Daly wrote:
On 12/10/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Thu, Oct 11, 2007 at 06:43:15PM -0700, Aaron
On 12/10/2007, Forest Bond [EMAIL PROTECTED] wrote:
Hi,
On Fri, Oct 12, 2007 at 09:07:17AM +0100, Fergal Daly wrote:
On 12/10/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Thu, Oct 11, 2007 at 06:43:15PM -0700, Aaron C. de Bruyn wrote:
If I modify them, doesn't that mean they
On 12/10/2007, Aurélien Naldi [EMAIL PROTECTED] wrote:
So anyone who disliked anything in the system bashrc 10 years should
have skipped all updates since?
Why do I have to opt out of bug future fixes and improvements just
because somebody else prefers their way of tab-completion?
I
Hi,
On Fri, Oct 12, 2007 at 09:07:17AM +0100, Fergal Daly wrote:
On 12/10/2007, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
On Thu, Oct 11, 2007 at 06:43:15PM -0700, Aaron C. de Bruyn wrote:
If I modify them, doesn't that mean they will get overwritten by the
next update to the bash
Op donderdag 11-10-2007 om 10:03 uur [tijdzone +0200], schreef Aurélien
Naldi:
- very smart completion: hostnames after ssh thanks to the content of
your .ssh/knownhosts (which does not work with more recently added
hosts as the hostname is no more written explicitely...)
HashKnownHosts no
I think this sucks. I spend a lot of time at the bash prompt and use
tab-completion constantly. When you are in bash, I would expect you sorta
know what you are doing.
I totally forgot my other example until just a few minutes ago when I went to
modify my apt sources list.
sudo -e
On 10/11/07, Aaron C. de Bruyn [EMAIL PROTECTED] wrote:
Ok--I'm sorry, but none of what you said made any sense to me.
I don't see the point why filenames needs to be tab-completed on default, it
does it when it's necessary.
I'm asking why tab-completion changed from allowing
On 10/11/07, Aaron C. de Bruyn [EMAIL PROTECTED] wrote:
Yes, you hit tab to complete certain commands and filenames. It seems like
Ubuntu is trying to be helpful by showing you only the things it thinks you
need.
bash completion isn't an Ubuntu feature specifically - it's a bash
feature.
Try with the following in your ~/.bashrc:
shopt -u progcomp
That turns off Programmable Completion (see the section in bash man
page for more) and leaves you (well, it leaves me) with the normal
file-based tab-completion.
Actually, I'm a fan of programmable completion, but I don't like
you can of course modify tab-completion by
modifying /etc/bash_completion and the files in /etc/bash_completion.d
that might be what you want to do.
If I modify them, doesn't that mean they will get overwritten by the next
update to the bash package?
there are lots and lots of reasons to
On Thu, Oct 11, 2007 at 08:23:38AM -0700, Aaron C. de Bruyn wrote:
If I modify them, doesn't that mean they will get overwritten by the next
update to the bash package?
No; it is a configuration file, which means dpkg will prompt you whether or
not to replace the file. You can choose not to.
On 11/10/07 23:51, Vincenzo Ciancia wrote:
The shortest path to solve usability of this would be to complete
restricted for the first tab, and all files for the second. When I
have file extension corrected, I love unzip to complete only .zip files.
But this will always be in the way in many
If I modify them, doesn't that mean they will get overwritten by the next
update to the bash package?
not if you modify them in your own .bashrc
Yeah--but system-wide I want it off.
On the hosting server I own, I have 4 other admins that would absolutely hate
this.
sniffing the mime
On Thu, Oct 11, 2007 at 06:43:15PM -0700, Aaron C. de Bruyn wrote:
If I modify them, doesn't that mean they will get overwritten by the next
update to the bash package?
not if you modify them in your own .bashrc
Yeah--but system-wide I want it off.
On the hosting server I own, I
Today a website generated a PDF file for me automatically and firefox popped up
and asked if I wanted to download it. I hit 'OK' and it saved 'genpdf.asp'
into my downloads folder. I was surprised to find bash wouldn't tab-complete
the filename.
Apparently there is new (newer than dapper)
On 10/11/07, Aaron C. de Bruyn [EMAIL PROTECTED] wrote:
Today a website generated a PDF file for me automatically and firefox
popped up and asked if I wanted to download it. I hit 'OK' and it saved '
genpdf.asp' into my downloads folder. I was surprised to find bash
wouldn't tab-complete
Ok--I'm sorry, but none of what you said made any sense to me.
I don't see the point why filenames needs to be tab-completed on default, it
does it when it's necessary.
I'm asking why tab-completion changed from allowing tab-completion of EVERY
file to being restricted.
It sounds like you are
24 matches
Mail list logo
