timfeirg
timfeirg
see https://github.com/ms-jpq/coq_nvim/issues/90 and consider closing this issue as duplication
whenever in doubt, pressing `esc` always takes you to normal mode, command line is not where you'd want to spend a lot of time typing and editing, so I think...
I'm also seeing this on 6.2.4.
I usually submit docs update after functionality has been confirmed, I'll work on them now.
I wish to resolve https://github.com/juicedata/juicefs/issues/2504 first, and work on docs for this feature later on, in a separate PR.
failed tests passed without any code change, if things go poorly in the future, remember that current state is able to PASS. working on docs now, no code change will...
code change has been introduced since review, take another look at the follow-up commits? @davies
can I create a separate PR for docs update? review suggestions so far are all concerning release planning & version inconsistency, which won't be an issue if we update docs...
docs part has been moved to https://github.com/juicedata/juicefs/pull/2554
might not be an actual script (and relevant docs), instead I'll try to integrate `--update-fstab` functionality into [mount.go](https://github.com/juicedata/juicefs/blob/main/cmd/mount.go)