parsley936 has quit [Remote host closed the connection]
<ldlework>
sad
<jtojnar>
I am starting to think the easiest solution to caching dependencies on GitLab would be to run Squid in front of binary cache
<bkv>
cole-h: sphalerite: nevermind, the random crashes were actually due to some awful systemd hacks i was doing
<jtojnar>
but not sure if fetching the data from GitLab cache would not be equally slow
<cole-h>
bkv: F
<gchristensen>
what does F mean?
<cole-h>
"F to pay respects" meme
<samueldr>
I believe it's from the insensitive videogame that used "press F to pay respect" as an action prompt
<gchristensen>
ah
<cole-h>
AKA CoD of Duty
<samueldr>
if you were a console lad it would have been press X to pay respect or something similar
<bkv>
gamer memes
<bkv>
the fsharp package seems to think it was compiled on windows
<bkv>
that's interesting
<drakonis>
fsharp is good
<drakonis>
cole-h: i thnk it was call of duty advanced warfare
<cole-h>
Cawa Doody
<drakonis>
bad game
<cole-h>
F
<bkv>
i had to read that in an american accent in my head
<bkv>
that was uncomfortable
<drakonis>
cowadoody
<samueldr>
why is advanced warfare not a game boy advance game?
<drakonis>
too advanced for game boy advance!
<bkv>
drakonis: yeah, it is pretty good
<bkv>
at least, i love having a vaguely functional interface to the CLR
lassulus_ has joined #nixos-chat
<drakonis>
i've been looking into learning a bit of it for a project
<drakonis>
at least, attempting to.
lassulus has quit [Ping timeout: 256 seconds]
lassulus_ is now known as lassulus
<bkv>
i've become vaguely familiar in it in just a few days
<infinisil>
abathur: Yeah saw that, though didn't really look closely at the context
<abathur>
infinisil: oh, it just reminded me of a discussion around your secret module for nixus leaking a little information about the existence of specific filenames
<abathur>
infinisil: and I had wondered out loud about whether it'd be possible to use a FUSE that pretended all files existed as a way to deny that information, and just a few weeks later someone shared a paper link out of the blue where they made a FUSE that does this, albeit for a different reason
<samueldr>
or you could do one that pretends no file exists unless you have access to it, when you *open* it (not even listing)
kalbasit has quit [Ping timeout: 256 seconds]
rajivr has joined #nixos-chat
kalbasit has joined #nixos-chat
waleee-cl has quit [Quit: Connection closed for inactivity]
drakonis has quit [Ping timeout: 272 seconds]
<cole-h>
Good news guys
<cole-h>
My package went one state down (OH -> KY).
<cole-h>
At this rate, I'll get it by next millenium.
slack1256 has quit [Remote host closed the connection]
<samueldr>
cole-h: don't worry
<samueldr>
everything's gonna be ohky
<cole-h>
Oh my god
<cole-h>
I can't believe you've done this
<cole-h>
samueldr++
<{^_^}>
samueldr was put on Santa's "nice" list
<cole-h>
SSS+++ execution
<samueldr>
well
<samueldr>
you basically spelled it out for me
evanjs has quit [Ping timeout: 272 seconds]
endformationage has quit [Quit: WeeChat 2.7.1]
evanjs has joined #nixos-chat
cole-h has quit [Quit: Goodbye]
kalbasit has quit [Ping timeout: 240 seconds]
ixxie has joined #nixos-chat
<eyJhb>
Damn it, Michael get a znc
ixxie has quit [Ping timeout: 240 seconds]
sphalerite has quit [Quit: WeeChat 2.6]
sphalerite has joined #nixos-chat
<eyJhb>
The joys. So apparantly xpra does not like i3 :p
<infinisil>
Xpra works at all?
<eyJhb>
ANd my multikey works in xfce without having my cursor over it!
<infinisil>
Last time I heard about xpra I thought it was hopelessly broken
<eyJhb>
It does, it works "well" in i3 (some apps), and better xfce
<eyJhb>
Well, I have no clue how many hacks they have put into it tbh.
<eyJhb>
Considering just using a vncserver + client like Michael suggested
<eyJhb>
It is to isolate my x11 windows from each other
<eyJhb>
Part of my jail setup, now that I have nsjails working
<eyJhb>
Ehh, now back to i3 I guess.
<eyJhb>
Any other way to isolate a window from the others in x11 is appreciated
<bkv>
Xpra is a cool tool, I was considering using it to make my graphical sessions survive even display manager restarts
<bkv>
But now I just use wayland :p
<bkv>
adisbladis: it occurs to me, with xonsh being basically a literal python app, no reason it couldn't be extended to use fish completions through a wrapper, lol
<bqv>
i've just realised i'm running wayland emacs compiled with Xwidgets on... hmm
<bqv>
surprisingly, it doesn't not work
<eyJhb>
Damn it
<eyJhb>
Doesn't seem like VNC is a viable option...
<gchristensen>
I don't think X supports dynamic resizing like that
<gchristensen>
RDP does, I found
<gchristensen>
xfreerdp /dynamic-resolution
<eyJhb>
Proprietary MS
<eyJhb>
Right?
jakob38 has joined #nixos-chat
<gchristensen>
probably linux doesn't support that
<neeasade>
> bqv: i've just realised i'm running wayland emacs compiled with Xwidgets on... hmm
<{^_^}>
error: syntax error, unexpected WITH, expecting ')', at (string):318:60
<neeasade>
X widgets isn't X11
<neeasade>
the naming is confusing
<neeasade>
it's supposed to be like "any" iirc
<bqv>
ahh ok
<eyJhb>
SEE! Remove the X isn't ever consistent with X11
monsieurp has quit [Read error: Connection reset by peer]
monsieurp has joined #nixos-chat
<philipp[m]>
Is there anybody that actually likes cyclic auto completion?
<neeasade>
no
<neeasade>
I want it to just read-my-mind and go
<neeasade>
stupid dumb computer
<bqv>
philipp[m]: i find it useful, i often overshoot
<philipp[m]>
And you don't prefer bash style "complete safe, wait for next input"?
<bqv>
i dunno, it's been so long since i used bash. xonsh completes fish-style
<philipp[m]>
I just get so confused every time cyclic completion comes up and I don't even know any more from what point I started the completion.
<bqv>
to be honest i don't exactly use autocompletion enough for it to matter. there's always either one unique match, or i'll probably just use something more accurate/predictable
ixxie has joined #nixos-chat
<bqv>
one thing i miss about when i used Xorg, is being able to run apps without them reliably crashing at least once a day :D
<bqv>
at least i'm managing to make my environment extremely reproducible and resilient to crashes, heh
FRidh has quit [Quit: Konversation terminated!]
__monty__ has joined #nixos-chat
kalbasit has joined #nixos-chat
ixxie has quit [Ping timeout: 260 seconds]
ixxie has joined #nixos-chat
jakob38 has quit [Remote host closed the connection]
FRidh has joined #nixos-chat
waleee-cl has quit [Quit: Connection closed for inactivity]
endformationage has joined #nixos-chat
kalbasit has quit [Remote host closed the connection]
<philipp[m]>
I'm still unsure whether patching the executable or running it in steam-run is worse. I usually just go for steam-run because it's easier.
<adisbladis>
That background is pretty but I find it distracting, it starts morphing
<colemickens>
"how easy is it to migrate CI/CD off of GitHub Actions to Gitlab?"
<__monty__>
Fwiw, I don't think the models correspond very well but I *have* heard GitLab's CI is more pleasant to work with.
<samueldr>
with my limited experience with both, I think that if your CI/CD relies mainly on nix, it's not gonna be a pain to switch
<adisbladis>
With fairly extensive experience with both, what samueldr said
<samueldr>
now, if you lean heavily within the "actions ecosystem"
<samueldr>
whew
<samueldr>
if you needed another reason to love nix ♥
rajivr has quit [Quit: Connection closed for inactivity]
parsley936 has quit [Remote host closed the connection]
parsley936 has joined #nixos-chat
<joepie91>
guess this is my cue to remind people that centralizing the whole open-source world onto a single centralized proprietary platform is Not A Great Idea
<lassulus>
do you mean nixpkgs or github?
bqv has quit [Quit: WeeChat 2.8]
bqv has joined #nixos-chat
<ixxie>
github
<ixxie>
nixpkgs is not propreitary :D
<__monty__>
I couldn't update my system when I wanted to yesterday because of a github outage. Not something I ever encountered on ubuntu, not sure about arch.
<samueldr>
__monty__: why couldn't you upgrade? if it was packages build, I guess it would happen on archlinux too, with the equivalent custom builds
<samueldr>
custom builds on ubuntu? no thank you
<__monty__>
samueldr: Because I couldn't fetch a new version of channels.
<gchristensen>
joepie91: I am sure we would all be surprised at the odd and wonderful places Nixpkgs has found itself
<lassulus>
there were contributions from the DoD to our weird nixops alternative
<gchristensen>
link?
<joepie91>
lassulus: which of the weird nixops alternatives
<joepie91>
:P
<lassulus>
krops
<joepie91>
they seem to be growing on trees nowadays
<samueldr>
(should we start saying DoD out loud as dud?)
<joepie91>
ah
<gchristensen>
yeah the DoD definitely uses nix,nixpkgs,hydra at least
<eyJhb>
Free laser pointers on AliExpress, wonder if I will ever receive them
<gchristensen>
$100 shipping?
<samueldr>
so glad to soon be done with that horrible thing I'm doing where the development cycle takes ~40 minutes
<eyJhb>
Don't think so, let me see :p
<joepie91>
eyJhb: wait, free?
<cole-h>
gchristensen: "the DoD definitely uses nix,nixpkgs,hydra" That's insane to me (in a good way) -- is there any public info on this, or just that we've had contributions from them?
<eyJhb>
Dicks, I think I have to be a new customer
<samueldr>
language! Richards!
<gchristensen>
cole-h: contributions among other things, and job postings for contractors that use nix,nixpkgs,hydra,+
<cole-h>
:O
<cole-h>
That's super cool.
<gchristensen>
some of it is, some of it I don't find very cool
<cole-h>
Well, I guess the "cool" part comes from "large government entity utilizing relatively niche OS/package manager/tool"
<gchristensen>
but in principle: big names using nix is cool to me
<gchristensen>
yea
<cole-h>
Regardless of how they use it, iMO
bqv has quit [Quit: WeeChat 2.8]
<cole-h>
(not to say there are no uncool parts of how some entities use it)
<samueldr>
never trust those laser pointers with a cat
<samueldr>
it's highly likely that they are stronger than advertised
<samueldr>
well, maybe not *those*, but any from non-brand sources
<gchristensen>
good point
<__monty__>
If you're talking about eye damage, isn't *any* laser strong enough for that?
<eyJhb>
But samueldr , I need a kitty laser?!
<worldofpeace>
what
<gchristensen>
a laser sold in a shop is probably more carefully regulated than one you get off ali
<worldofpeace>
I don't even know what to expect from something that costs $0.01
<worldofpeace>
that's less than a penny
<cole-h>
*sets of car alarms from 200 feet away*
<cole-h>
s/of/off/
<adisbladis>
As someone who at some point bought a bunch of lasers for roughly $0.01 each at one point: The unit variation is striking
<worldofpeace>
😸
<worldofpeace>
oh goodness, this is aliexpress
<adisbladis>
The only reason I even bought them was because "ohh, cheap lasers"
<worldofpeace>
I've recieved such frightening things from that site
<worldofpeace>
lol so the same as cole-h rn. woah lazers
<adisbladis>
worldofpeace: Now imagine that there is an even shadier site to order this kind of stuff
<adisbladis>
With even less QC
<__monty__>
Wish?
<adisbladis>
Nah, Taobao
<worldofpeace>
u killin me __monty__
<adisbladis>
God I love Taobao
wildtrees has joined #nixos-chat
<adisbladis>
Chinese ecommerce is miles ahead
<worldofpeace>
omg taobao!
<worldofpeace>
I literally got a nose mask from there
<adisbladis>
worldofpeace: I've bought furniture on Taobao :3
<worldofpeace>
me and my friends try to play "guess the price" from there. I always lose
<__monty__>
Isn't taobao in chinese? I wouldn't want to layer google translate on-top of something already shady cheap.
wildtrees has quit [Remote host closed the connection]
<adisbladis>
Basically whatever you buy on aliexpress or wish is probably sourced on taobao ^_^
wildtrees has joined #nixos-chat
<gchristensen>
I'm going to do all my future shopping on taobao via adisbladis
<adisbladis>
lol
<adisbladis>
I used to buy coffee on taobao too
<adisbladis>
Effing Taobao <3
<__monty__>
Hehe, imagining worldofpeace with a mask that covers just the tip of the nose.
<gchristensen>
adisbladis: can you fetch me some cheap hard drives?
<eyJhb>
adisbladis: get out.
<adisbladis>
gchristensen: Brand name stuff is usually not cheaper
<worldofpeace>
__monty__: I saw it and fell in love
<adisbladis>
eyJhb: Ok :(
<gchristensen>
wow a mercedes benz
<worldofpeace>
it's such a look
<eyJhb>
I had a mate buy I think... 10-15 kg of coffee on something like taobao :p
<eyJhb>
He just got a giant bucket of it
<eyJhb>
Tasted like ... the thing that comes after coffee
<worldofpeace>
well damn eyJhb
<samueldr>
on taobao you can likely get cheaper ryzen laptops
<samueldr>
*good* cheaper ryzen laptops
<adisbladis>
The craziest thing I ever bought off there was a group buy with my hackspace, we were like "do you have this wifi adapter but with sma connector" and then they made them custom for us
<gchristensen>
I'll take one, samueldr
<samueldr>
I, too
<gchristensen>
adisbladis: can you find samueldr and I some custom ryzen laptops?
<Valodim>
I wonder, is there a way to call autoPatchelfHook "ad-hoc" like described in that post? e.g. `nix-shell -p gzip autoPatchelfHook --command autoPatchelf ./path/to/binary`?
<makefu>
maybe Mic92 knows, he hinted me towards autopatchelfhook in first place for the wiki entry
<samueldr>
IIRC basically what you said works
<samueldr>
not 100% sure though
<Valodim>
neat
<samueldr>
though it would be --run
<Valodim>
add some nix-locate magic to that mix and even the deps could be found automagically :)
<samueldr>
and the right libraries need to be -p'd
<Valodim>
honestly though nix has such good packaging coverage, and executables that come as elf binaries are rarely in need of binary packaging, I can't recall ever having the need
<__monty__>
Tbh, I don't really like the new RFC. It seems to be pushing to "just accept commonmark as the format." But as domenkozar[m] has said repeatedly it's the *tooling* that actually matters, more than the format.
<__monty__>
And that's kinda swept under the rug "because it's bikeshedding."
<infinisil>
jtojnar: Hehe, nice though
<infinisil>
__monty__: Yeah not a fan of it either
<samueldr>
I hope the messaging in my comments also say that
<samueldr>
I mean, it's fine to select an input format, but selecting the tooling should not be an implementation detail hand-waved away
<samueldr>
it could be another process *that the RFC dictates*
<abathur>
yeah, that rubs me weird too
<abathur>
I mean, I get deciding to just make a blind call and rip the band-aid off to move on to implementation
<samueldr>
ugh, forgot to read the in-line responses, since github's commenting UI is a mess
* samueldr
goes back to the RFC
<jtojnar>
are we actually sure docbook is the problem, and not mostly just the docbook tooling?
<samueldr>
they may be two distinct problems
<infinisil>
I think the right thing to do is to just use Sphinx, and the discussion should be about whether we use ReST with it or some markdown variant
<samueldr>
I'm sure docbook is *a* problem, which is probably less of an issue than the tooling
<jtojnar>
yeah, but from what I have seen of other tooling, it seems to be only slightly better
<infinisil>
I think whether it's better isn't even that important
<infinisil>
Wait no
<infinisil>
It is important
wildtrees has quit [Remote host closed the connection]
<adisbladis>
Docbook tooling is imho not a problem, the XML format is.
<samueldr>
isn't docbook's tooling mainly xml tooling?
<infinisil>
jtojnar: I think we should use Sphinx because it's just so widely used. There might be better tooling, but if it's only used by 1 project then that's not very good either
<adisbladis>
A fair bit is, yes
<infinisil>
jtojnar: We should mainly be concerned about writing docs, not having to figure out problems with the tooling
<adisbladis>
I used to be an advocate for asciidoc, but I've since reached the conclusion that documentation is more of a social problem than a technical one. And since everyone "knows" markdown it's more likely to get people contributing to docs.
<infinisil>
And sphinx is battle tested
<adisbladis>
ReST is yet another format to learn
<abathur>
jtojnar: not that I can speak with authority, but my impression is that the "format" debate mostly boils down to two aspirations: lower the *bar* for writing docs far enough that more people do it, and lower the friction for people who do it anyways
<samueldr>
adisbladis: forgetting the semantically equivalent not-xml, isn't docbook based on xml, so saying that xml is the issue meaning that docbook is also the issue?
<samueldr>
I want to understand your point
wildtrees has joined #nixos-chat
<samueldr>
abathur: pretty much what I understand too
wildtrees has quit [Remote host closed the connection]
wildtrees has joined #nixos-chat
<samueldr>
adisbladis: if your point is asciidoc is docbook without xml, and asciidoc is fine, then I understand
<jtojnar>
infinisil: yes, but looking at the individual tools, I am afraid it does not seem much greener on the other side
<jtojnar>
and we will need to deal with tooling either way
<infinisil>
I at least expect that Sphinx will be relatively smooth
<adisbladis>
samueldr: By extension yes, what I mean is that xsltproc and friends are fine tools but that writing docs in XML format is a terrible endeavour
<samueldr>
adisbladis: I understand
<gchristensen>
xsltproc is not a fine tool
<adisbladis>
=)
<gchristensen>
it is incredibly slow
<samueldr>
(what aborted the attempt at splitting docs in a "modern layout")
<jtojnar>
yeah, the free tooling around XML seems to be stuck at 2000's 😿
<abathur>
this is why I think it might be more helpful (as a decision razor) to be starting from longer-term goals for what people would like to do to or with the docs automagically
<adisbladis>
Anyway, ReST is not sufficiently better than commonmark (with some extensions) to warrant learning another syntax
<gchristensen>
adisbladis: read them :)
<__monty__>
I wouldn't mind markdown if it didn't allow for inline HTML.
<gchristensen>
dangit I promised I wouldn't make jokes or use snark
<gchristensen>
I seriously said that to myself.
<__monty__>
Means you need constant vigilance or to give up on alternative output formats.
<infinisil>
I think commonmark doesn't allow that
<infinisil>
(arbitrary HTML at least, I think there are a small set of HTML elements supported though)
<jtojnar>
infinisil: commonmark specifies how (HTML) tags are to be parsed
<__monty__>
That's the thing about markdown it has a brilliant/cursed escape hatch.
<gchristensen>
can I make one more semi-snark-but-anchored-in-truth statement before I don't say any more?
<infinisil>
Hm though actually, as long as people don't put weird stuff in there, html blocks can just be converted
<infinisil>
html is semantic after all
<gchristensen>
no. I won't.
<jtojnar>
infinisil: it even explicitly mentions Docbook as an example of custom tags
<infinisil>
Neat, yeah so I think even if markdown allows html that should be fine
<abathur>
I agree that markdown is familiar, and commonmark is much better for inline presentational markup than ReST, but presentational markup is just fundamentally a different thing than semantic markup; knowing what you hope to do longer-term helps you figure out if semantic markup is suffering for nothing, or suffering for important goals :]
<jtojnar>
__monty__: we could have a linter, or if we used MDX, we could probably make it not import HTML tags, only custom semantic ones (e.g. for admonitions)
<__monty__>
gchristensen: But we like your sass.
<abathur>
I often feel like restricting the set of valid markup down below what a syntax "allows" is as helpful/important as picking a syntax in the first place
<adisbladis>
gchristensen: Please do
<samueldr>
and y'all, don't forget to voice your opinions that aren't voiced yet on the RFC proper!
<__monty__>
jtojnar: MDX seems interesting but not anywhere near as mature as sphinx?
<jtojnar>
__monty__: that's my reading as well
<samueldr>
I might be wrong, but isn't MDX more of a building block than a "final tool"?
<adisbladis>
An observation from all the docs discussions: One of the weaknesses of this community is that we let perfect be the enemy of good too easily.
<gchristensen>
the good thing about being unable to pick one for any number of reasons (tooling, output formats, etc.) is that it won't matter once nix.dev becomes the defacto choice for docs and nobody looks at our man pages anymore and then they get deleted
<samueldr>
ouch
<gchristensen>
no ouch intended
<samueldr>
I kno
<samueldr>
w*
<gchristensen>
but no choice is a choice
<infinisil>
Nix, one of the few project to have no official documentation
<{^_^}>
nixos-homepage#486 (by edibopp, 3 weeks ago, open): Integrate nix.dev tutorials as a flake
<__monty__>
Nix.dev is domenkozar[m]'s project? And uses reST?
<abathur>
adisbladis: I roughly agree, and if not for the fact that a markdown conversion is likely to involve/encourage throwing out some semantic information that will be hard to recover, I would have kept my mouth shut entirely :]
<adisbladis>
At this point I'm happy if I can rebase the release notes on a long-running PR without it becoming an absolute mess. XML is _horrible_ for this use case.
<gchristensen>
I agree semantic markup is useful, but only if the content is usefully maintained
<abathur>
which isn't to say I'm sure the semantics are actually worth suffering for; just that I haven't seen anyone make the kind of case for their useful-/useless-ness that would make a decision simple
<abathur>
nod
<jtojnar>
are not manuals vaguely the reference, and nix.dev the other three types of docs?
<infinisil>
gchristensen: semantic docbook docs aren't maintained -> switch to markdown -> less-semantic markdown is maintained -> switch to semantic docbook
<gchristensen>
infinisil: even professional documentation writers don't use docbook anymore :)
<__monty__>
Yes, though I'd rather migrate from all the semantics to most of the semantics we'll end up with, rather than having the lowest common denominator as a stop in-between. Information's bound to get lost. So the reluctance of the new RFC to specify the extensions that are to be used worries me.
<gchristensen>
yeah, though I do understand that it might be counter-productive to enshrine the list of extensions in an RFC
<abathur>
I realize this really is the bikeshed, and I said something similar on the old RFC, but I think "docs" is a uselessly big umbrella for the decision
<__monty__>
(LCD is completely the wrong term, sorry.)
<infinisil>
abathur: In rfcs#64 we agreed to only nixpkgs docs
<infinisil>
(that's the nixpkgs repo, meaning nixpkgs and NixOS)
<abathur>
a concise technical reference is different than a guide, tutorials, or a book
<__monty__>
gchristensen: Yes, I wouldn't specify extensions or maybe even tooling. But requirements that'd mean the right extensions would be used.
<abathur>
infinisil: nod, I mostly mean that it feels like the manual is a kitchen-sink of types
<gchristensen>
on the other hand, nixpkgs' technical docs have no chance of being concise
<infinisil>
gchristensen: The fact that there's 100 different ways to do things in nixpkgs doesn't help :P
<gchristensen>
docs will help that problem :) (if one thing works one way, you can lean on patterns which only need to be documented once)
<abathur>
infinisil: if there were a terse API reference, and that API reference had strong semantic information in it, I would probably say there's no *strong* need for additional doc products to bear the same weight, if commonmark is a more efficient way to get them written/maintained
<adisbladis>
No documentation format is good enough - lets make our own!
* adisbladis
runs away and hides
<samueldr>
adisbladis: I did suggest it!
<samueldr>
and it was somehow taken on by someone else
<samueldr>
why not make a bespoke nix-based format!
<gchristensen>
adisbladis: SHUSH.
<infinisil>
Really though, a Nix-based semantic format for writing would enable some cool stuff
<gchristensen>
adisbladis: EELCO WILL HEAR YOU.
<adisbladis>
gchristensen: lol
<abathur>
I was hoping I could write a bespoke bash-based semantic doc EDSL for this
<infinisil>
E.g. you wouldn't have to think about "which syntax do we use to make a reference to this other thing", because we can just import the other thing into scope and code around with it
<samueldr>
abathur: nothing stops you from doing it for your resholved project, proving it works, and TAKE OVER THE WORLD
<abathur>
I kid, but I actually do have a vague desire to write an opinionatedly-small semantic markup language without all of the footguns that come bundled with everything else
<infinisil>
I feel like all markup languages start out about like that :P
<abathur>
and I've had that one pre-nix, mostly growing out of editing some certification guides/textbooks
<gchristensen>
oh yeah abathur might be uniquely qualified here
<abathur>
they do
<adisbladis>
Bash based is flawed from the get go (I'm a bash hater)
<abathur>
I'm 100% kidding :)
<adisbladis>
You never know (:
<abathur>
my itch is that I haven't found a really barebones markup that doesn't come with a bunch of pre-bundled semantics, markdown-wannabe plaintext presentation syntax, and output assumptions to swim against
<__monty__>
abathur: PML, Practical Markup Language comes close imo.
<cole-h>
Let's use rustdoc :^)
<abathur>
and markdownlikes, even including ReST, come with a bunch of nonsemantic presentation crap
<adisbladis>
It's too bad I think my favourite format (org) is not a serious contender
<abathur>
and any time you have to do format conversions, you learn that a documentation corpus with 200 bespoke hand-coded ascii tables that all convey different semantics are a real PITA to massage between formats
<cole-h>
While I like org, I feel like it only makes sense to write it from inside Emacs
<adisbladis>
cole-h: Exactly why I think it's not a serious contender
<samueldr>
it only makes sense where emacs makes sense :^)
<samueldr>
(read from that like you were peering in a mirror of your own biases)
<cole-h>
Pfft, I'm completely impartial
<adisbladis>
I don't know why everyone just can't use emacs :3
<samueldr>
adisbladis: make an emacs-based BPG thingamajig
<samueldr>
BGP*
<samueldr>
and make it run the whole internet
<samueldr>
this way everyone uses emacs
<abathur>
__monty__: nod, PML is one of the ones I've run into
<abathur>
pollen feels like the closest thing I've found, but I haven't found the time to get up on my feet with racket and it would be my first lisp
<abathur>
and my itch is also a little more about something I can imagine normies writing
<cole-h>
No way. My package is finally leaving Kentucky!
<abathur>
and I have a hard time imagining normies writing either PML or pollen
<__monty__>
I could definitely see people writing PML, though I don't like some of its rules. (It kinda goes against its own goals at some points imo.)
<__monty__>
Pollen is very interesting but I'm afraid you might end up with a documentation DSL per project basically.
<abathur>
I guess I have a few specific stick-in-the-mud people in mind
<cole-h>
:P
<__monty__>
Imo anyone who can kinda learn markdown can surely learn PML.
<abathur>
I agree on roughly a DSL per project, though I'd argue that to some degree many projects already do, can, or should have one
<samueldr>
jtojnar: AFAIUI assume the form the generated documents are not final
<samueldr>
the design
<samueldr>
at least that's my understanding
<samueldr>
I find it weird to compare the output the way the RFC does though
<jtojnar>
samueldr: yeah, but that still does not add confidence
<samueldr>
to me it just shows that the default theme sucks
<samueldr>
there are other issues I have had with that specific output
<samueldr>
that are for the tooling discussin (whenever :/)
<samueldr>
discussion*
<abathur>
I guess I'm also not as clear on why it would be a problem for each project to have its own doc DSL as long as the syntax itself lays a stable foundation for that variance
<abathur>
__monty__ ^
<samueldr>
jtojnar: oooh, though I think that specific example shows a lossy markdown conversion
<__monty__>
abathur: Someone said earlier reST was too different from markdown and an extra language to learn and therefore too high a bar for casual doc contributions. A DSL would have exactly the same effect, knowing a language's syntax doesn't really matter you still need to learn about all its functions.
<samueldr>
jtojnar: oh, I assumed it was something else entirely because of your dark github
<samueldr>
jtojnar: yeah, someone didn't use the significant indent it looks like
edefdef is now known as tazjin
<cole-h>
tazjin: Nice nickname :P
<tazjin>
cole-h: need more edef ;_;
<jtojnar>
samueldr: yes, and this is exactly the kind of issues we will begin seeing if we switch to markdown
<samueldr>
yes
<jtojnar>
of course that is a trade-off
<samueldr>
exactly
<samueldr>
and one that is easily understandable with a bit of experience, so hopefully not much of an issue in the end
__monty__ has quit [Quit: leaving]
<abathur>
,tell __monty__ __monty__ I agree it's a potential outcome. But I also imagine a presentational markup aesthetic like "as little as I can get away with", plus a small number of semantic aff
<{^_^}>
abathur: I'll pass that on to __monty__
<abathur>
erg
<abathur>
,tell __monty__ oops; affordances. If you're choosing project-specific semantics, they should line-up with things people already have to learn about your project...