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
Hi! First of all, thank you so much for this extension. Is SUPER useful and I love it.
I like a lot the navigation feature with ALT+PageUp/Down, but I have noticed that it places the caret at the end of the comment.
This is not a problem if you are working in a big monitor and/or your workspace view is now split into diferent columns with different files.
But if your view is splitted, is quite uncomfortable to place the caret at the end of the comment, since your (horizontal) view of the code changes (to the end of the comment), and you have to scroll back at the end of the line to have a "normal view".
To avoid that, you have to remember that you should not write long comments in the same line of an anchor if you want to use the navigation shortcut.
IMHO, a better approach would be:
A) Putting the cursor at the start of the anchor/line
B) Putting the cursor in the same column (if possible) that it was previously to pressing the shortcut, so the horizontal scroll/view of the code is not altered.
Is just a humble idea that I think it will make the navigation better!
Again, thanks again for this awesome extension!
The text was updated successfully, but these errors were encountered:
Hi! First of all, thank you so much for this extension. Is SUPER useful and I love it.
I like a lot the navigation feature with ALT+PageUp/Down, but I have noticed that it places the caret at the end of the comment.
This is not a problem if you are working in a big monitor and/or your workspace view is now split into diferent columns with different files.
But if your view is splitted, is quite uncomfortable to place the caret at the end of the comment, since your (horizontal) view of the code changes (to the end of the comment), and you have to scroll back at the end of the line to have a "normal view".
To avoid that, you have to remember that you should not write long comments in the same line of an anchor if you want to use the navigation shortcut.
IMHO, a better approach would be:
A) Putting the cursor at the start of the anchor/line
B) Putting the cursor in the same column (if possible) that it was previously to pressing the shortcut, so the horizontal scroll/view of the code is not altered.
Is just a humble idea that I think it will make the navigation better!
Again, thanks again for this awesome extension!
The text was updated successfully, but these errors were encountered: