| Time |
Nick |
Message |
| 04:00 |
|
MTDiscord joined #minetest-docs |
| 05:01 |
|
MTDiscord joined #minetest-docs |
| 05:03 |
|
[0] joined #minetest-docs |
| 05:03 |
|
MTDiscord1 joined #minetest-docs |
| 05:10 |
|
MTDiscord joined #minetest-docs |
| 05:10 |
|
[0] joined #minetest-docs |
| 05:10 |
|
settl3r[m] joined #minetest-docs |
| 05:10 |
|
MrDraxs[m] joined #minetest-docs |
| 05:10 |
|
settl3r[m] joined #minetest-docs |
| 05:11 |
|
MrDraxs[m] joined #minetest-docs |
| 05:13 |
|
wsor joined #minetest-docs |
| 05:13 |
|
BuckarooBanzai joined #minetest-docs |
| 06:23 |
|
settl3r[m] joined #minetest-docs |
| 07:10 |
|
schwarzwald[m] joined #minetest-docs |
| 07:20 |
|
appguru joined #minetest-docs |
| 07:23 |
|
MrDraxs[m] joined #minetest-docs |
| 08:17 |
|
MTDiscord2 joined #minetest-docs |
| 12:34 |
|
appguru joined #minetest-docs |
| 13:04 |
MTDiscord |
<exe_virus> I hope we end up being both a reference, and a how to, but that's just me |
| 13:38 |
|
appguru joined #minetest-docs |
| 13:43 |
MTDiscord |
<exe_virus> Adoc is good in theory, but the syntax is not that professional yet, basically it needs reworked and designed so that the syntax is cleaner and less verbose, but all the functionality desired is there at least, unlike markdown which has the opposite problem |
| 13:46 |
MTDiscord |
<Benrob0329> To be honest, calling a long established syntax "Not professional yet" sounds like "I don't like it so I'll call it bad" |
| 13:48 |
MTDiscord |
<Benrob0329> The project started in 2002. People have used it to write books. I'm also using it to write a book. It's plenty professional. |
| 14:05 |
MTDiscord |
<Benrob0329> Just as a guess, I wonder if [source]#Myfoo()# would work |
| 14:06 |
MTDiscord |
<luatic> I went with `+stuff+` in the end |
| 14:06 |
MTDiscord |
<luatic> perhaps it's more suited for books than docs tho? |
| 14:07 |
MTDiscord |
<Benrob0329> That..that doesn't make any sense. Books are neither docs nor non docs |
| 14:09 |
MTDiscord |
<Benrob0329> We probably need a couple custom macros to make writing these easier, but we've known that for a while. I could probably use some in my personal writing projects as well but I'm lazy |
| 14:10 |
MTDiscord |
<luatic> granted, I phrased that poorly |
| 14:10 |
MTDiscord |
<luatic> books are independent of content which may be documentation |
| 14:11 |
MTDiscord |
<luatic> let's just say literature/prose |
| 14:11 |
MTDiscord |
<Benrob0329> That may be true, but the entire Asciidoc reference is written in asciidoc |
| 15:35 |
MTDiscord |
<exe_virus> Something can be used forever and have a great feature set, but still have a bad interface |
| 15:35 |
MTDiscord |
<exe_virus> Examples include: the damn C preprocessor "language" |
| 15:41 |
MTDiscord |
<exe_virus> Nah, I'd say a good example might be something like directX |
| 15:41 |
MTDiscord |
<exe_virus> Or win32 api |
| 16:30 |
MTDiscord |
<MarkTheSmeagol> Given that the C preprocessor is Turing complete, I don't think you need those quotes around the word language. |
| 17:34 |
|
appguru joined #minetest-docs |
| 18:38 |
|
appguru joined #minetest-docs |
| 20:13 |
|
appguru joined #minetest-docs |
