Time Nick Message 00:32 MTDiscord adding these as snippets is really helpful: json "Frameless Table": { "prefix": ["ftable"], "body": [ "[%autowidth, frame=none]", "|===", "${1:body}", "|===", ] }, "Function Row": { "prefix": ["frow"], "body": [ "| ${1:name} | ${2:type} | ${3:description}", ] }, 00:32 MTDiscord snippets? 00:32 MTDiscord VsCode snippets 00:32 MTDiscord ah 00:32 MTDiscord should still be macrod 00:33 MTDiscord We'll get there, eventually 02:35 MTDiscord Excellent idea. The technical term for the URL "macros" is attributes; perhaps we should use that to stay consistent with the asciidoc documentation. 02:37 MTDiscord Attributes are specific settings, macros are technically things like xref[] and link[], and substitutions are called..well, substitutions iirc 02:37 MTDiscord iirc anyways 13:49 MTDiscord @Benbob0329 resolved everything, except for https://github.com/minetest/minetest_docs/pull/28#discussion_r785184378. I believe it should be mentioned there for the sake of completeness; obviously I don't consider this proper entity documentation. I wouldn't mark entity:on_step as documented after merging this PR. 15:16 MTDiscord I'll take a look in a little while 18:42 MTDiscord @Luatic Reviewed timing PR 19:30 MTDiscord @Benbob0329 why all the macros? 19:31 MTDiscord Because that's in the template, because it's provides links to them for quick reference 19:32 MTDiscord class types also get macros (like vector) 19:32 MTDiscord not a fan of integer -> number though 19:33 MTDiscord It's a number lua-side, thats what people will see if they check the type 19:34 MTDiscord Hmm, I agree that knowing what kind of number is helpful, but knowing what type an argument/return is is also helpful 19:35 MTDiscord Maybe we should separate these concepts 19:36 MTDiscord for example: vector.new returns a variable of type "table", which is of the "vector" class kind 19:36 MTDiscord "kind" probably isn't the best word, but I'm not sure what would be better off the top of my head 19:45 MTDiscord I dont want superfluous information 19:45 MTDiscord Having to cram two things into types is a no from me 19:45 MTDiscord knowing that something is a whole number vs a decimal is useful 19:46 MTDiscord That should be described in prose 19:58 MTDiscord Pretty much perfect analogy IMO 19:59 MTDiscord anology* 23:02 MTDiscord I absolutely do not want 2 values for types 23:02 MTDiscord so either figure out a way to represent it in one word or describe it elsewhere