Well there's no doubt that the Earth experiences periods of warming and cooling, sometimes very quickly, but I think what you meant to say is that the theory of Global Warming predominantly due to the burning of fossil fuels is false, to which I agree.
No need to be sarcastic. I specifically mentioned it doesn't have to be numbers. You obviously missed my point - it should be something unique to the root cause and by implication of the context of this discussion, easily *web-searchable*. Even if it was 'english' (hindu-arabic?) numerals, it's not there for reading, it's there for indexing.
This is why error messages in any language should be accompanied by an error code (usually numerical but it doesn't have to be) that is unique to the root cause of the error. Then you can search on this error code regardless of the language of the message.
I take it you're showing how sometimes backspacing or moving the cursor backwards along a line that exceeds the terminal's width does a strange duplication thing, making it almost impossible to edit? In my own experience, there are two main reasons why this might happen:
1. you changed the *term window size while constructing the command, so use this to enable checks for this condition: shopt -s checkwinsize
2. you have an improperly terminated escape code in your prompt. I had this problem until I started using codes like this: \[\e[0m\] rather than the other style, which I now forget.
I learned a lot with that great machine - only 32kb RAM, most of which was taken up with the current video mode's memory map. I used to tuck little bits of 6502 machine code into unused buffer areas to try and get the most out of it. It also had some of the best games ever:
- Elite
- Citadel
- Repton et al
I got a sideways RAM image (two actually) of a C compiler once, and learned my first few lines of C. You couldn't #include more than 3 files deep due to RAM constraints. I had a fascination with typing in thousands of lines of code from BBC Micro and Acorn User magazines too...
I've spent the last week setting up a Gentoo cluster with distcc and I've noticed a few things:
1. when *recompiling*, the advantage due to ccache far outweighs the performance of distcc on the first compile. If you're testing distcc you need to be aware of this and disable ccache.
2. most large packages either disable distcc (e.g. xfree by limiting make -jX) or compile small sets of files in bursts and spend the majority of time performing non-compilation and linking. Distcc helps with the compilation but because it's only a small part of the total build time, the overall improvement isn't as great as you might have hoped.
3. distccmon-gnome is very cool.
4. using distcc with Gentoo transparently involves modifying your path and this can make non-root compilations troublesome (permissions on distcc lock files). I haven't figured this one out yet other than to specify the full path to the compiler: make CC=/usr/bin/gcc rather than CC=gcc.
5. the returns from adding an extra distcc server to the pool drop considerably after the first few machines. Even on a 1 gigabit LAN the costs of distcc catch up with the benefits after a while. This is more of a concern when compiling lots of small files.
6. it can handle cross-compilation with a bit of configuration.
So although distcc can often reduce build time, it's not quite as effective as you might assume or hope at first.
It's not a requirement, it's a recommendation. Mixing gcc versions will give you unpredictable results, some of which are perfectly acceptable, and some of which are fatal.
Even if the major versions are the same, Gentoo applies patches to gcc 3.3.3 that are not present in Debian's 3.3.4 (the major version is 3.3). For example, Debian's gcc doesn't recognise -fno-stack-protector which Gentoo's does, and distcc fails.
Well, I wasn't completely correct either it seems, according to these. It's all about assuming something is true without validating it:
http://www.wsu.edu:8080/~brians/errors/begs.html http://skepdic.com/begging.html http://alt-usag e-english.org/excerpts/fxbegthe.htm l
Google.com has lots more.
Oh, and just because lots of people do something doesn't make it right. Although I'm constantly surprised how many people subscribe to this world view.
The original post makes use of the phrase "begs the question". This does not mean "to wonder" or "leads me to think" or to "rhetorically enquire" or anything like that. It's plain and simple - it means to take something as given (similar to the concept of conditional probability). For example, you could say something like:
"Begging the question that it's raining tomorrow, would you like to go the cinema?".
In this example, you are asking the person to whom you are speaking to consider the question as if it will be raining tomorrow. You are asking them to ignore the question of whether it will rain, and consider their response assuming it WILL rain. You could ask this too:
"If it rains tomorrow, would you like to go to the cinema?".
You might consider me as a pedant - but you would be wrong (look up pedant). I would argue I am not being pedantic. I am not correcting a trivial mistake or trying to get one-up on the original poster - I am trying to correct an obvious and serious mistake. This is not pedantry, it is sharing knowledge in the hope of improving the use of such language for the benefit of everyone.
Someone's ported Linux to the iRaq?
on
Linux in Iraq
·
· Score: 1
Wow - I knew it would happen sooner or later. Is it pretty stable or does it tend to blow up now and again?
Doesn't work - the problem occurs when loading a savegame, and the values in default.ini are not used in that case. They are supposed to be retrieved from the savegame, but are not and therefore remain at their *coded* defaults of 1.0. Read the threads.
^U kills the entire line (or everything from the current cursor to the end of the line if you prefer and configure it this way) in pico/nano. Emacs too. The bash shell as well. Readline. Probably many others...
"If consumers want a backup of their favourite album, they should buy another copy" (or something very close - it's from memory).
In New Zealand, it's illegal to make any unauthorised copies of copyrighted audio works at all. Nobody gets charged for doing it (not for personal use anyway) and the Govt is considering changing the law to allow 'personal transcoding' but of course the recording industry is getting mighty steamed up about it.
So, here it's illegal to legitimately buy a CD and rip the tracks to mp3 or ogg/vorbis or whatever to play on my iHP-120:( This makes me a criminal, which is stupid - I bought the #^@!ing CDs didn't I?!
A great game to play with other intelligent people. It's not hard to learn, but difficult to master. There's almost no element of luck in the game (there is one non-player source of entropy, but it's not completely random) but the design of the game leads to billions of possible scenarios. An excellently designed and balanced game - highly recommended.
Slashdot Mirror
Well there's no doubt that the Earth experiences periods of warming and cooling, sometimes very quickly, but I think what you meant to say is that the theory of Global Warming predominantly due to the burning of fossil fuels is false, to which I agree.
perl + sox. Oh, *Windows*...
It's ^H (backspace) not ^D (end of transmission) to 'delete' the prior character.
No need to be sarcastic. I specifically mentioned it doesn't have to be numbers. You obviously missed my point - it should be something unique to the root cause and by implication of the context of this discussion, easily *web-searchable*. Even if it was 'english' (hindu-arabic?) numerals, it's not there for reading, it's there for indexing.
This is why error messages in any language should be accompanied by an error code (usually numerical but it doesn't have to be) that is unique to the root cause of the error. Then you can search on this error code regardless of the language of the message.
I take it you're showing how sometimes backspacing or moving the cursor backwards along a line that exceeds the terminal's width does a strange duplication thing, making it almost impossible to edit? In my own experience, there are two main reasons why this might happen:
1. you changed the *term window size while constructing the command, so use this to enable checks for this condition: shopt -s checkwinsize
2. you have an improperly terminated escape code in your prompt. I had this problem until I started using codes like this: \[\e[0m\] rather than the other style, which I now forget.
oops, sorry! :(
mldonkey is good.
My BBC Model B still works :)
I learned a lot with that great machine - only 32kb RAM, most of which was taken up with the current video mode's memory map. I used to tuck little bits of 6502 machine code into unused buffer areas to try and get the most out of it. It also had some of the best games ever:
- Elite
- Citadel
- Repton et al
I got a sideways RAM image (two actually) of a C compiler once, and learned my first few lines of C. You couldn't #include more than 3 files deep due to RAM constraints. I had a fascination with typing in thousands of lines of code from BBC Micro and Acorn User magazines too...
Of course I meant 'minor' not 'major':
major.minor.??? (revision?).
I've spent the last week setting up a Gentoo cluster with distcc and I've noticed a few things:
1. when *recompiling*, the advantage due to ccache far outweighs the performance of distcc on the first compile. If you're testing distcc you need to be aware of this and disable ccache.
2. most large packages either disable distcc (e.g. xfree by limiting make -jX) or compile small sets of files in bursts and spend the majority of time performing non-compilation and linking. Distcc helps with the compilation but because it's only a small part of the total build time, the overall improvement isn't as great as you might have hoped.
3. distccmon-gnome is very cool.
4. using distcc with Gentoo transparently involves modifying your path and this can make non-root compilations troublesome (permissions on distcc lock files). I haven't figured this one out yet other than to specify the full path to the compiler: make CC=/usr/bin/gcc rather than CC=gcc.
5. the returns from adding an extra distcc server to the pool drop considerably after the first few machines. Even on a 1 gigabit LAN the costs of distcc catch up with the benefits after a while. This is more of a concern when compiling lots of small files.
6. it can handle cross-compilation with a bit of configuration.
So although distcc can often reduce build time, it's not quite as effective as you might assume or hope at first.
It's not a requirement, it's a recommendation. Mixing gcc versions will give you unpredictable results, some of which are perfectly acceptable, and some of which are fatal.
Even if the major versions are the same, Gentoo applies patches to gcc 3.3.3 that are not present in Debian's 3.3.4 (the major version is 3.3). For example, Debian's gcc doesn't recognise -fno-stack-protector which Gentoo's does, and distcc fails.
nicely said
yes, I agree completely. I revised my opinion in a later post after doing some more digging. Thanks for clarifying.
Well, I wasn't completely correct either it seems, according to these. It's all about assuming something is true without validating it:
l g e-english.org/excerpts/fxbegthe.htm l
http://www.wsu.edu:8080/~brians/errors/begs.htm
http://skepdic.com/begging.html
http://alt-usa
Google.com has lots more.
Oh, and just because lots of people do something doesn't make it right. Although I'm constantly surprised how many people subscribe to this world view.
> There are just lots of people who like making
/. between insults and observations sometimes)
> themselves look stupid while trying to look smart.
Are you referring to me or people who use the phrase incorrectly? (Sorry - hard to tell on
The original post makes use of the phrase "begs the question". This does not mean "to wonder" or "leads me to think" or to "rhetorically enquire" or anything like that. It's plain and simple - it means to take something as given (similar to the concept of conditional probability). For example, you could say something like:
"Begging the question that it's raining tomorrow, would you like to go the cinema?".
In this example, you are asking the person to whom you are speaking to consider the question as if it will be raining tomorrow. You are asking them to ignore the question of whether it will rain, and consider their response assuming it WILL rain. You could ask this too:
"If it rains tomorrow, would you like to go to the cinema?".
You might consider me as a pedant - but you would be wrong (look up pedant). I would argue I am not being pedantic. I am not correcting a trivial mistake or trying to get one-up on the original poster - I am trying to correct an obvious and serious mistake. This is not pedantry, it is sharing knowledge in the hope of improving the use of such language for the benefit of everyone.
Wow - I knew it would happen sooner or later. Is it pretty stable or does it tend to blow up now and again?
Sounds like that keeps you ON, rather than OFF Windows. Read the summary properly next time, eh?
My apologies - I inadvertently missed your point. After re-reading your original post, I see that we agree.
Doesn't work - the problem occurs when loading a savegame, and the values in default.ini are not used in that case. They are supposed to be retrieved from the savegame, but are not and therefore remain at their *coded* defaults of 1.0. Read the threads.
^U kills the entire line (or everything from the current cursor to the end of the line if you prefer and configure it this way) in pico/nano. Emacs too. The bash shell as well. Readline. Probably many others...
"If consumers want a backup of their favourite album, they should buy another copy" (or something very close - it's from memory).
:( This makes me a criminal, which is stupid - I bought the #^@!ing CDs didn't I?!
In New Zealand, it's illegal to make any unauthorised copies of copyrighted audio works at all. Nobody gets charged for doing it (not for personal use anyway) and the Govt is considering changing the law to allow 'personal transcoding' but of course the recording industry is getting mighty steamed up about it.
So, here it's illegal to legitimately buy a CD and rip the tracks to mp3 or ogg/vorbis or whatever to play on my iHP-120
A great game to play with other intelligent people. It's not hard to learn, but difficult to master. There's almost no element of luck in the game (there is one non-player source of entropy, but it's not completely random) but the design of the game leads to billions of possible scenarios. An excellently designed and balanced game - highly recommended.
You can play it online too at BSW.