|
Documentation Channel for #raku | This channel is logged | Roadmap: github.com/raku/doc/wiki Set by [Coke] on 23 May 2022. |
|||
|
07:39
sena_kun joined
12:43
Altai-man joined,
sena_kun left
16:15
Altai-man left
16:17
sena_kun joined
16:35
raiph joined
16:41
sena_kun left,
sena_kun joined
17:32
raiph left
|
|||
| [Coke] | anyone see any issues if a .rakudoc extension implied the --doc command line arg? | 18:12 | |
| (currently it treats it like .raku and runs the code) | 18:13 | ||
| Voldenet | maybe you could make extensions map configurable via env vars | 18:15 | |
| lizmat | Voldenet: OOC what other extension -> functionality mapping do you have in mind? | 18:16 | |
| Voldenet | RAKUDO_FILE_EXTENSIONS=raku:code,rakudoc:doc,rakumod:mod,p6:code,pod6:doc,pm6:mod | ||
| something likee that perhaps | 18:17 | ||
| lizmat | what different functionality would mod have ? | ||
| from code I mean | |||
| Voldenet | theoretically it would indicate a module, I didn't think this too much though | 18:18 | |
| s/think this/think this through/ | |||
| RAKUDO_FILE_EXTENSIONS=rakudoc:doc,pod6:doc,*:code | 18:19 | ||
| I doubt anyone would ever need to change this either way | |||
| [Coke] | I wouldn't want to make this an env var. | 18:22 | |
| lizmat | I think hardcoding .rakudoc --> --doc for now, would give us ample feedback | ||
| [Coke] | envisioning someone turning on code execution when you weren't expecting it. | 18:23 | |
| Voldenet | I don't feel strongly about that – env var can be added when someone needs it (which is never) | 18:44 | |
|
19:01
sena_kun left
19:04
sena_kun joined
21:41
sena_kun left
|
|||