Wataru Ashihara
Wataru Ashihara
One of the workaround is using HTML tags. ```html ## [example.com](http://example.com) ## _foo_ **bar** `baz` Using HTML tags: [example.com](http://example.com) _foo_ **bar** `baz` ^ space here must be needed (#7781) ```...
> The bottom part of the comment is not in the pull request Exactly. > but it looks like a "debug" test. Is the later assumption correct? I'm sorry, I...
Yes ToC (and possibly several other things) becomes impossible, so this is just a workaround. Thank you for pointing it out. I'll add a caution to the upper comment.
This behavior is as expected and a current limitation. Showing local variables in _VARIABLES_ view is one of our [plans](https://github.com/rogalmic/vscode-bash-debug/wiki/TODO-for-next-version), but is tough to be implemented :(
@eedwards-sk On [bashdb@7504a22](https://sourceforge.net/p/bashdb/code/ci/7504a22/), the behavior of getopt_long was changed, which was included on bashdb-4.0-0.4. Could you try [bashdb-4.4-0.92](https://sourceforge.net/projects/bashdb/files/bashdb/)? (not 4.4-0.93 or later because of #69) I think it can be...
Makes sense! @rogalmic Why don't we replace [--quiet --tty](https://github.com/rogalmic/vscode-bash-debug/blob/v0.2.0/src/bashDebug.ts#L142) with `-q -t` ? Using short options seems to be necessary when using macOS's built-in `/bin/bash` (version 3.2.57, even on latest...
## Summary of the issue bashdb on some environment can't parse `--quiet` and `--tty` options, thus vscode-bash-debug doesn't work. - bashdb < 4.0-0.4 uses [getopt(1)](http://man7.org/linux/man-pages/man1/getopt.1.html) to parse arguments to `bashdb`...
Reproduced on Ubuntu 18.04 ~~when debugging [NetBSD's build.sh](https://github.com/IIJ-NetBSD/netbsd-src/blob/master/build.sh)~~ on any script. Maybe comes from changes in latest bashdb, I'll describe details later.
git-bisecting revealed [bashdb@4e1479d](https://sourceforge.net/p/bashdb/code/ci/4e1479d) is the bad commit, certainly introducing the use of `stty` command. I think the author didn't consider a situation where bashdb's fd[0-2] are connected to pipes. As...
Here's a screenshot: ![image](https://user-images.githubusercontent.com/4846670/40974777-99ea76a4-6903-11e8-9806-bdbf2fde7b9b.png) Once debugging has started, we can't stop it nor even restarted it. The error message `stty: 'standard input': Inappropriate ioctl for device` differs from @mfour-merickson's one...