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
One trouble which bugged me most when using godev, was that when I jumped from file to file (e.g. "jump to definition", or searching for some function name, etc), especially just for a moment, which I do quite much, then after coming back to the original file, each time I had to scroll again from the beginning and hunt for the position where I was last editing.
In this workflow, there's also trouble with having to save the file each time, even if the changes are just "in progress" and not worth saving; but IIRC, I worked around this by enabling autosave feature.
One possible solution I imagine to fix annoyances in my workflow would be if there was a "Navigate Back/Navigate Forward" feature like in the desktop Eclipse IDE.
Other one that could mostly solve my problem would be if there was "bookmarks" feature and keyboard shortcut, for marking lines in files and quickly jumping between them ("next"/"previous"-style); disadvantages here are: that it requires interaction and thus can be accidentally forgotten; also that it is often some line near editing place which is marked (since previous jumps - I know that from using such feature in other editors), and thus requires some movement keystrokes after jumping back to reposition on correct line. There's however an advantage too, that it is more permanent than "Navigate back/forward" and allows for marking more important navigation points.
One more partial solution which would often mitigate the problem would be if multiple files could be opened at once (with position remembered), or even if it was that just the position in each filename was remembered. This would help when jumping between files, but would not when jumping inside a single big file, or when jumping to other file later led back to jumping to other function in original file.
I'd be very grateful if some feature to mitigate my problems was implemented in godev, it would much improve my workflow with it! It's been my main pain point when I last tried. That said, the tool is very impressive already, and balancing near the edge of becoming my favourite for Go development. Big thanks!
The text was updated successfully, but these errors were encountered:
Thank you for taking the time to raise this. There are some good points and ideas here.
One way that I have personally gotten around this problem is to Ctrl-Click on the links in the GoDev dialogs to force them to open in another browser window. I know that not everyone likes to expand into multiple browser tabs but it seems to work fairly well for me except when I'm navigating within the same file.
I will give your ideas some thought and see if there's something that I can do.
One trouble which bugged me most when using godev, was that when I jumped from file to file (e.g. "jump to definition", or searching for some function name, etc), especially just for a moment, which I do quite much, then after coming back to the original file, each time I had to scroll again from the beginning and hunt for the position where I was last editing.
In this workflow, there's also trouble with having to save the file each time, even if the changes are just "in progress" and not worth saving; but IIRC, I worked around this by enabling autosave feature.
I'd be very grateful if some feature to mitigate my problems was implemented in godev, it would much improve my workflow with it! It's been my main pain point when I last tried. That said, the tool is very impressive already, and balancing near the edge of becoming my favourite for Go development. Big thanks!
The text was updated successfully, but these errors were encountered: