Forum comments in chronological order
Disclaimer: I am not responsible for what people (other than myself) write in the forums. Please report any abuse, such as insults, slander, spam and illegal material, and I will take appropriate actions. Don't feed the trolls.
Jag tar inget ansvar för det som skrivs i forumet, förutom mina egna inlägg. Vänligen rapportera alla inlägg som bryter mot reglerna, så ska jag se vad jag kan göra. Som regelbrott räknas till exempel förolämpningar, förtal, spam och olagligt material. Mata inte trålarna.
- Jun 2007
- Aug 2007
- Oct 2007
- Nov 2007
- Dec 2007
- Jan 2008
- Feb 2008
- Mar 2008
- Apr 2008
- May 2008
- Jun 2008
- Jul 2008
- Aug 2008
- Sep 2008
- Oct 2008
- Nov 2008
- Dec 2008
- Jan 2009
- Feb 2009
- Mar 2009
- Apr 2009
- May 2009
- Jun 2009
- Jul 2009
- Aug 2009
- Sep 2009
- Oct 2009
- Nov 2009
- Dec 2009
- Jan 2010
- Feb 2010
- Mar 2010
- Apr 2010
- May 2010
- Jun 2010
- Jul 2010
- Aug 2010
- Sep 2010
- Oct 2010
- Nov 2010
- Dec 2010
- Jan 2011
- Feb 2011
- Mar 2011
- Apr 2011
- May 2011
- Jun 2011
- Jul 2011
- Aug 2011
- Sep 2011
- Oct 2011
- Nov 2011
- Dec 2011
- Jan 2012
- Feb 2012
- Mar 2012
- Apr 2012
- May 2012
- Jun 2012
- Jul 2012
- Aug 2012
- Sep 2012
- Oct 2012
- Nov 2012
- Dec 2012
- Jan 2013
- Feb 2013
- Mar 2013
- Apr 2013
- May 2013
- Jun 2013
- Jul 2013
- Aug 2013
- Sep 2013
- Oct 2013
- Nov 2013
- Dec 2013
- Jan 2014
- Feb 2014
- Mar 2014
- Apr 2014
- May 2014
- Jun 2014
- Jul 2014
- Aug 2014
- Sep 2014
- Oct 2014
- Nov 2014
- Dec 2014
- Jan 2015
- Feb 2015
- Mar 2015
- Apr 2015
- May 2015
- Jun 2015
- Jul 2015
- Aug 2015
- Sep 2015
- Oct 2015
- Nov 2015
- Dec 2015
- Jan 2016
- Feb 2016
- Mar 2016
- Apr 2016
- May 2016
- Jun 2016
- Jul 2016
- Aug 2016
- Sep 2016
- Oct 2016
- Nov 2016
- Dec 2016
- Jan 2017
- Feb 2017
- Mar 2017
- Apr 2017
- May 2017
- Jun 2017
- Jul 2017
- Aug 2017
- Sep 2017
- Oct 2017
- Nov 2017
- Dec 2017
- Jan 2018
- Feb 2018
- Mar 2018
- Apr 2018
- May 2018
- Jun 2018
- Jul 2018
- Aug 2018
- Sep 2018
- Oct 2018
- Nov 2018
- Dec 2018
- Jan 2019
- Feb 2019
- Mar 2019
- Apr 2019
- May 2019
- Jun 2019
- Jul 2019
- Aug 2019
- Sep 2019
- Oct 2019
- Nov 2019
- Dec 2019
- Jan 2020
- Feb 2020
- Mar 2020
- Apr 2020
- May 2020
- Jun 2020
- Jul 2020
- Aug 2020
- Sep 2020
- Oct 2020
- Nov 2020
- Dec 2020
- Jan 2021
- Feb 2021
- Mar 2021
- Apr 2021
- May 2021
- Jun 2021
- Jul 2021
- Aug 2021
- Sep 2021
- Oct 2021
- Nov 2021
- Dec 2021
- Jan 2022
- Feb 2022
- Mar 2022
- Apr 2022
- May 2022
- Jun 2022
- Jul 2022
- Aug 2022
- Sep 2022
- Oct 2022
- Nov 2022
- Dec 2022
- Jan 2023
- Feb 2023
- Mar 2023
- Apr 2023
- May 2023
- Jun 2023
- Jul 2023
- Aug 2023
- Sep 2023
- Oct 2023
- Nov 2023
- Dec 2023
- Jan 2024
- Feb 2024
- Mar 2024
- Apr 2024
- May 2024
- Jun 2024
- Jul 2024
- Aug 2024
- Sep 2024
- Oct 2024
Sep 2014
Anonymous
Tue 2-Sep-2014 16:01
Tue 2-Sep-2014 16:01
the VT100 was not a colour terminal as the text suggests, though.
seems so, just checked the manuals online. http://www.vt100.net/docs/
do you perhaps know which terminal introduced color attributes for escape sequences?
Anonymous
Thu 4-Sep-2014 11:55
Thu 4-Sep-2014 11:55
Seriouse Condencending Wonka meme
Oh, you got an old-school party in the non-US
That must be soo better than out dubsteps.
Oh, you got an old-school party in the non-US
That must be soo better than out dubsteps.
Anonymous
Thu 4-Sep-2014 23:13
Thu 4-Sep-2014 23:13
The Plan 9 operating system completely does away with TTY, signals, and ioctl. Everything in Plan 9 is either a file or represented as a file.
A case against syntax highlighting
Anonymous
Sun 7-Sep-2014 20:37
Sun 7-Sep-2014 20:37
"this blog article is bullshit"
Anonymous
Tue 9-Sep-2014 22:08
Tue 9-Sep-2014 22:08
This is basically a nice thought technology for some people to try rather than rejecting it out of hand.
I work in 'big iron' mainframes where some of the editing tools lack syntax highlighting and others have syntax highlighting. Most new comers and experienced people report finding the lack of syntax highlighting slows down their coding and leads to more errors that are harder to find. A minority (maybe the geniuses?) report finding removing syntax highlighting a boon and I have long advocated that they develop schemes in the tools where syntax highlighting is available to remove or minimise syntax highlighting.
I haven't kept hard numbers but in my estimates are that about 90% of people write better code, faster, with syntax highlighting and 10% the opposite. Given my experience it makes sense for you to follow Linus' advice and try out the options and see what group you are in.
From years of personal experience I know I am in the 'syntax highlighting helps me' camp. I FTP code out of environments without syntax highlighting to put it into editors with highlighting and often immediately see bugs I have spent ages searching for or find design flaws that leap off the screen with some help (these are declarative and or interpreted tools with no compiler to help me).
But that doesn't mean the same is true for Linus or for you. Give it a try and find out.
Perhaps I am in the dumbo camp and Linus and you are in the genius group. It is cheap to find out. If I have a bad knee I will use crutches without shame, it would be better to not have to use them but if they get me to my goal faster or with less pain then I am not going to deny myself the help on a matter of principle. But if crutches are getting in your way more than they help then you would be a fool to keep using them.
The argument that people should only comment if they have solid statistical data is simply missing the point of what stats do and don't tell you. Group stats tell you nothing about any individual in a group. Even if 99.999% of people do better with option A if YOU are one of the 0.001% who do better with option B then 100% of YOU do better with option B. Therefore you should use option B if it makes sense to do so even though it would be a bad choice statistically.
I work in 'big iron' mainframes where some of the editing tools lack syntax highlighting and others have syntax highlighting. Most new comers and experienced people report finding the lack of syntax highlighting slows down their coding and leads to more errors that are harder to find. A minority (maybe the geniuses?) report finding removing syntax highlighting a boon and I have long advocated that they develop schemes in the tools where syntax highlighting is available to remove or minimise syntax highlighting.
I haven't kept hard numbers but in my estimates are that about 90% of people write better code, faster, with syntax highlighting and 10% the opposite. Given my experience it makes sense for you to follow Linus' advice and try out the options and see what group you are in.
From years of personal experience I know I am in the 'syntax highlighting helps me' camp. I FTP code out of environments without syntax highlighting to put it into editors with highlighting and often immediately see bugs I have spent ages searching for or find design flaws that leap off the screen with some help (these are declarative and or interpreted tools with no compiler to help me).
But that doesn't mean the same is true for Linus or for you. Give it a try and find out.
Perhaps I am in the dumbo camp and Linus and you are in the genius group. It is cheap to find out. If I have a bad knee I will use crutches without shame, it would be better to not have to use them but if they get me to my goal faster or with less pain then I am not going to deny myself the help on a matter of principle. But if crutches are getting in your way more than they help then you would be a fool to keep using them.
The argument that people should only comment if they have solid statistical data is simply missing the point of what stats do and don't tell you. Group stats tell you nothing about any individual in a group. Even if 99.999% of people do better with option A if YOU are one of the 0.001% who do better with option B then 100% of YOU do better with option B. Therefore you should use option B if it makes sense to do so even though it would be a bad choice statistically.
Anonymous
Wed 10-Sep-2014 20:07
Wed 10-Sep-2014 20:07
This is extremely helpful in timing your code! Have saved hours of debugging. Thanks!
Anonymous
Sat 13-Sep-2014 12:33
Sat 13-Sep-2014 12:33
The basic idea is that every pipeline is a job, because every process in a pipeline should be manipulated (stopped, resumed, killed) simultaneously.
Not just pipelines, every command is a job in shell's parlance. Job is a userspace thing, only maintained by shell, not kernel.
http://www.gnu.org/software/bash/manual/bashref.html#Shell-Commands
Niz
Not just pipelines, every command is a job in shell's parlance. Job is a userspace thing, only maintained by shell, not kernel.
http://www.gnu.org/software/bash/manual/bashref.html#Shell-Commands
Niz
Anonymous
Fri 19-Sep-2014 23:55
Fri 19-Sep-2014 23:55
This are the first steps for the next iPhone KillerApp ! :)
Very delicious flowers there...
Very delicious flowers there...
Anonymous
Wed 24-Sep-2014 12:34
Wed 24-Sep-2014 12:34
By far the most amazing article about TTY I have ever read, thanks!