Lucas Gangstad
Lucas Gangstad
Agreed. That's the issue I originally made, which was closed as a duplicate, so it seems like this issue should be modified to accurately reflect the issue.
Other than the configuration aftman does for your path, the entire installation is contained in that folder, so removing it should remove aftman.
I'm not really involved in this, but having looked at the problem and solution I think that a better overall solution probably involves doing both. Creating our own separate tmp...
Right, this is why I suggested first copying it from one filesystem to the other within the directory its meant to be i.e. `~.aftman/bin`, using a temporary filename e.g. `mybin.tmp`....
Can we get this linked to an issue that explains what the PR is solving to keep that documented for the future?
We can potentially revisit this interface later if we do more debugger reworking. For now, however, this is the interface that I think is the least intrusive and still has...
I don't think this is a good choice of API. The debugger shouldn't be creating a loop. If you think the parameters need to be associated, I understand that argument...
I think it would actually be best to display debug information about this problem that could assist the developer, e.g. "World does not contain entity {id}."
This isn't what the wontfix label is for. I've added the appropriate blocked label.
I would definitely use this for C# if it were supported. I'm sure many others would as well.