Google+ Checkvist community posts 2013-2018

I poked around a bit but didn't find this discussed (which of course doesn't mean it hasn't been done): Why does 'un-hoisting/focusing' result in the list returning focus to the root level of the list (albeit, with the branch I had just had hoisted)? In the attached images, #1 shows the fully expanded list, #2 hoists Root_item_1, #3 hoists sub_item_1, and #4 unhoists sub_item_1. Notice that the focus has return to the root level. It seems far more intuitive to me that if I press 'shift-right arrow' to focus that sublist, then 'shift-left arrow' should return the focus to the previous state. Was this a deliberate design decision, and if so, what was the rationale behind it? I like to keep the focus well below the root level in order to keep things neat and uncluttered, and I find this hoisting logic a bit disruptive since it basically forces me back to root.

Love checkvist! Thank you so much for creating it. I appreciate the j/k movement keys, but I would love it if I had h/l (and H/L to substitute for shift-left/shift-right) as then I could dispense with the arrow keys altogether. Any possibility of a vim-mode setting where: - hkjl as movement keys - H/L are the equivalent of shift-left/shift-right - gg jumps to top of list (current gg behavior to :e/:vs (new tab) perhaps ) - G jumps to bottom - ctrl-u does what page up currently does - ctrl-d does what page down current does - u is undo - yy to cut - pp to paste If the ability to remap shortcuts were available, I would absolutely do it myself. Would be happy to help if there were any way for me to do so. Thanks again for an awesome product!