« first day (1556 days earlier)      last day (3696 days later) » 

13:33
Does anyone have a recommendation for reasonable generic Nvidia video that would owrk with the existing nvidia drivers? My current version of the drivers is 304.117-1, but I could upgrade if necessary.
 
4 hours later…
17:04
@FaheemMitha check your verion's readme file for a list of supported chipsets
 
3 hours later…
19:42
@derobert Chipsets don't specify cards, correct?
I suppose multiple vendors might manufacture cards with the same chipset.
@FaheemMitha With nVidia cards they basically do.
They cards might have more or less RAM, or different fans, or something like that... but the driver doesn't care about that.
(Well, or it does care, but it works with all the variations.)
notepad + hacked :(
@Ramesh ?
@derobert, see this.
ah, a web site defacement
20:04
Any super bash experts around?
Several of us have been banging our heads against this for a bit now and no one seems to have figured it out:
1
Q: Why isn't this linux script from SO working on my computer?

KlikThe script can be found here: http://stackoverflow.com/questions/14750650/how-to-delete-history-of-last-10-commands-in-shell For convenience here it is: for x in `seq $1 $2` do history -d $1 done I put this in my include directory (one which I've added to the PATH) where I run many other sc...

20:30
@derobert Well, my point was more that (I presume) all the card manufacturers are not of equal quality. So the first question is what manufacturer is good. Also, is a graphics card with a fan desirable?
@Seth paging @Gilles and @StéphaneChazelas I guess.
As long as it's no bother. I'm interested in the answer :)
20:53
In
12
A: "E: Sub-process /usr/bin/dpkg returned an error code (1) " What does this mean?

BraiamThat message is generic. It just means that the dpkg instance called by apt/apt-get failed for some motive. It doesn't explain why, how, or give hints how to solve it. As diagnostic message it is not useful. You need to read the lines before the message (sometimes quite an amount of them) to fin...

I don't think "motive" is the right word.
I'd just go with reason.
Looks like this is the problem @FaheemMitha:
3
Q: "history" stops working when run inside bash script

Martin VegterI am writing a simple script to grep my bash history to find a particular string. On the command line, I can do the following, which works fine: history | grep git However, when I create a bash script with the same command as above, suddenly history returns nothing: #!/bin/bash history | grep...

21:27
@Seth ok
21:54
@FaheemMitha AFAIK, neither Gilles nor I (or any sensible person I know, though that may be down to my definition of sensible ;-) use bash as his interactive shell.
3
@StéphaneChazelas wrong link. presumably zsh is sensible, then?
I've thought of using zsh. Maybe some day.
22:31
@StéphaneChazelas I use bash... but that's probably only because I haven't gotten around to trying zsh. And maybe I'm a crazy person, who knows.
Now, now. Let's not bash bash.
3
@FaheemMitha Does bash enjoy a good bashing? And if so, would bash be to to bashful to say?
@derobert Dunno. I think you'll have to ask bash what it enjoys.
anthony@Zia:~$ what do you enjoy?
bash: what: command not found
You have a duplicated 'to'. Which might be Ok, but should also be 'too'.
22:36
... seems it's bashful
@FaheemMitha indeed.
@derobert missing apostrophe.
@FaheemMitha Does bash enjoy a good bashing? And if so, would bash be too bashful to say?
@derobert better
There, grammar patches applied :-)
I keep thinking I should try zsh. Hasn't happened yet, though.
22:38
anthony@Zia:~$ which things bring bash pleasure?
/bin/bash
... well, then!
@derobert that really should produce an error.
@derobert so, by @StéphaneChazelas's defn, neither you nor me are sensible people. Anyone else care to join the club of non-sensible people?
@FaheemMitha Nah, it gave the expected $?=1 exit code.
@derobert shouldn't is say not found or something?
@FaheemMitha Nope, it says that via its exit code, not diagnostics.
command -v works the same way, btw.
@derobert Hmm, is that specific to bash? Or a shell thing?
22:44
@FaheemMitha which is (in)famously not a shell built-in. It's /usr/bin/which
It's also, AFAIK, not part of POSIX/SuS, so there isn't a standard behavior.
command -v is specified, as is its no-output on not found.
@derobert don't follow that.
"as is its no-output on not found"?
I like things to complain loudly when everything is not all right.
@FaheemMitha The behavior of not printing anything if the command isn't found---that behavior is specified by the standard.
I'm the sort of person that turns on all the warning flags in a compiler
"Otherwise, no output shall be written and the exit status shall reflect that the name was not found." under the -v flag
23:02
@derobert I think I disagree with that. And what is the rationale. Let's not display errors for maximum helpfulness?
@FaheemMitha shrug, you'd have to bring that up with the SuS folks. Really, it's a command mostly intended to be used from shell scripts, and changing it now would lead to a lot of pointless diagnostic messages.
E.g., when scripts use command -v to check for which of a series of commands exist.
@derobert Agreed, debating a standard here is fairly pointless.
But it is possible to associate classes of diagnostics with flags. as compilers do. i don't see why shells can't do the same.
Someone on academia.sx just linked to this xkcd which I hadn't seen before. But is really pretty funny.
@FaheemMitha That would be command -V (capital -V instead of lowercase -v)
@FaheemMitha That's what Gentoo does to people!
Parents: talk to your children about Linux.. before somebody else does.
@casey does Gentoo really do that to people?
@derobert don't follow.
@FaheemMitha command -V does, at least in bash, print that diagnostic.
23:12
@derobert oh. let me try
The spec doesn't require that or prohibit that, AFAICT. -V seems to be more for interactive usage.
@derobert usage example, please.
this is actually eye opening:
anthony@Zia:~$ command -V ohnoes
bash: command: ohnoes: not found
@FaheemMitha ^^^
@derobert oh, you literally meant command. i don't know what that is.
So for example:
command -V which things bring bash pleasure?
23:15
anthony@Zia:~$ command -V which things bring bash pleasure?
which is /usr/bin/which
bash: command: things: not found
bash: command: bring: not found
bash is /bin/bash
bash: command: pleasure?: not found
so what does this command thingy do? some bash builtin in guess.
Yes, it's a bash bultin (as command -V command would tell you). help command, man bash, or that SuS link I posted earlier will explain more...
@derobert I see.
You learn something new every day.
23:50
@Seth no need to be an expert, it's a classic newbie mistake: missing .
@Gilles Ah yes, that classic.
Although I fear some of those a C shell.
I don't get:
1984: Event not found.                  # (on some systems)

« first day (1556 days earlier)      last day (3696 days later) »