529 karma · joined September 21, 2017
It would be great if grep could figure out whether its parent process is an interactive shell or a script, but there doesn't seem to be a reliable way to do that.
programs like make could collect output using a pty rather than a pipe or temp file
This seems brilliant. The pipe mechanism is too dumb to differentiate between these cases - Unix needs a smarter pipe, and pty could be it. Maybe there could be another character in the shell for a pipe that's really a pty like '_', or a digraph like '|p'.
Yes, it should be the responsibility of the build system to control the environment variables set during the build.
What would happen if a build system set one of those, and then somewhere deep in the build system (or even in a shell script called from the build system), someone ran grep in a pipeline
The person adding the 'grep' would need to be aware of whether the build system is using color output or not.
This is also part of why programs like grep are removing environment variables like GREP_OPTIONS: they break scripts.
This seems unfortunate; scripts could just unset GREP_OPTIONS if they care.
He then throws in salacious and irrelevant intimations about race and class ("Because the outdoor recreation community is far whiter, wealthier, and better educated than the U.S. population at large, it’s an interesting case study in how misinformation propagates through privileged communities.")
It's clickbait, exactly the sort of garbage published on the front page of every newsprint weekly - taxi drivers without medallions: scandalous! Boat owners profit from people fishing: another scandal! The real scandal is how any of this passes as journalism.
It's natural to want to apologize if you think you've hurt someone's feelings. Just be aware that some people are addicted to creating drama, and that may have nothing to do with you.
Moral: don't apologize to a truly toxic person - instead remove them from your life immediately.
https://github.com/roswell/roswell
(As a side-note: Perl 5 was really the ideal language for this, by design; we might be in a different world today if it hadn't been derailed by Perl Forever^W 6).
Perhaps the best use case for Oil is to provide a debugging environment where you can figure out what your legacy shell scripts are doing, and rewrite them in another language.
> Unlearning bash-isms is not a liberty I can afford, as I need to be proficient when I SSH into a machine I do not own or control.
This is a slippery slope. I have heard things like, "don't make your own custom aliases / shell functions, because they won't be available when you SSH to another machine." Forcing yourself to always use the lowest common denominator of software is not a fun path.
> Only housing near economic opportunity means anything.
Your error is that you're obsessed with trying to fix this within a market economy, by specifically housing them in areas of high economic activity where they can supposedly find "opportunity". That won't work and is counterproductive.