-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strange behavior from 'n' and 'p' keys when near collapsed threads #7
Comments
I confirm. I'm navigating with up/down arrows which work fine s maybe the native binding for n/p is different. I suspect make you point on an hidden child and this might be the reason. |
I think the one issue I'm having is probably the same one as this: if I navigate in headers view to a folded thread (say by arrows keys or mouse click) and view the first message in the folded thread (without unfolding), then pressing =n= moves me to the next message in the next in the =Article= buffer but the indicator from the =mu4e-headers= buffer just disappears. Would there be a way of having navigation beyond the first message of a folded thread automatically trigger the unfolding of that thread? |
That might be doable. If you look at the toggle-at-point code, I think you can probably adapt it. |
I noticed the same scrolling issue as described in the first post, using the
|
Do you what the difference between the |
From the documentation, it seems that
|
Thanks. Skipping hidden lines make sense. I need to implement this (or just copy the code from |
Navigating the header view with 'n' and 'p' no longer works perfectly.
'n' moves right 1 when 1 line below a ">".
'p' from below a ">" moves to end of line with ">"
The text was updated successfully, but these errors were encountered: