<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent posts to Discussion</title><link href="https://sourceforge.net/p/bashdb/discussion/" rel="alternate"/><link href="https://sourceforge.net/p/bashdb/discussion/feed.atom" rel="self"/><id>https://sourceforge.net/p/bashdb/discussion/</id><updated>2024-01-14T08:24:25.777000Z</updated><subtitle>Recent posts to Discussion</subtitle><entry><title>Should I submit these changes for bashdb?</title><link href="https://sourceforge.net/p/bashdb/discussion/206895/thread/9c6c4fd536/?limit=25#5ec1" rel="alternate"/><published>2024-01-14T08:24:25.777000Z</published><updated>2024-01-14T08:24:25.777000Z</updated><author><name>Jokerwild</name><uri>https://sourceforge.net/u/jokerwild108/</uri></author><id>https://sourceforge.net61d674ef3cb812c2264ff40e940ffdb3de39bc1a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Rocky, sure, I will have a look at zshdb on GitHub, as you suggest.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Should I submit these changes for bashdb?</title><link href="https://sourceforge.net/p/bashdb/discussion/206895/thread/9c6c4fd536/?limit=25#14e4" rel="alternate"/><published>2024-01-13T09:33:35.354000Z</published><updated>2024-01-13T09:33:35.354000Z</updated><author><name>Rocky Bernstein</name><uri>https://sourceforge.net/u/rockyb/</uri></author><id>https://sourceforge.netac3288d6c13b2dfa29c2727386d206c87bace0f4</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;@Jokerwild  -  I have created a github repository for this and copied all of the code there. &lt;/p&gt;
&lt;p&gt;If you have a github account, please suggest changes as Pull Requests (PR's) there. &lt;/p&gt;
&lt;p&gt;Here is a suggestion for something to do that is both needed and will get understanding the code better. Look at &lt;a href="https://github.com/rocky/zshdb/" rel="nofollow"&gt;https://github.com/rocky/zshdb/&lt;/a&gt; and the more recent changes there. See if these can be applied to bashdb. &lt;/p&gt;
&lt;p&gt;When this project was started, there wasn't much in the way of linters for shell code. In the past I have used &lt;code&gt;ksh -n&lt;/code&gt; which  offers some checks. Nowadays there is &lt;a class="" href="https://www.shellcheck.net/" rel="nofollow"&gt;"ShellCheck"&lt;/a&gt; .&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Should I submit these changes for bashdb?</title><link href="https://sourceforge.net/p/bashdb/discussion/206895/thread/9c6c4fd536/?limit=25#f260" rel="alternate"/><published>2024-01-13T02:20:07.362000Z</published><updated>2024-01-13T02:20:07.362000Z</updated><author><name>Jokerwild</name><uri>https://sourceforge.net/u/jokerwild108/</uri></author><id>https://sourceforge.net8721dfcd97661c80b92b7f7265d2d65f98a6dcd5</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;My understanding of Bash is rather rudimentary, but I would like to help. If I can assist in any simple way to start with, please let me know.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Should I submit these changes for bashdb?</title><link href="https://sourceforge.net/p/bashdb/discussion/206895/thread/9c6c4fd536/?limit=25#e706" rel="alternate"/><published>2024-01-05T12:05:28.902000Z</published><updated>2024-01-05T12:05:28.902000Z</updated><author><name>Rocky Bernstein</name><uri>https://sourceforge.net/u/rockyb/</uri></author><id>https://sourceforge.netfc4b396dab6f67193b5be0c177463596c91776f8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Starting next week my time will &lt;em&gt;finally&lt;/em&gt; free up. for open-source things. The top priority will be whatever is needed for bashdb and zshdb. &lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Should I submit these changes for bashdb?</title><link href="https://sourceforge.net/p/bashdb/discussion/206895/thread/9c6c4fd536/?limit=25#53ac" rel="alternate"/><published>2024-01-05T11:28:35.759000Z</published><updated>2024-01-05T11:28:35.759000Z</updated><author><name>Joachim Ansorg</name><uri>https://sourceforge.net/u/joachim/</uri></author><id>https://sourceforge.netd2a7c96f2b2a42b05d8b5a35dd8ce165aee832eb</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;&lt;a class="user-mention" href="/u/rockyb/"&gt;@rockyb&lt;/a&gt; Thanks! &lt;br/&gt;
I've submitted most of the commits as merge requests. There's one against 4.4 and one against 5.1 where applicable.&lt;br/&gt;
I've kept most PRs to just one commit to help with the review.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Should I submit these changes for bashdb?</title><link href="https://sourceforge.net/p/bashdb/discussion/206895/thread/9c6c4fd536/?limit=25#8faa" rel="alternate"/><published>2023-12-16T22:22:07.835000Z</published><updated>2023-12-16T22:22:07.835000Z</updated><author><name>Rocky Bernstein</name><uri>https://sourceforge.net/u/rockyb/</uri></author><id>https://sourceforge.net3d2bab38f43ffd819b57f5b2207517c91ffe2b8c</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Yes, please submit these, to the extend we can I would prefer the code bases to as close as possible.&lt;/p&gt;
&lt;p&gt;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. &lt;/p&gt;
&lt;p&gt;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 that listings vary the output,  and maybe even check that keywords have tagging. around them. &lt;/p&gt;
&lt;p&gt;I am going to be busy until Jan 9th or so. After that I will probably have a lot more time to devote to open-source kinds of things.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Should I submit these changes for bashdb?</title><link href="https://sourceforge.net/p/bashdb/discussion/206895/thread/9c6c4fd536/?limit=25#d754" rel="alternate"/><published>2023-12-14T10:18:22.270000Z</published><updated>2023-12-14T10:18:22.270000Z</updated><author><name>Joachim Ansorg</name><uri>https://sourceforge.net/u/joachim/</uri></author><id>https://sourceforge.net2b4c43ef77036f8a36072000e41fe807c97a8f5a</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I've cleaned my commits and made sure that all tests are passing.&lt;br/&gt;
I had to repair a few, the commits should contain the details. Some failures were related to a new version of pygmentize. I wasn't sure which version is expected to run the tests.&lt;/p&gt;
&lt;p&gt;Commits to bash-5.1, which may be useful:&lt;br/&gt;
- &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/89f60e890ad7dbc904e61cd8861f74a643162958" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/89f60e890ad7dbc904e61cd8861f74a643162958&lt;/a&gt;&lt;br/&gt;
- &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/d83d7dc913fc66521926cfb3a689c3b9f6708f0a" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/d83d7dc913fc66521926cfb3a689c3b9f6708f0a&lt;/a&gt;&lt;br/&gt;
- &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/2d25b38290d317161efeb5c080e02184d3f5959d" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/2d25b38290d317161efeb5c080e02184d3f5959d&lt;/a&gt;&lt;br/&gt;
- &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/49d6c4379be1c5fd4d4e9089e718575b5d96380a" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/49d6c4379be1c5fd4d4e9089e718575b5d96380a&lt;/a&gt;&lt;br/&gt;
- &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/084d95d5447182151efc51cf324015b1ce5b4d7e" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/084d95d5447182151efc51cf324015b1ce5b4d7e&lt;/a&gt;&lt;br/&gt;
- &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/1eea0c01bbdaba0585deecfc9c61fe11640f9175" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/1eea0c01bbdaba0585deecfc9c61fe11640f9175&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Commits to bash-4.4, mostly the same as above:&lt;br/&gt;
- &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/1cf584c9cdb7255c411572e953beb9b615687045" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/1cf584c9cdb7255c411572e953beb9b615687045&lt;/a&gt;&lt;br/&gt;
- &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/4e76fda17466bae06cd7bef028645b199d95b028" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/4e76fda17466bae06cd7bef028645b199d95b028&lt;/a&gt;&lt;br/&gt;
- &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/b74a8f09725754e1264aa732692b75e2bb7d42b2" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/b74a8f09725754e1264aa732692b75e2bb7d42b2&lt;/a&gt;&lt;br/&gt;
- &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/a9ef0772dbe2c761cf5e8614ceb82ab19f0cf0af" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/a9ef0772dbe2c761cf5e8614ceb82ab19f0cf0af&lt;/a&gt;&lt;br/&gt;
- &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/6b0837c1ccf866b7f6c904f51559127cb5692f5d" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/6b0837c1ccf866b7f6c904f51559127cb5692f5d&lt;/a&gt;&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Should I submit these changes for bashdb?</title><link href="https://sourceforge.net/p/bashdb/discussion/206895/thread/9c6c4fd536/?limit=25#a1b9" rel="alternate"/><published>2023-12-13T19:03:39.126000Z</published><updated>2023-12-13T19:03:39.126000Z</updated><author><name>Rocky Bernstein</name><uri>https://sourceforge.net/u/rockyb/</uri></author><id>https://sourceforge.net6935818ce3ea025ef2876b6bc85db8649a846b2f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thanks - I will look at the changes  this weekend to let you know.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Should I submit these changes for bashdb?</title><link href="https://sourceforge.net/p/bashdb/discussion/206895/thread/9c6c4fd536/?limit=25#f01e" rel="alternate"/><published>2023-12-13T18:57:11.972000Z</published><updated>2023-12-13T18:57:11.972000Z</updated><author><name>Joachim Ansorg</name><uri>https://sourceforge.net/u/joachim/</uri></author><id>https://sourceforge.net5278ee38f76b6376058018fbe0325931a232c5b7</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;For BashSupport Pro, I have made a few changes to my fork of bashdb which were not yet submitted.&lt;br/&gt;
&lt;a href="https://github.com/BashSupport-Pro/bashdb/commits/bashsupport-5.1" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commits/bashsupport-5.1&lt;/a&gt; for the 5.1 branch and &lt;a href="https://github.com/BashSupport-Pro/bashdb/commits/bashsupport-4.4" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commits/bashsupport-4.4&lt;/a&gt; for the 4.4 branch.&lt;/p&gt;
&lt;p&gt;Commits like &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/389ad7668318ed6866d4fde32b820c1e321302dc" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/389ad7668318ed6866d4fde32b820c1e321302dc&lt;/a&gt; are most likely only useful for the use in BashSupport.&lt;/p&gt;
&lt;p&gt;For example, there's &lt;a href="https://github.com/BashSupport-Pro/bashdb/commit/f0bda0c2d67515444c2dcda18f7228f000c53d75" rel="nofollow"&gt;https://github.com/BashSupport-Pro/bashdb/commit/f0bda0c2d67515444c2dcda18f7228f000c53d75&lt;/a&gt;, which makes "info variables" faster (should be O(1) instead of O(n) now, I think) and keeps bash's escapes im the output to support linefeeds and spaces in the output. &lt;/p&gt;
&lt;p&gt;Because SF.net is so awkward, I wanted to make sure if these patches would be accepted before I submit them. &lt;br/&gt;
If it's likely that they'd be  merged, I'd clean it up and submit them with tests.&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>bashdb on bash 5.1</title><link href="https://sourceforge.net/p/bashdb/discussion/206895/thread/5e15940b26/?limit=25#0d33" rel="alternate"/><published>2023-08-19T19:44:11.191000Z</published><updated>2023-08-19T19:44:11.191000Z</updated><author><name>Rocky Bernstein</name><uri>https://sourceforge.net/u/rockyb/</uri></author><id>https://sourceforge.netace51a2a8ad0d0e1cc29fbce3adbfcedab1ae733</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Actually, I just tried from branch 5.1 and I do not see "This package is only known to work with Bash 5.0".  line 106 of configure.ac looks like 5.1 was allowed since 2020-07-29 in commit 6daffb5c. &lt;/p&gt;
&lt;p&gt;I have just adjusted the error message which reported that only 5.0 was allowed.&lt;/p&gt;
&lt;p&gt;As for the failures. I do still see two of them,. test-bash-rematch however is not in there, but another one test-bug-loc. Again though these can be ignored.&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>