Markdown largely serves the same role as things like vocal emphasis and intonation in speech. Here are some example sentences that have slightly different semantics communicated by markdown differences.
Ugh, troff. It's mind-boggling that the closest way to have an actual (hyper)link in a manpage is to use your pager's "search for text" function. No, "JuSt usE gNu iNfO it'S beTtER" is not an answer either.
groff can produce output with links in it, and does by default in HTML mode! The GNU version of the Unix man page macro set has .UR and .UE for “URI start” and “URI end”. (I don't know whether these were present earlier in the lineage or whether they were introduced by GNU.) Also, the lowdown Markdown converter when in man output mode will output those for links. For fun, try:
echo 'Hi there! Have a [hyperlink](https://www.gnu.org/software/groff/manual/groff.html).' | lowdown -st man | groff -man -Thtml
There's also support for OSC 8 terminal hyperlink sequences throughout most of the groff toolchain: grotty(1) supports outputting them, and less(1) supports passing them through, including ^O^P and ^O^N gestures for moving between them. But man(7) says they're not enabled for grotty output by default. “Options” describes the rationale in its item for “-rU1”: “grohtml enables them by default; grotty does not, pending more widespread pager support for OSC 8 escape sequences.”
So if I set MANROFFOPT=-rU1 in the environment, I can get clickable links in man… if the man page author included them that way in the first place. I'm not sure how common that is in the wild, but grepping the ones on my system, I find firejail(1) contains a link to a GitHub issue embedded in that way, and it does indeed work when I hit ^O^N to seek to it and then C-mouse1—though the mouse gesture I have Alacritty using for links doesn't seem to work through tmux (there might be a way involving twiddling the tmux terminal-features setting, but I ran out of steam before trying this), and I didn't see a great way to get either grotty or Alacritty to style them on display instead of having them blend into the surrounding text, so it's still kind of scuffed in practice. (Though I bet the cool kids have moved on from Alacritty by now?) less displays the link target in the status line when you use the navigation commands, so it's not inaccessible, but for opening selected links directly from less with the ^O^O gesture rather than leaning on terminal support, it looks like you need to explicitly set the LESS_OSC8_ANY and/or LESS_OSC8_‹scheme› environment variable to a shell command that outputs a shell command pattern to substitute the link into; if I set LESS_OSC8_ANY='echo xdg-open %o' then it passes it to my Firefox. I wonder if they'd take a patch (or if any existing distributions patch it) to use that as the default?
That was a fun little rabbit hole to go down, thank you.
I mostly care about links inside the man page (look at man bash — there are tons of internal references like "described below under CONDITIONAL EXPRESSIONS" or "section SHELL BUILTIN COMMANDS below", or operators being underlined and looking like hyperlinks, which you can't easily interact with to just go to where they refer to. You have to employ full-text search, but it also turns up the references themselves, and good luck searching for the place where e.g. command "." is described) and links to other man pages, not the normal Internet URLs being clickable (those things are trivially copy-pastable into a browser next window).
Let's also imagine an alternative reality where some reasonable percentage of the $2.5T in current year AI spending was instead invested in the "general intelligence" researchers we already have for the same purpose. I think it's a pretty reasonable expectation that 1) they'd probably make more progress and 2) that money would help a lot more people in the process (through jobs and economic activity).
We shouldn't use the word "species" lightly with hominins. There's no accepted way to properly classify archaic humans.
For example, some paleoanthropologists classify most archaic humans as h. sapiens. Anatomically modern humans become h. s. sapiens, neanderthal become h. s. neanderthalensis. This incorporates the middle pleistocene hominins from mainland Asia pretty well to boot. Many of those same people also use the "conventional" binomial terminology when they're not making a very specific point, so you can't just look at usages to understand where they're coming from.
There's also a hundred other classifications, some giving neanderthals their own species, others including it with heidelbergensis, and so on. None of them has clearly "won" and probably won't while we keep publishing "new" transitional forms every couple of years.
Sure... and it would help if there was more consistency in general.
But given that there isn't, we should at least maintain internal consistency. That's what I was commenting on above. You can't use one conceptual framework for Neanderthals/Eurasia and another for Sapiens/Africa. It's confusing... and you end up with statements that are essentially false.
Neanderthal and Sapiens exist approximately concurrently. The "classic neanderthal" form doesn't predate sapiens. It only predates Sapiens if we define "Neanderthal" from the point of divergence. If we do that, we need to define Sapiens the same way. It can't be the establishment of a founder population for one and the emergence of a distinct form for the other.
I'm not advocating for one system or another... or even for the establishment of one consistent system necessarily.
Valve's most anticompetitive rule is that steam keys you distribute outside steam shouldn't be sold for less than the price on steam. Would that Apple were the same.
The unitasker advice is also a bit difficult for inexperienced people to follow, from what I've seen. A stand mixer is a great multitasker on paper, whereas a speed peeler does exactly one thing. Yet the latter will be used massively more often than the former in most kitchens. Probably the most used tool in my kitchen (after knives and cutting boards) is the kettle, another unitasker.
I generally agree with that and there are some small kitchen appliances I don’t use often but when I need them I need them. Funnily an electric drip coffee maker is one of the things I somewhat regret replacing after a kitchen fire but I think insurance and may be handy for company at some point.
How can you possibly know which type of repo you're in ahead of time? My experience is that "temporary" code frequently becomes permanent and I've also been on the other side of those decisions 40 years later.
This is a huge part of how SV as a whole works. People figure out what works and point out how to do things better at their next roles. It's mostly a good thing. The main downside is that it exacerbates tendencies to cargo cult apply solutions for problems that come from a particular organizational scale to orgs without them.
My cat is an idiot.
My cat is an idiot.
My cat is an idiot.
reply