Rocky Bernstein

@Jokerwild - I have created a github repository for this and copied all of the code there. If you have a github account, please suggest changes from the above as Pull Requests (PR's) there. Here is a suggestion for something to do that is both needed and will get understanding the code better. Look at https://github.com/rocky/zshdb/ and the more recent changes there. See if these can be applied to bashdb. When this project was started, there wasn't much in the way of linters for shell code. In the...

@Jokerwild - I have created a github repository for this and copied all of the code there. If you have a github account, please suggest changes as Pull Requests (PR's) there. Here is a suggestion for something to do that is both needed and will get understanding the code better. Look at https://github.com/rocky/zshdb/ and the more recent changes there. See if these can be applied to bashdb. When this project was started, there wasn't much in the way of linters for shell code. In the past I have used...

Starting next week my time will finally free up. for open-source things. The top priority will be whatever is needed for bashdb and zshdb.

Yes, please submit these, to the extent we can, I would prefer the code bases to be as close as possible. As for the changes due pygments changing things from time to type, my view is that this is fragility in testing . Testing should be done without pygmentizing output. There should be tests just to see that pygments does something, but that test needs to be crafted more carefully so that it does not rely too heavily on specific kinds of formatting that is likely to change. For example it might...

Yes, please submit these, to the extent we can, I would prefer the code bases to be as close as possible. As for the changes due pygments changing things from time to type, my view is that this is fragility in testing . Testing should be done without pygmentizing output. There should be tests just to see that pygments does something, but that test needs to be crafted more careful so that it does not rely too heavily on specific kinds of formatting that is likely to change. For example it might detect...

Yes, please submit these, to the extent we can, I would prefer the code bases to as close as possible. As for the changes due pygments changing things from time to type, my view is that this is fragility in testing . Testing should be done without pygmentizing output. There should be tests just to see that pygments does something, but that test needs to be crafted more careful so that it does not rely too heavily on specific kinds of formatting that is likely to change. For example it might detect...

Yes, please submit these, to the extend we can I would prefer the code bases to as close as possible. As for the changes due pygments changing things from time to type, my view is that this is fragility in testing . Testing should be done without pygmentizing output. There should be tests just to see that pygments does something, but that test needs to be crafted more careful so that it does not rely too heavily on specific kinds of formatting that is likely to change. For example it might detect...

Thanks - I will look at the changes this weekend to let you know.