I like the idea. It reminds me of something I want for myself but can't really formulate well.
For example, let's say I'm working on a paper and while writing, I encounter a latex problem that I want fixed so I go off and look it up on stackoverflow (instead of making a note that I need to fix this later).
Ideally I'd go right back to working on my paper after solving the issue. Unless I can't solve it and have to do more digging and on and on. Until I'm interrupted by someone/ something and when I get back to the task at hand I don't even know what I was working on and why.
So I thought that it would be nice to have something like a stack trace of things I'm doing. I'd be able to see where I left off and more importantly how and why I got there. But I'm not sure that a stack is the right data structure for this, and if not, what else to use. Also, I can't imagine how to build something like this in a way that I'd actually use it, because it would probably require too much typing/ other overhead.
For example, let's say I'm working on a paper and while writing, I encounter a latex problem that I want fixed so I go off and look it up on stackoverflow (instead of making a note that I need to fix this later). Ideally I'd go right back to working on my paper after solving the issue. Unless I can't solve it and have to do more digging and on and on. Until I'm interrupted by someone/ something and when I get back to the task at hand I don't even know what I was working on and why.
So I thought that it would be nice to have something like a stack trace of things I'm doing. I'd be able to see where I left off and more importantly how and why I got there. But I'm not sure that a stack is the right data structure for this, and if not, what else to use. Also, I can't imagine how to build something like this in a way that I'd actually use it, because it would probably require too much typing/ other overhead.