`[m]control_menu(up)` and `down` interact badly with ToC heirachies

[tennysontbardwell]

Environment

• MacOS 14.5
• Macbook M1 Air
• The arm version of sioyek3-alpha0
• Config files
  • Specifically:

    [m]control_menu(up) <C-p>
    [m]control_menu(down) <C-n>

Observed behavior

• Opened The Matrix Cookbook (doc)[1]
• Scroll to page 17
• Typed t to open the table of contents
  • behaves as expected
  • 
• Typed <C-n> to go down the table of contents
  • Does NOT behave as expected. Menu focuses on the parent heading in the table of contents.
  • 
• Typed <C-n> to go down the table of contents
  • Does NOT behave as expected. Menu focuses on the next top-level-heading in the table of contents.
  • 
• Typed <C-n> <C-n> <C-n> to go down the table of contents 3 times
  • Does NOT behave as expected. Each time, menu focuses on the next top-level-heading in the table of contents.
  • 
• Typed tab to go down the table of contents
  • behaves as expected
  • 
• Typed <C-n> to go down the table of contents
  • Does NOT behave as expected. Menu focuses on a top-level-heading very far away from the current selection
  • 

Expected Behavior

• [m]control_menu(up) <C-p> behaves similar to "shift tab" or <up>
• [m]control_menu(down) <C-n> behaves similar to <tab> or <down>

Other thoughts

It seems as though the current development branch does not have any better item than [m]control_menu(up) (codelink)

[1] md5sum f26b052726b6dd92907c402c35a92131, sha256 93da5e376fbc106ec92fbb9c59174298b6c3be8f6ad0295d805e94b8d5e76667

[tennysontbardwell]

Even if it was desired that [m]control_menu(up) works on the top-level ToC items, the final screenshot is (as far as I can tell) a nonsensical result.

Obligatory: thank you for producing and maintaining sioyek.

[ahrm]

Should be fixed in https://github.com/ahrm/sioyek/commit/d448ea962494cd2295669209320b667665314dc8.

[tennysontbardwell]

Thank you very much! I have not gotten a chance to build development, but I will optimistically close this.