Recent comments on posts in the blog:
Your example starts screen
with a script containing screen -t irssi irssi
.
This script is not really a config file like the ones you would use via screen's -c configfilename
option.
script
's "real" config files can contain commands which would be not recognised by your way of doing it.
Your way is starting screen -t ...
in an already running outer screen
what makes the inner screen recognise running in screen and therefore delegating its commands to the outer screen.
Thanks for your comment.
Yes it's missing content because of a formatting error in the source (there should be an empty line before the code block). The output that it was supposed to have is:
$ awk <testdata '{ split($0, A, /->/); print A[2] }'
b
I'll get it fixed.
Hi, thanks for this great blog!
Regarding the cut example: the last line says "For this more complicated tools need to be used. $ awk /); print A[2] }' b", I think something is missing. Regarding the sort/uniq paragraph: the option I find more useful of uniq is "-c" for counting occourrences.
Thank you again, Riccardo
Computer/Programming/Information Ethics is a whole discipline in itself, though it is certainly a topic that every programmer really ought have some grounding in.
The Wikipedia page on the topic - https://en.wikipedia.org/wiki/Programming_ethics - is a good place to start for more general information and some ideas about what to consider.
For a more philosophical exploration of the topic, the Stanford Encyclopedia of Philosophy has some good articles, such as: https://plato.stanford.edu/entries/ethics-computer/ and https://plato.stanford.edu/entries/computing-responsibility/
There are also a whole range of books on the topic both from computing perspectives and more philosophical ones.
The Open University also offers a free course on the subject, Introducing Ethics in Information and Computer Sciences
"Does it promote $BADTHINGS, directly or indirectly?"
Slippery surface, as one can easily put GPG/TOR/GNUNet (and loosely following your example, R) in that $BADTHINGS basket.
A medical professional cures people regardless, a lawyer defends their client regardless: is a Free Software contributor more equipped to indulge in this deontological Pandora's box?
Some things to add:
You should add a list of all the reserved characters on Windows, as well as the COM*, etc. already listed. From https://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#:
< (less than)
Falsehood: Windows UNC paths \FOO refer to a network server. Counterpoint: \.\COM1.
Feel free to use the above.