links: Chronological entries
These are my WanderingThoughts
(About the blog)
Full index of entries
Recent comments
This is part of CSpace, and is written by ChrisSiebenmann.
Twitter: @thatcks
* * *
Categories: links, linux, programming, python, snark, solaris, spam, sysadmin, tech, unix, web
This is a DWiki.
GettingAround
(Help)
Link: My current dmenu changes
As I've mentioned before, I have a set of changes I've made to dmenu to make it work better for me. I have now put my current patch online as dmenu-4.5-tip.patch in case anyone is interested. I happen to like all of my changes, but then I would. See the start of the patch for a description of what it includes (and then the documentation for the new switches in the revised
dmenu.1manpage).I expect that I'll update this patch periodically as the main dmenu source itself gets updated, but so far the latter doesn't seem to change very often.
PS: to save the energy of anyone asking: while my patch set contains a bugfix for dmenu's handling of
-m(and the manpage), I don't currently feel like breaking it out as a separate patch and then trying to send it upstream. It's too much work for too little chance of success.Update, August 4th 2015: The patchset linked above is now out of date, per here. My dmenu changes are now in my github repo for my version, split up into multiple commits that you can cherry-pick as desired.
(2 comments.)
Link: Go at Google: Language Design in the Service of Software Engineering
Go at Google: Language Design in the Service of Software Engineering is an article version of a Rob Pike keynote on, well, let me just quote:
The Go programming language was conceived in late 2007 as an answer to some of the problems we were seeing developing software infrastructure at Google. [...]
Go was designed and developed to make working in this environment more productive. [...]
The article then discusses what this means and how various aspects of Go's design were consciously shaped by a number of pragmatic software engineering issues in building large software across large(r) teams. I find it really interesting reading (and I keep referring to it and having to re-find it, so it's clearly time to put this somewhere more obvious).