{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":759262590,"defaultBranch":"main","name":"LazyVim","ownerLogin":"mbhutton","currentUserCanPush":false,"isFork":true,"isEmpty":false,"createdAt":"2024-02-18T05:01:24.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/63345?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1708232608.0","currentOid":""},"activityList":{"items":[{"before":"a50f92f7550fb6e9f21c0852e6cb190e6fcd50f5","after":"91126b9896bebcea9a21bce43be4e613e7607164","ref":"refs/heads/main","pushedAt":"2024-02-22T19:56:33.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"mbhutton","name":null,"path":"/mbhutton","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/63345?s=80&v=4"},"commit":{"message":"chore(build): auto-generate vimdoc","shortMessageHtmlLink":"chore(build): auto-generate vimdoc"}},{"before":"b875a2d01272f7e3d6a595a21d7760a5a90e9d25","after":"dec4cabb7575bf7f2a7cb2fa667a7b4def68939e","ref":"refs/heads/fix-vscode-timeoutlen","pushedAt":"2024-02-18T05:36:49.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"mbhutton","name":null,"path":"/mbhutton","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/63345?s=80&v=4"},"commit":{"message":"fix(options): don't lower timeoutlen when in VS Code\n\nAvoid lowering timeoutlen when running in VS Code, to avoid\nunwanted timeouts from key mappings.\n\nThe lower value of 300ms (down from Neovim's default of 1000ms)\nworks great outside of VS Code, where it helps trigger the which-key UI\nquickly, and where which-key prevents timeouts from occuring.\n\nBut in VS Code (where which-key isn't applicable), the lower value\nmakes it difficult to perform some key mappings in time,\nsuch as `]p`, which requires shifting hand position.","shortMessageHtmlLink":"fix(options): don't lower timeoutlen when in VS Code"}},{"before":"a50f92f7550fb6e9f21c0852e6cb190e6fcd50f5","after":"b875a2d01272f7e3d6a595a21d7760a5a90e9d25","ref":"refs/heads/fix-vscode-timeoutlen","pushedAt":"2024-02-18T05:32:25.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"mbhutton","name":null,"path":"/mbhutton","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/63345?s=80&v=4"},"commit":{"message":"fix(options): don't lower timeoutlen when in VS Code\n\nAvoid lowering timeoutlen when running in VS Code, to avoid\nunwanted timeouts from key mappings.\n\nThe lower value of 300ms (down from Neovim's default of 1000ms)\nworks great outside of VS Code, where it helps trigger the which-key UI\nquickly, and where which-key prevents timeouts from occuring.\n\nBut in VS Code (where which-key isn't applicable), the lower value\nmakes it difficult to perform some key mappings in time,\nsuch as `[p`, which requires shifting hand position.","shortMessageHtmlLink":"fix(options): don't lower timeoutlen when in VS Code"}},{"before":null,"after":"a50f92f7550fb6e9f21c0852e6cb190e6fcd50f5","ref":"refs/heads/fix-vscode-timeoutlen","pushedAt":"2024-02-18T05:03:28.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"mbhutton","name":null,"path":"/mbhutton","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/63345?s=80&v=4"},"commit":{"message":"chore(build): auto-generate vimdoc","shortMessageHtmlLink":"chore(build): auto-generate vimdoc"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEAmWyHQA","startCursor":null,"endCursor":null}},"title":"Activity · mbhutton/LazyVim"}