You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When there are branchs which only exists in local, GinBranch throws error like this.
Error detected while processing function denops#request[1]..denops#server#request[6]..<SNR>53_request:
line 1:
Error invoking 'invoke' on channel 4:
Error: Failed to call 'branch:read' with []: Error: Failed to parse 'git branch' record ' ddc 123fa8e update'
at file:///home/denjo/.cache/dein/repos/github.com/lambdalisue/gin.vim/denops/gin/feat/branch/parser.ts:92:11
at Array.map (<anonymous>)
at parse (file:///home/denjo/.cache/dein/repos/github.com/lambdalisue/gin.vim/denops/gin/feat/branch/parser.ts:55:38)
at read (file:///home/denjo/.cache/dein/repos/github.com/lambdalisue/gin.vim/denops/gin/feat/branch/command.ts:84:18)
at async Session.dispatch (https://deno.land/x/msgpack_rpc@v3.1.4/session.ts:99:12)
at async https://deno.land/x/msgpack_rpc@v3.1.4/session.ts:108:18
at async Session.handleRequest (https://deno.land/x/msgpack_rpc@v3.1.4/session.ts:104:29)
at Session.call (https://deno.land/x/msgpack_rpc@v3.1.4/session.ts:207:13)
at async Service.dispatch (file:///home/denjo/.cache/dein/.cache/init.vim/.dein/denops/@denops-private/service.ts:101:14)
at async Session.invoke (file:///home/denjo/.cache/dein/.cache/init.vim/.dein/denops/@denops-private/host/nvim.ts:48:16)
at async Session.dispatch (https://deno.land/x/msgpack_rpc@v3.1.4/session.ts:99:12)
at async https://deno.land/x/msgpack_rpc@v3.1.4/session.ts:108:18
at async Session.handleRequest (https://deno.land/x/msgpack_rpc@v3.1.4/session.ts:104:29)
It seems that this pattern doesn't match with the output of git branch --list -vv, which shows the result like ddc 123fa8e update.
The text was updated successfully, but these errors were encountered:
When there are branchs which only exists in local,
GinBranch
throws error like this.It seems that this pattern doesn't match with the output of
git branch --list -vv
, which shows the result likeddc 123fa8e update
.The text was updated successfully, but these errors were encountered: