@plragde @regehr The original was with "music", FWIW -- also some slight wording changes for increased gender neutrality I see. And while I can sort of sympathize with the font change, in some ways I wish it kept the faux-script...

@mcc @megmac @swetland All the ones that translate it to "/tmp" above also do the same with ./. instead of . (not hugely surprising). It gets interesting with other ways of spelling the same thing though:

$ for s in bash zsh dash mksh 'busybox sh' tcsh rc; do echo $s; strace -qqq -e chdir -e signal=none $s -c 'cd ./foo/..'; done
bash
chdir("/tmp/./foo/..")                  = -1 ENOENT (No such file or directory)
chdir("./foo/..")                       = -1 ENOENT (No such file or directory)
bash: line 1: cd: ./foo/..: No such file or directory
zsh
chdir("/tmp/foo/..")                    = -1 ENOENT (No such file or directory)
chdir("./foo/..")                       = -1 ENOENT (No such file or directory)
zsh:cd:1: no such file or directory: ./foo/..
dash
chdir("/tmp")                           = 0
mksh
chdir("/tmp")                           = 0
busybox sh
chdir("/tmp")                           = 0
tcsh
chdir("./foo/..")                       = -1 ENOENT (No such file or directory)
chdir("./foo/..")                       = -1 ENOENT (No such file or directory)
./foo/..: No such file or directory.
rc
chdir("./foo/..")                       = -1 ENOENT (No such file or directory)
rc: ./foo/..: No such file or directory

bash & zsh handle it correctly IMO, whereas dash, mksh, and busybox get a bit overzealous and hallucinate the existence of a directory that isn't there (or isn't actually a directory -- the above is unchanged even after running touch foo, aside from s/ENOENT/ENOTDIR/).

@swetland @mcc @megmac Yeah, as alluded to elsewhere in the thread, this is due to the shell doing "unexpected" things internally... cd . doesn't really translate to chdir(".") in most cases:

$ for s in bash zsh dash mksh 'busybox sh' tcsh rc; do echo $s; strace -qqq -e chdir -e signal=none $s -c 'cd .'; done
bash
chdir("/tmp")                           = 0
zsh
chdir("/tmp")                           = 0
dash
chdir("/tmp")                           = 0
mksh
chdir("/tmp")                           = 0
busybox sh
chdir("/tmp")                           = 0
tcsh
chdir(".")                              = 0
rc
chdir(".")                              = 0

So the "trick" in question here won't work if you're using rc or tcsh.

Sure that's not a swan, @tedu? Regardless, I support equal opportunity honking.

@jlevon @pervognsen @cliffle Is vimeo demanding that? The link above plays fine for me without any login, FWIW (yt-dlp or similar might also be worth a shot if browser-based playback is horked for some reason).

@shenki Not a lot of information available online that I can see, but from what I can glean from the dts and this page that's a quad 1.6GHz Cortex-A35 with 32K L1 I & D caches, a 512K L2, and probably multiple gigs of memory? Not too long ago those would've been pretty decent specs as a server all its own!

Maybe the host CPU will eventually become redundant and can be depopulated for cost savings...or perhaps the 2700 will need a 2500 or 2600 on the side to manage it in turn.

@arj Hah, never noticed that file's existence before -- mostly different stuff though. And actually looking at it now, the email-related stuff is maybe a bit more than 10%...in all its messy ad-hoc glory, plus accessories: https://gist.github.com/zevweiss/63482cda0e7003a58530e4e2eabb2fb0

@arj I've taken to keeping a file called CHECKLIST in my kernel git tree that I run through before taking the --dry-run off of git send-email. Granted, only about 10% of it is specific to the emailed-patches workflow, most of it's just generic "do docs or MAINTAINERS need updates?" and "spellcheck commit messages" kinds of things.

@w8emv You got one out of two? Lucky!

@regehr @scheidegger Oh wow -- this little aside in that article is...certainly something:

Slack had used 4 times more energy than the Z3 app despite less time on screen

@petersanchez I think my answer would be "angrily".

@monsieuricon But which of the umpteen not-quite-compatible markdown dialects would we use instead?? Let the bloodbath begin!

@regehr @porglezomp @wilcoxjay I feel like ld's -( and -) flags are some sort of software analog to mimicry in evolution, trying to frighten people off by looking like one of those but not actually (AFAIK...) implementing any sort of recursion.

@cks @dalias Yeah, I end up using shift-right-click often, but was hoping for something that would obviate the need for the modifier.

I see the opposite behavior though -- I've never seen shift-right-click do anything but bring up firefox's "real" native context menu as it should, but upon experimenting with dom.event.contextmenu.enabled=false right-clicking a link in Discord brings up both the firefox menu and Discord's obnoxious in-page one. Alas...

@cks @dalias Ooh, great find! Happen to know of anything similar for right-click?

