On 2010-03-23 at 11:05:44 +, Dmitrijs Ledkovs wrote:
Hardy - Lucid upgrade will not be enabled on day 0. Latest plans I've
read (maybe changed since then) is that LTS upgrade will start with
10.04.1 which will bring us a few bugfixes after the release.
snip
So you should consider Lucid
As soon as more than x people actively seeking help are on a channel (not
sure how many in this case), it becomes hard for new people on the channel
to get attention. The trick would be to get the volunteers onto the right
subchannel so that when someone on #ubuntu points the user to
25.12.2007 um 23:35 schrieb Aaron C. de Bruyn:
Can anyone provide me with some guidance on how to resolve this issue? Am
I overblowing the issue since I am affected?
Just to understand the problem better:
Exposing SATA drives as IDE drives to the OS appears to be a temporary
solution until all
My personal preference would be to move it to shut-down, but an
interruptable check on boot is better than nothing. Just my two cents.
Of course then there's the laptop angle.
My old POS laptop has about 3 minutes of battery life left. One day I either
need a new laptop or to pony up a
Of course then there's the laptop angle.
My old POS laptop has about 3 minutes of battery life left. One day I either
need a new laptop or to pony up a thousand for a shiny new model.
Anyways--I usually hit shutdown, unplug everything and throw it in my bag.
It would definitely run out of
Aaron C. de Bruyn:
It boils down to this: If users aren't running into bugs, why repackage?
Because having “Release Conadidate” on the splash screen and “rc” in the
About box gives users the impression that this is not a trustworthy,
final version of GIMP.
Kinda like how hundreds
And how do you know that no one is having a problem? Oboviusly
*somebody* is or the latest release would not be 4.0.1.
Bug reports.
If someone is having a problem and they file a bug report, it will get dealt
with.
And just becasuse Ubuntu users haven't reported the bugs that the GIMP
devs
Wouldn't logic dictate that if their latest release was for bugfixes,
that they would recommend an update? Or do developers update software
just for the heck of it?
I haven't done an official study or anything, but I'd be willing to bet that a
month after Gutsy is out, about half the packages
It's the wrong way to fix it. You can lose data by clicking enter
while a link is focused too, should we disable the enter key? The
Your example doesn't fit. Navigation is the PRIMARY function of the enter key.
Enter is for submitting URLs in the location bar, for following links, and
I installed Ubuntu just yesterday, and backspace not mapping to 'back
in history' is the main annoying thing I found. It happened once or
twice (in a year) that I went one page back when I wanted to delete
text, because I wasn't focused on the right control. But I'd
definitely choose the
Maybe you mean that you switched from Windows to Linux for.. because
Firefox on Windows has always used BACKSPACE==BACK. Also, I agree that
reversability is very important in GUIs (being smart about confirms and
providing good undo where it makes sense).
Hmm--I never ran into my most
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
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
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
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
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)
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
17 matches
Mail list logo
