A System-Witch’s Package Manager Murder Mystery
1–10 of 11 posts
Re: A System-Witch’s Package Manager Murder Mystery
#2Re: A System-Witch’s Package Manager Murder Mystery
#3Nor sure what this article is trying to convey? Is it about grepping wrong defaults for bash? Is it about mentioning the protagonist as much as often? I've read it twice now, and I feel ignorant.
So the author went through an investigation to figure out what was happening, and decided to write down her findings.
----
On a personal note, reading this caused me to look at fish's error message in this case. It mentioned "environment list", but tbh that's still too jargony and non-obvious.
So the next version of fish will now explicitly mention "environment variables" in the error message here, and it will print a hint if the environment variables account for over half the limit.
Re: A System-Witch’s Package Manager Murder Mystery
#4Re: A System-Witch’s Package Manager Murder Mystery
#5Re: A System-Witch’s Package Manager Murder Mystery
#6Re: A System-Witch’s Package Manager Murder Mystery
#7Re: A System-Witch’s Package Manager Murder Mystery
#8This is a great illustration of how Bash and similar shell dialects are convenient for interactive use but terrible as a programming language.
Change my mind: Bash is the PHP of operating systems. Any Bash script becomes tech debt the moment it is written.
Re: A System-Witch’s Package Manager Murder Mystery
#9Nicely written! This is a great illustration of how Bash and similar shell dialects are convenient for interactive use but terrible as a programming language. Change my mind: Bash is the PHP of operating systems. Any Bash script becomes tech debt the moment it is written.