Added support for tilde to be present on the cwd through untildify
Closes #287
I’ve tested this with tilde in the cwd. Previously I’d see ‘lldb-mi’ not found errors when running the child process spawn for the debugger due to the tilde in the cwd. With this fix I no longer see that errror
untildify is MIT-licensed as other dependencies (most important the vscode parts) are, so I assume this is fine. As noted in the issue it would be good to either support tildes in general or not - can you please check if the calls to GDB/LMDB, the executables to debug need that (I guess the easiest option is to create a link to these in your home directory, then setup the paths using the tilde) and if the cwd arguments already internally resolves the tilde already? If not then we should use untildify also in these places.
Note: untildify currently only works for plain ~ (on all environments including Windows), but the ~user syntax is currently not supported: https://github.com/sindresorhus/untildify/issues/1 (no show stopper, just something to keep in mind)
Looks like they don’t need that. At least it seemed to work on my machine but my setup is a bit weird. I’m running this through a dap adapter in emacs. I’ve verified the name in emacs is using a relative path for the executable under debug for lldb it seems to be fine.