!vVDCbufQqGEdAdfclU:matrix.org

neorg treesitter

574 Members
2 Servers

Load older messages


SenderMessageTime
8 Jan 2024
@_discord_845674119391477820:t2bot.io_gilfoyle_ .vhyrro is this man trolling 15:00:29
@_discord_783655191953670214:t2bot.io.vhyrro no he fr 15:00:42
@_discord_783655191953670214:t2bot.io.vhyrro he just mad like that 15:00:48
@_discord_783655191953670214:t2bot.io.vhyrro ah that's such an annoying edge case 15:00:54
@_discord_783655191953670214:t2bot.io.vhyrro we should probably completely rethink verbatim modifiers altogether i think 15:01:06
@_discord_750666437420384297:t2bot.ioboltless btw this is all done by a little bit complicated external scanner, but at least one man in the universe knows how it works
I hope he doesn’t forget about this
15:02:35
@_discord_783655191953670214:t2bot.io.vhyrro "a little bit" 15:02:53
@_discord_783655191953670214:t2bot.io.vhyrro it works though that's the most important 15:03:04
@_discord_750666437420384297:t2bot.ioboltlessRedacted or Malformed Event15:39:22
@_discord_783655191953670214:t2bot.io.vhyrro bro changed his mind before I had time to read it 15:39:41
@_discord_750666437420384297:t2bot.ioboltless wait a min I was writing 15:39:53
@_discord_783655191953670214:t2bot.io.vhyrro we could give verbatims etc. the same precedence level as links 15:39:54
@_discord_783655191953670214:t2bot.io.vhyrro and then LTR sounds good 15:39:57
@_discord_750666437420384297:t2bot.ioboltless I think current behavior seems reasonable
LTR (but verbatim has higher precedence than linkables, so any link closer won’t work before verbatim is closed)
{* heading `Object {}`} <- ends on second }
[heading `Array []`] <- ends on second ]

generally users won’t want these to break

{* heading mentioning *}*} <- ends on first }
[mentioning *]*] <- ends on first ]

these will break linkables and client like nvim-neorg or neorg-ls should warn user to change it to \} and \]
{* heading mentioning *|}|*} <- ends on second }
[mentioning *|]|*] <- ends on second ]

but free-form linkables won’t break the linkables because they must be closed, so user don’t have to change those to escape sequence
15:43:27
@_discord_750666437420384297:t2bot.ioboltless can confirm all of these are current parser behavior 15:45:42
@_discord_750666437420384297:t2bot.ioboltless .vhyrro cc 15:46:41
@_discord_521906768779935752:t2bot.iorhaskia does anyone have a version of this compiled to wasm? it keeps complaining docker or emcc is not on my PATH whenever I try to compile it 19:00:58
@_discord_1061401373968703558:t2bot.iopyxodan removed their profile picture.22:44:45
@_discord_284994674262016012:t2bot.iolarry_guy joined the room.22:47:48
9 Jan 2024
@_discord_1189759514744979477:t2bot.iophenomenal_possum_18890 joined the room.00:06:53
@_discord_186483831547756544:t2bot.io.isaacs joined the room.06:30:19
@_discord_750666437420384297:t2bot.ioboltless .vhyrro can I just get write access to v3 repo?
current draft PR state is fine, but I think it would be better if I can open issues about PR branch in official v3 repo (like test case todo for contributions)
10:36:43
@_discord_783655191953670214:t2bot.io.vhyrro yessir hold on 10:36:54
@_discord_783655191953670214:t2bot.io.vhyrro haven't tried compiling to wasm yet so no not really 10:37:10
@_discord_783655191953670214:t2bot.io.vhyrro https://github.com/nvim-neorg/tree-sitter-norg3/invitations boltless 10:38:26
@_discord_708254240539410472:t2bot.iomt.moon_daniel joined the room.17:50:54
10 Jan 2024
@_discord_354159856284073984:t2bot.iojakelarkin joined the room.06:18:22
@_discord_1120438957935693914:t2bot.iojotrorox joined the room.10:29:34
@_discord_651460971084251136:t2bot.iojomaweb joined the room.21:29:52
@_discord_564092270127874048:t2bot.io.viperx7 joined the room.21:56:14

Show newer messages


Back to Room ListRoom Version: 9