The project page for mod_virgule gives as its project TO-DO list a link to
http://rainwaterreptileranch.org/steve/sw/mod_virgule/todo.html
but that is a broken link.
Is there a most-current version of the project's TO DOs?
http://rainwaterreptileranch.org/steve/sw/mod_virgule/todo.html
Is there a most-current version of the project's TO DOs?
I'll crosspost something I wrote there: a recommendation for cabal-dev as a way of making Haskell package management sane:
Cabal is a package manager that by default compiles packages either to a system database (if invoked as root/admin) or a per-user database. Since Haskell code is very often fussy about exact version numbers, and because Cabal offers essentially no way to uninstall packages, this is very painful. cabal-dev is a front-end to Cabal that gives you per-directory repositories: suddenly conflicts go away, and you can remove packages by deleting the directory's repository and reinstalling everything again. It's a kludge, but it is very helpful.
He cited an HN thread, Female FOSS dev quits tech industry due to harassment, and in particular this post from jxcole: I was going to start a rant about how this behavior is encouraged by the macho men online, but this was just one guy harassing her. "Due to harassment" reads as due to harassment from the community, but she gave in to one idiot. She let him win.
I answered as follows:Well, I kind of agree with this in part, but it is often trotted out as a reason why it's the victim's fault. Let's see what's badly wrong with it by looking at things another way.Standing up for what is right is not something that we weaker mortals should leave to the heroes. We have a breaking point, a point above which we can't take it. That does not mean we should not take risks to do what we find right. You should not be "disappointed" with the victim, but supportive, and we should be encouraging others to take these risks to do what is right as well. The more of us there are, the we achieve.
Since I'm on the subject, let me plug Skud's long post, On being harassed: a little GF history and some current events.
Despite the event that lies behind this post, I'm more optimistic than I was a year or so ago that the free software community can sort itself out on this one, since the fair-weather friends do seem to sometimes be a bit more aware that there might be something wrong with their behaviour. Skud deserves special praise for her efforts that have made a positive difference, as does Matthew Garrett. who I suspect will not find himself unable to continue with free software.
I still write C. I work on implementations of safe languages -- languages that don't have the same kinds of fundamental vulnerabilities that C and C++ have. Eventually the amount of C in the world will stop growing, and decline as pieces that are now written in C will be written in Python, in JavaScript, in Guile: in short, in languages that don't launch the missiles when you try to write beyond the end of an array.C has had a great run; we should celebrate it. But its time has passed. What is your migration strategy? How are you going to stop writing C?
I actually had a dream about this, where I was reading a paper about an extension to Lua that allowed Cyclone+Lua programs to have whole-system correctness guarantees. I don't often remember my dreams, funnily enough.
Bad RSS feeds? Really? I guess it's possible, but I assumed that StevenRainwater was backing out code that was not working, or has safety issues arising from the recent libxml2 migration.
viper-mode
's support for the ex command set, implemented in the viper-ex
package as a part of the Viper vi-emulation package, is mostly orthogonal to the rest of Viper, meaning the Viper implementation of ex can be used without activating Viper mode. Hence you can bind the viper-ex
function to a key in any Emacs mode and use commands like .,$s/wrong/right/g
there. It is quite straightforward to use this to support vi-like macros, which are sometimes quite a bit briefer than their Elisp equivalents.To get started, you need to import the viper-ex
package, which defines the viper-ex
interactive command, and which has some dependencies on the rest of Viper, ones which could be pruned without much difficulty. The ex commands are more pleasant with line numbering. The following Elisp will configure this, with viper-ex
bound to C-:
(require 'viper-ex)
(require 'viper-keym)
(require 'viper-cmd)
(require 'linum)
(define-key global-map (kbd "C-:") 'viper-ex)
(global-linum-mode)
Advogato's new libxml2-based text handler
This is new, I think. It seems to have fewer glitches than the old code, so kudos to StevenRainwater for getting this done.
I've no issue with having both constants about, using π or τ whichever is simplest, but I find that π feels more fundamental to me. A couple of considerations:
As a datapoint, I do have a Gmail account, and I try only to use that for mailing lists, although some family members seem to prefer using that account despite my protestations. I don't consider the privacy implications of my mailing list subscriptions to be particularly invasive, especially since the fact of my subscribing to several of them is public information. I have a web.de account as an emergency backup for correspondence with my hosting service, and apart from these cases, I try to use the email accounts I maintain myself for correspondence, with the considerations LaForge talks about looming large.
It occurs to me that I could try to get a friend to administer my emergency email account, but then I recall that I've had trouble with that in the past.
I should think that Joel Coel's answer to the question Using gmail as your primary mail server on Server Fault provides a common answer to LaForge's question too.
Today, let me introduce SEM Media, India offering to "Clue your Wounded Website", and whose graphic design skills are as weak as their brand self-awareness is feeble. For but a taster of their site, I provide a snapshot below.
New HTML Parser: The long-awaited libxml2 based HTML parser code is live. It needs further work but already handles most markup better than the original parser.
Keep up with the latest Advogato features by reading the Advogato status blog.
If you're a C programmer with some spare time, take a look at the mod_virgule project page and help us with one of the tasks on the ToDo list!