zanchey

LWN's article on unveil() is a good explanation - the restrictions are permanently applied to the process and its children until termination: https://lwn.net/Articles/767137/

Someone gave me a book called "Danger UXB", about the teams that removed unexploded bombs across the UK during and after WWII, which was unexpectedly fascinating. Incredibly dangerous and painstaking work.

It's hopefully not too tricky - it can't be packaged as a crate using (say) debcargo, as the install path still requires CMake. The Debian experimental package changes are mostly about pulling in the right dependencies (including some internal mangling to support some policy choices).

The University Computer Club at UWA also has a door sensor!

https://door-status.ucc.asn.au/ucc

Runs off a Raspberry Pi with a bodged-up version of https://github.com/ide/pico-door-sensor/tree/main

This is at least the third iteration; some previous iterations are documented here:

https://www.ucc.asn.au/services/door.ucc

It's geek code in the cloud!

https://web.archive.org/web/20090220181018/http://geekcode.c...

Mostly it's because you can't copy and paste stuff from blogs or Stack Overflow.

If you want to write C++03, that's true, but as a maintainer of the fish build system I was having to backport compilers in order to use C++11 features on supported systems until 2020. Modern C++ is still a moving target and newer versions contain a number of features that make it much more pleasant to work with, but it takes decades to percolate into distributions.

They're animated GIFs, which were an extension of the longstanding format and predate CSS

No, through the excellent b3ta newsletter

Now that's how you write a headline.

It's the "similarily old" ZIP comparison for me

It's fine, I won't be staying up late just for HN points!

"Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can."

Interesting how much timing affects HN submissions https://news.ycombinator.com/from?site=github.com/fish-shell

It doesn't even support named pipes - the function's been broken for years. Interestingly it doesn't actually seem to matter a great deal, at least now that temporary files are usually on a fast disk.

I wonder about the trade-offs in writing a completely new server compared to a backend for BIND or PowerDNS.

To reprise a previous comment, I think vi mode suffers because it's a relatively niche feature - none of the current committers use it as far as I know, and pull requests to improve it are relatively infrequent. 1.8% of the pull requests into the (not yet released) 3.2.0 are for Vi mode, which is a slight increase on previous milestones, and includes support for dh, dl, c0, cf, ct, cF, cT, ch, cl, y0, tilde, ci', ci", yi', yi", di' and di".

I don't think it helps that it's this huge target area which (the small number of?) users use a slightly different 10% of, and it can be quite complex to integrate new features into existing editor state.

The only dependency the web configuration tool should bring in is Python, which is already an optional dependency for the manual page completion generator. You can install and run fish without ever running the web configuration.

I used to have access to heaps of weird real machines as well, but sadly everything now is x32/x64.

The behaviour was initially imported from zsh's PROMPT_SP:

https://github.com/fish-shell/fish-shell/issues/397

One of the problems with the suggested solution in the article is that it doesn't apply to other people's view of your calendars - so my partner had an event from my calendar clogging her view but I couldn't see it to remove it!

Job control should be fully featured - backgrounding, stopping/continuing, and disowning are all implemented. If there's something missing we'd definitely look at adding it.

I think vi mode suffers because it's a relatively niche feature - none of the current committers use it as far as I know, and pull requests to improve it are fairly infrequent. It gained t/T/;/,/d{f,F,t,T} in 3.0 in two different pull requests, which represents about 1% of all PRs in the 3.0 cycle.

I don't think it helps that it's this huge target area which (the small number of?) users use a slightly different 10% of, and it can be quite complex to integrate new features into existing editor state.

If you liked that, you'll love Comic Papyrus!

http://www.barthandco.com/blog.php?i=5

Anyone remember the articles in Uplink? This feels like it could easily have been lifted from the game.

Automatic roaming seems to be the killer feature that nobody has noticed - I know IPsec has this to a degree but Wireguard looks like it works much faster.

You can have most stuff in Australian healthcare good, cheap or fast. Pick two.

Are you opting out? I keep remembering that AHPRA applied for warrantless access to metadata, and thinking that perhaps I might be better without a record in case the wideranging provisions for access by other agencies get deployed too liberally.

There's definitely room for innovation - fish is for me but I'm always impressed with the work being done on both new and old shells. One thing fish doesn't do is get much into the semantics of how processes interoperate, and I'm interested to see if there's a new idea that can gain some traction in that regard.

Sadly not.