Michał Rogaliński

- add tty_in terminal_in option for full control over separate terminal- make examine command show if command is builtin or not- spaces stuff- vscode configuration

- add tty_in terminal_in option for full control over separate terminal

further fixes, tested. Fix for failing tests in is set.sh...

bashdb: cannot read program to debug: /Users/dcooper/Downloads/bashdb-4.4-0.94/test/example/bug-set-e.sh. Looks like file is missing from #94 build package: test/example/bug-set-e.sh After taking the file from master branch, test passes. "make check" is not needed to install bashdb.

What is the issue here? Sorry, I totally misunderstood that. This is the integration test output, I get same error in "make check".

What is the issue here? I created 2 files: main.sh 1 2 3#!/bin/bash source test3.sh && echo success || echo fail test3.sh 1 2 3 4 5 6 7#!/bin/bash set -e (( 1 / 0)) echo eof As far as I can see, the debugger works as expected: prints fail when code as above prints eof\nsuccess when line is commented out: # (( 1 / 0))

Great, thank you for your help. I will reset my git fork...

Found additional small issue when showing bactrace and path has multiple spaces in bath: https://sourceforge.net/u/rogalmic/bashdb/ci/bdb0836764b24d783de564470b2604e52760fd37/ I think this fix is trivial and could also be taken.