| FreeBSD | https://people.freebsd.org/~zirias/ |
| C64 scene | https://csdb.dk/scener/?id=25812 |
| Github | https://github.com/Zirias |
@jadi @stefano Just browsing the wiki, I'm
a) surprised there are more services than "just" #mastodon 🤩 (wow!)
b) as a die-hard #IRC fan (nothing beats #irssi in #xterm!!!), a bit disappointed the chat stuff is only available via #matrix 😁
Hehe ... also reminds me to one day revisit my "#libircbot" (designed to write IRC bots in pure #C, actually used for a bot, but far from finished)
@jadi @stefano I might follow your suit. Although I'm tooting about tech stuff in general, and have a second focus on #c64 #coding (#retrocomputing), I really wanted to use a #bsd-related instance at first, but back then, bsd.network never reacted, and bsd.cafe didn't exist yet 🙈 .. so I picked some random other instance looking "tech related".
I wasn't aware there's a "clean migration path" like this, thanks!
@lw If you think it's hard to read, you should probably rather complain about the glyphs in the font ... but then, it does look correct to me.
Also refer to https://en.wikipedia.org/wiki/Bracket#Angle_brackets
In a nutshell, ASCII doesn't have angle brackets, all it has is less/greater-than symbols. They're used to "approximate" angle brackets when all you have is ASCII, but strictly speaking, they're wrong.
@lw Quoting mdoc(7):
---
Since Aq usually renders with non-ASCII characters in non-ASCII
output modes, do not use it where the ASCII characters ‘<’ and ‘>’
are required as syntax elements. Instead, use these characters
directly in such cases, combining them with the macros Pf, Ns, or Eo
as needed.
---
Manpages were never meant to produce "pure ASCII" (unless that's a restriction of the output device), not even to use monospaced fonts by default. Their origin is a macro package for the roff typesetting system. There have always been macros to produce enclosures (like quotes and brackets) and they always produced "typographic output" when possible.
btw, you can of course always force pure-ASCII output:
LANG=C man rc.conf
@paoloredaelli I think it's pretty much pointless anyways. 🤷
Doesn't mean I'm against doing it, but I *do* think the time this will take could also be invested in things giving a lot more benefit. After all, there is quite some complexity attached to it, starting with integrating #Xorg into the #FreeBSD installation process *without* making it a part of base (which I think nobody wants to do, at least I hope so 🙃). I mean, that's a lot to do for the sole benefit to have something that "looks more modern" or whatever. It's not like it will add any *features* to the installer, just a different UI.
@lobocode @meena NP. You could now even get creative and e.g. add testcases (rc.conf files with different errors) in '.github' and script in the yaml file to check for the expected output or whatever.
But OTOH, I wouldn't invest TOO much work here either, because this part is strictly tied to github and services *they* offer (while a git repository itself is completely independent from where it is hosted).
@lobocode @meena Found another issue and created yet another PR for it:
https://github.com/scovl/checkrc/pull/7
Background is explained there, in a nutshell, avoid setting -Werror in the default CFLAGS (distributed to users), it has the potential to just break builds...
Instead take advantage of github's infrastructure and have a CI build run automatically on pushes and pull requests that *does* use -Werror.
@meena @lobocode Yeah, there's a comment somewhere in #FreeBSD's make framework, bsd.sys.mk:
# -pedantic is problematic because it also imposes namespace restrictions
#CFLAGS+= -pedantic
Not sure what kind of namespaces they mean, maybe related to feature flags?
edit: I *do* have it in my default CFLAGS (in my own gmake framework) and never ran into issues so far, just wanted to mention it.