@petersanchez khal plus vdirsyncer perhaps? (Works reasonably with Radicale server-side for me.)

@cliffle Ah, indeed -- this was the...fifth or sixth for me I think? But the first in probably ten years or so, so I was happy to see them still going strong.

@cliffle

I hope it was helpful to at least one person.

Speaking as one such individual, I can confirm you cleared that bar! Informative and fun.

@tedu Maybe check hasanyoneregisterediscurl8dot4dot0outyetdotcomyet.com?

@lorddimwit @mattb Only as a last-ditch fallback if you don't have sufficient permissions on /dev/console or /dev/kmsg.

@barrelshifter One order of fun roll loops please.

@lorddimwit Please tell me you're not building a third-party implementation of AppleScript.

@arj I think I'm gonna go erase some flash chips just so I can reflash them again.

@tedu I haven't used one in any seriousness in some years now, though from the last time I did I recall some wistful sadness at the general feeling that macports was a dying project, losing out to (the IMO markedly inferior) homebrew.

From a skim of those comments it sounds like maybe macports has had some degree of resurgence though? So if in the future I am in fact ever compelled to use a mac again, perhaps at least macports will still be a viable option...

@robey @swetland I use insert heavily! (Shift-insert produces the equivalent of a middle-click to paste the current primary selection text, at least in my terminals.) I also occasionally use a bare insert to toggle overwrite-mode in emacs, but that's admittedly pretty rare.

@robey [Nods emphatically] Yeah, Framework's product announcements have really thrown into stark relief just how stagnant and boring the rest of the consumer-electronics industry has gotten.

@Obdurodon The slope of the computer-improvement line has really leveled off -- I'm typing this on a computer that's 10 years old, and in 2023 that's basically fine, and aside from some relatively minor performance differences not really noticeably "old". Running a 10-year-old computer in even, say, 2005 would have been laughable.

@tedu But are the files still named *.jpg? Apple seems to like doing that.

@benjojo @electronic_eel Entirely fair, though if you do ever change your mind and want to pursue that, I've done a number of ASRock OpenBMC ports (and maintain the meta-asrock layer in the OpenBMC tree) and would be happy to offer assistance!

@tedu What about "defun" -- does the negating prefix absolve it? (Okay, not strictly a keyword I suppose, but the moral equivalent.)

@lorddimwit

YEARS OF PROGRAMMING yet NO REAL-WORLD USE FOUND for applying an operation to anything more than a PAIR OF VALUES

My ?: operator would like a word!

@arj "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." They've finally done it!

@stephen0x2dfox Proprietary BMC firmware (especially from a particular three-lettered vendor, it seems) has been and likely will remain for as long as people care to poke at it a wellspring of easily-exploited vulnerabilities, yes.

Open-source alternatives are, I'd hazard an educated guess, likely to be substantially better in that regard, however. I'm hedging a bit here of course because there's still lots of non-memory-safe code involved (though some of us are working on getting Rust integrated), but (a) while there are still likely to be remotely-triggerable bugs, I'd guess they're probably somewhat less numerous/egregious, and (b) enabling some basic protections like ASLR and a non-executable stack at least raise the difficulty level of writing exploits a bit.

@leah @benjojo Indeed -- much like git's index, the exposed distinction between buffer content and file content (and explicit synchronization of the two) is while arguably an implementation detail that "should" (some think) be hidden from the user, also a very useful tool for users who understand it.

@erincandescent @benjojo You can also disable flow control with stty -ixon, reclaiming Ctrl-s/Ctrl-q for one's own purposes -- by default in bash, respectively forward-search-history (like Ctrl-r but in the opposite direction) and quoted-insert (handy for inserting literal tabs and such, but also available via Ctrl-v).

@arj Oog, maybe toss in technical writing too while we're at it!

@mxshift @fasterthanlime @sigmasternchen See also

@lorddimwit @todb Oh wow, is that EtherApe I spy at the very end (t=60s) of that clip? Judging by the release date of the film and when I was actively working on that project it's borderline, but maybe just maybe there's a little bit of my code in a movie! Guess that means I might have to watch it, despite the (predictably) terrible reviews...

@arj Should we add file formats and device register interfaces to that set as well? (Or maybe they're already included for a sufficiently general definition of "protocol"...)

@tedu Well, according to the coverage pie charts, 91.4% of that module is either fully or indirectly documented, so I think you just need to work on your reading comprehension?

@Obdurodon Wait, but doesn't "vanished" imply that it was actually here at some point?

@bascule @djm While perhaps technically a slightly different case, a trailing slash can also determine whether a symlink is dereferenced or not.

@monsieuricon @gregkh How about a tarball?

@monsieuricon I haven't noticed any other problems myself, but would whatever this is referring to have anything to do with me receiving 40 copies of this email from @gregkh?