Is there any IDE that allows you to jump through a stack trace like emacs does?
e.g. If I have a panic on a run, with two keystrokes I can jump to the origin of the panic, and then their caller, and then the parent caller, and then up to the grandparent on the call stack... instantly. I've never found this essential functionality elsewhere, but maybe I'm just not familiar... A friend of mine tried to add it to Visual Studio and gave up... it was just too hard for VS. But maybe JetBrains has it?? I'd love to try an IDE other than emacs, but this is a fundament thing, that I cannot give up. On Friday, August 25, 2023 at 6:21:35 PM UTC+1 Mike Schinkel wrote: > Yes, as Luke Crook mentioned I think those requirements are more ALM > functionality than IDE functionality. > > Generally, ALM addresses concerns broader than individual concerns whereas > IDEs are more focused on individual productivity. > > Just my opinion, but I would expect you'd be better off finding an ALM > solution and then an IDE that integrates with that ALM, or vice versa, i.e. > find an IDE that integrates with an ALM and then use that ALM. > > #fwiw > > -Mike > On Wednesday, August 23, 2023 at 7:21:46 AM UTC-4 alex-coder wrote: > >> Hi All ! >> >> Considering that IBM's punch cards were bearing at least twice, I would >> vote for them. :-) >> >> Of cource I do agree with them who wrote that to feel comfortable "under >> fingers" is great ! >> >> So, the tasks to code - they are different. >> Sometimes it is possible to keep all the details regards to the task in a >> head or several. >> Sometimes it is nesessary to write say a hard copy of them(details) on a >> paper with a different size. >> >> But in case the task from the area of the "poorly formalized". You spend >> paper quickly. :-) >> >> The Luke Crook points to: >> https://en.wikipedia.org/wiki/Application_lifecycle_management >> >> I will simplify the task somewhat and take from ALM for example even less >> than SDLC, namely: >> requirements, design, implementation, testing, deployment. >> >> 1. Requirements must be described somewhere. >> 2. Design artifacts should reflect requirements. >> 3. Design decisions refer to objects and messages that >> implemented in the form of classes and operations. >> 4. Each operation must pass at least one test. >> All tests must be passed successfully. >> 5. The application is assembled and installed there and >> the tests are successfully passed again. >> >> Question: is there any IDE or plugin which one support that kind of >> dependencies in a graphical mode ? >> >> Thank you. >> >> вторник, 22 августа 2023 г. в 18:22:52 UTC+3, Mike Schinkel: >> >>> On Saturday, August 19, 2023 at 5:27:34 AM UTC-4 alex-coder wrote: >>> >>> What I'm looking for is the ability to manage dependencies not only in >>> code, >>> but entirely in a project from requirements to deployment. >>> >>> >>> I assume you mean a lot more than just Go package dependencies, as `go >>> mod` handles those nicely. >>> >>> Can you elaborate on the specific dependencies you are trying to >>> manage? In specific, vs generalities. >>> >>> -Mike >>> >> -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/ba7b55ac-826e-42c2-8695-376441e7915en%40googlegroups.com.
