<cole-h>
It's certainly an improvement on docbook, IMO x)
<cole-h>
Don't you already have an example block above? Like with the tree dir structure?
<cole-h>
Ah, listing != example
<cole-h>
Because example will label with example or something, right?
<FireFly>
makes sense to use what feels semantically appropriate, and then instruct the tools to render that as you want it, to me
<FireFly>
also, looking at that help you have open, I guess maybe the tree(1) output should be a 'literal' (verbatim output), since it sounds like 'listing, source' specifies being for input rather than output
<FireFly>
(but, I don't really know asciidoc, and either way that might be unnecessarily nitpicky)
<cole-h>
Does adoc have a way to do small snippets of code, e.g. Markdown's backquotes?
<cole-h>
Good, how are you? :)
<Irenes[m]>
I'm okay
<tazjin>
nominal pandemic mood
<Irenes[m]>
got to do a thing though, back later I hope
<MichaelRaskin>
`+variable+` seems to be «monospaced and no formatting»
<Irenes[m]>
this was nice
<cole-h>
MichaelRaskin: You to it just before I did :(
<cole-h>
s/to/got to/
<cole-h>
Note that the backticks is required
<cole-h>
s/is/are/
<cole-h>
Backtick-plus disables formatting
<cole-h>
You can do markdown-like formatting with just backticks, but you can do `asdf *sadf*` which will embolden `sadf`
<cole-h>
Inside the monospace snippet
<MichaelRaskin>
Monospace + no formatting is what I would expect from a code «piece»
<cole-h>
`+ just means `+*asdf*+` will appear as `*asdf*` monospaced
<cole-h>
Whereas `*asdf*` will show up as bold `asdf`
<cole-h>
Btw, a literal block (probably what you want for the tree) is `....` instead of `----`
<cole-h>
Side-by-side of source adoc + output html
<cole-h>
(.... was meant for the tree example)
<cole-h>
:P
<cole-h>
Yep, that's good.
<cole-h>
Would it be worth it to prepend the commands with `$`?
<cole-h>
Fair enough. I guess that's one thing docbook succeeds at: separate the prompt from the actual command
<cole-h>
No big deal, indeed
<cole-h>
`doas cargo build` lol
<cole-h>
Oh hey, kernel finally finished building
<cole-h>
lol
<FireFly>
I think so
<FireFly>
hm
<FireFly>
you might have to search for 'Jonas Höglund', not sure
<MichaelRaskin>
Do we have IRC handles in maintainer list? Maybe we should
<FireFly>
oh, you could also git blame the maintainers list for the FireyFly entry I guess (so-named because github handle)
<cole-h>
That would be nice, tbh. It took me a while to relate you and your GH handle :D
<MichaelRaskin>
Well, technically Firefly would match in the email domain
<FireFly>
oh point
<MichaelRaskin>
And I even have my name in the GH bio!
<FireFly>
lol
<FireFly>
yeah sure, tha might be easier
<FireFly>
that*
<cole-h>
MichaelRaskin: It's true. I just don't hover on GH handles much, and never had a reason to your profile :P
<MichaelRaskin>
It was fun when I did not set display name in email client
* FireFly
waiting for the spectrum-vm build to finish as well
<MichaelRaskin>
Ah, GH _emails_ randomly use handles and names in different places
<FireFly>
...maybe blaming the maintainer list wasn't a great suggestion after all >.< whoops :p
<MichaelRaskin>
What _blaming_ m-l can ever yield??
<MichaelRaskin>
I mean, _searching_ is enough 100% of time, no?
<leah2>
use tig!
<FireFly>
you can use the firefly@ one
<MichaelRaskin>
I am pretty sure I have been a committer for longer than maintainership records exist in files
<cole-h>
`git log --grep='FireyFly'` shows the commit immediately :P
<cole-h>
Maybe you were misspelling it?
<FireFly>
oh yeah
<cole-h>
OK, I must depart. Good luck with the rest of the stream (however long that may be) and thanks for the intro on how to actually run spectrum :D
* FireFly
feels the time taken for finding their email isn't really proportional to the amount of help "looks like .... seems more semantically correct" provided :p
<cole-h>
Cleanup commits are my specialty!
<FireFly>
seeya, cole-h
<FireFly>
\o/
* FireFly
nods
<tazjin>
sleep well :P
<FireFly>
get some rest and get the things you wanted to get done done tomorrow :)
<MichaelRaskin>
Good night.
<qyliss>
Yes :)
<qyliss>
Night!
<leah2>
nini
<cole-h>
Got crosvm to run! Only downside is the keyboard layout is most definitely not qwerty lol
<cole-h>
qyliss: btw the warnings are present on Rust 1.43.0, not 1.42.0. I'll still fix 'em up, though (eventually).
<qyliss>
cole-h: if they're Rust 1.43-specific I wouldn't bother. Google will fix those.
<cole-h>
SGTM. No patches (just yet) for you then ;^)