IRC logs of Freenode #BZFlag for Friday, 2019-08-16

*** infobot <infobot!ibot@c-174-52-60-165.hsd1.ut.comcast.net> has quit IRC (Remote host closed the connection)00:15
*** infobot <infobot!ibot@c-174-52-60-165.hsd1.ut.comcast.net> has joined #bzflag00:16
*** ChanServ sets mode: +v infobot00:16
kierra~Delusional++00:39
*** spldart <spldart!~james@bzflag/contributor/spldart> has quit IRC (Quit: Leaving)00:55
*** Sgeo__ <Sgeo__!~Sgeo@ool-18b98455.dyn.optonline.net> has joined #bzflag01:38
*** Sgeo_ <Sgeo_!~Sgeo@ool-18b98455.dyn.optonline.net> has quit IRC (Ping timeout: 246 seconds)01:41
*** Zehra <Zehra!~Zehra@unaffiliated/zehra> has quit IRC (Quit: Gone for now.)01:55
*** Sgeo__ <Sgeo__!~Sgeo@ool-18b98455.dyn.optonline.net> has quit IRC (Read error: Connection reset by peer)02:37
Flashblast007: nothing in markdown inherently supports images, any more than HTML does. The point of markdown is to have a human-readable plain text format that can also be rendered nicer02:37
blast007https://daringfireball.net/projects/markdown/syntax#img02:40
Flashyes, as I said, not any more than HTML does02:41
blast007whatever.  I don't understand your point.02:41
Flashto me, that would never the a primary motivation for markdown02:41
blast007it certainly is a big use for it on Github02:42
Flashblast007: I don't think moving to markdown really adds much for our readme file02:42
Flashblast007: we're not gonna have any images, for instance02:42
blast007have you not seen tons of repos with badges?02:42
blast007"for instance"02:42
FlashGithub is a good example of why our READMEs *should* be in markdown02:43
blast007not really02:43
Flashwe can agree to disagree then.02:43
blast007sure02:43
*** Sgeo <Sgeo!~Sgeo@ool-18b98455.dyn.optonline.net> has joined #bzflag02:43
FlashI didn't understand your statement as you made it. Now I do. Thanks for the clarification02:44
blast007mainly, the original PR that moved it to markdown was basically just doing it to do it02:45
blast007it didn't really *add* anything02:45
Flashpersonally, I don't see any harm in adding the MD formatting to our files02:45
FlashI'm not sure why the PR was discouraged02:45
blast007because it would affect a bunch of other systems that parse or copy the files02:47
blast007and for what - some bold text?02:48
blast007it looks worse when just reading the files in a text editor02:48
blast007trying to figure out what dependencies to install on linux to build the code, and now it's wrapped in a ```sh ... ```02:49
Flashthat's bad02:50
blast007welcome to markdown :)02:50
Flashoh, you mean the MD wrapping02:50
blast007yeah02:50
blast007it's a syntax for generating HTML, not really for viewing it as the markdown syntax itself02:50
Flashpersonal preference, I guess. That's explicit code to me02:50
Flashthere's also the 4-space literal indent that is perfectly human readable02:51
blast007just makes things less clear for people who are not aware of the markdown syntax02:51
Flashthe only value in ```sh ... ``` is syntax highlighting.02:52
blast007with markdown, we tell them to execute:  `make install`02:52
blast007but they'd have to know to not include the `02:52
Flashon the other hand, a markdown renderer makes it perfectly clear where the verbiage and the command are02:53
blast007so we can't use images, we can't use syntax highlighting - so what, we're left with bold text and headers?  and links?02:53
Flash"we can't"?02:53
blast007"the only value in.." makes it sound like you don't think it should be used02:53
FlashI'm saying there is an alternate syntax that is perfectly human readable. The ``` syntax adds syntax highlighting, if the renderer supports it, but less so as a human renderer02:54
allejoI'm personally for markdown. markdown has become standardized and common enough that people should know what it is. and if they don't know what it is, they read it easily on github and get benefits like syntax highlighting and linkable headings02:55
FlashI use it in all my work READMEs, and I don't even have a renderer02:56
blast007if we did, I'd not want it to affect nearly as many files as what that PR did02:56
blast007the readme? maybe.  the rest, meh02:56
FlashChangeLog is one I wouldn't change, but the other 16 are READMEs03:00
Flashmaybe a case could be made for NEWS03:01
allejoI'd be ok with the changelog being markdown. plain text wise, it wouldn't be much difference. however on github, we'd get links to each release03:06
*** brad <brad!~brad@unaffiliated/brad> has quit IRC (Ping timeout: 272 seconds)03:22
*** brad <brad!~brad@37.187.113.104> has joined #bzflag03:23
*** brad <brad!~brad@37.187.113.104> has quit IRC (Changing host)03:23
*** brad <brad!~brad@unaffiliated/brad> has joined #bzflag03:23
macsformeI think markdown makes more sense if we rewrite our README with that format in mind, and distill the information down to be more concise05:05
macsformeI wouldn't just convert what we have straight over to markdown05:06
*** Sgeo <Sgeo!~Sgeo@ool-18b98455.dyn.optonline.net> has quit IRC (Ping timeout: 245 seconds)06:54
*** Sgeo <Sgeo!~Sgeo@ool-18b98455.dyn.optonline.net> has joined #bzflag09:01
blast007macsforme: yeah, I'd agree with that.  for me, the PR didn't really do enough to justify the changeover.10:57
*** Sgeo_ <Sgeo_!~Sgeo@ool-18b98455.dyn.optonline.net> has joined #bzflag16:12
*** Sgeo <Sgeo!~Sgeo@ool-18b98455.dyn.optonline.net> has quit IRC (Ping timeout: 248 seconds)16:14
*** Sgeo_ <Sgeo_!~Sgeo@ool-18b98455.dyn.optonline.net> has quit IRC (Ping timeout: 244 seconds)16:43
*** spldart <spldart!~james@bzflag/contributor/spldart> has joined #bzflag21:52
*** ChanServ sets mode: +v spldart21:52
*** I_Died_Once <I_Died_Once!~I_Died_On@unaffiliated/idiedonce/x-1828535> has quit IRC (Read error: Connection reset by peer)22:12
*** Zehra <Zehra!~Zehra@unaffiliated/zehra> has joined #bzflag22:33

Generated by irclog2html.py 2.17.3.dev0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!