!vVDCbufQqGEdAdfclU:matrix.org

neorg treesitter

574 Members
3 Servers

Load older messages


SenderMessageTime
1 Jan 2024
@_discord_783655191953670214:t2bot.io.vhyrro The parser has been doing it correctly the whole time ;) 16:31:47
@_discord_750666437420384297:t2bot.ioboltless wait, can conflict conflict bold valid output? 16:31:50
@_discord_750666437420384297:t2bot.ioboltless wut 16:31:53
@_discord_783655191953670214:t2bot.io.vhyrro yep 16:31:55
@_discord_783655191953670214:t2bot.io.vhyrro because at one point we had a small discussion to make a syntax amendment that permits bold in bold 16:32:06
@_discord_783655191953670214:t2bot.io.vhyrro and last I checked the parser was doing exactly this the entire time 16:32:39
@_discord_783655191953670214:t2bot.io.vhyrro *bold *what* huh* 16:32:45
@_discord_783655191953670214:t2bot.io.vhyrro this is counterintuitively more parser friendly, at the very least 16:33:03
@_discord_783655191953670214:t2bot.io.vhyrro did I just ruin 20 years of work or 16:33:27
@_discord_750666437420384297:t2bot.ioboltless 16:33:37
@_discord_783655191953670214:t2bot.io.vhyrro It shouldn't be difficult to fix for what it's worth 16:34:05
@_discord_783655191953670214:t2bot.io.vhyrro in my parser implementation I was using an incrementing counter in a hashmap which handled all of the cases 16:34:16
@_discord_783655191953670214:t2bot.io.vhyrro and no matter how the grammar is laid out if the scanner is doing the right thing it should "just work™️' 16:34:31
@_discord_750666437420384297:t2bot.ioboltless yes, that hashmap counting was genius 16:35:06
@_discord_783655191953670214:t2bot.io.vhyrro i can't tell if that was sarcastic 16:35:20
@_discord_750666437420384297:t2bot.ioboltless I mean, really that worked before the _failed_close implement 16:35:52
@_discord_783655191953670214:t2bot.io.vhyrro sounds like it should still work to be fair, as long as they're both in sync (i.e., upon generating a _failed_close you decrement the corresponding entry in the hashmap, or if it's a failed close for all of the attached modifiers in the current paragraph then you could hashmap.clear();) 16:37:24
@_discord_783655191953670214:t2bot.io.vhyrro it might be somewhat tricky to figure out which item you just closed, as you don't have that sort of information in the scanner 16:37:57
@_discord_783655191953670214:t2bot.io.vhyrro perhaps another variable which caches the last opened modifier and which serves as an index into the hashmap? then when you generate a failed_close you look at this variable and decrement the appropriate entry in the hashmap itself 16:38:50
@_discord_750666437420384297:t2bot.ioboltless I was thinking of some kind of stack (deque actually) to cache that information 16:40:14
@_discord_783655191953670214:t2bot.io.vhyrro yeah that could work 16:40:30
@_discord_783655191953670214:t2bot.io.vhyrro ah yeah because you could have many failed_closes 16:40:37
@_discord_750666437420384297:t2bot.ioboltless which (in theory) also allows
*bold *bold*

to be all bold
16:40:39
@_discord_783655191953670214:t2bot.io.vhyrro okay I see 16:40:50
@_discord_750666437420384297:t2bot.ioboltless I’m done for today though, will try implementing both behavior tomorrow. 16:41:50
@_discord_83007807036588032:t2bot.iopurewater Man is carrying 17:03:07
@_discord_434501616176201738:t2bot.iotwonine. joined the room.22:53:56
@_discord_202611455659474944:t2bot.iocr0wsy joined the room.23:34:33
@_discord_387036585033465856:t2bot.ioNTBBloodbath removed their profile picture.23:50:50
2 Jan 2024
@_discord_922261430235975700:t2bot.io_sansk_ joined the room.03:22:49

Show newer messages


Back to Room ListRoom Version: 9