Yes. I knew it was off-topic. Looking for activity in other projects, me and a few friends also found that Savannah seemed a bit unused. This is why I decided to post here. Sorry for this.
I'll check the other list, and its answer. I'll recheck why I didn't see it, since it has an answer. Thank you very much for your attention. > Hello Balaco, > > You have posted to the Savannah users mailing list. This is a mailing > list concerning operation of the Savannah freedom software forge. But > you are asking about Bash. Bash is a separate project. You should > write to the bash project maintainers if you want to discuss bash. > > I see you have already done this. Chet Ramey the bash maintainer > responded to your message. Did you not get his response? Your > original message and his response is here: > > http://lists.gnu.org/archive/html/bug-bash/2015-05/msg00027.html > > http://lists.gnu.org/archive/html/bug-bash/2015-05/msg00028.html > > There wasn't any follow-up from you in that mailing list. That is the > right place to talk about the bash project. Either to bug-bash or to > the help-bash mailing list. > > Bob > > Balaco Baco wrote: > >> About a year ago I reported an issue that I have known Bash has since >> years ago. No clear solution seems to exist, just work arounds some do >> for their specific cases. >> >> The issue is about duplicate history lines, even with erasedups active: >> >> https://savannah.gnu.org/support/?108530 >> >> My "solution" is the simple silly, but quite ashaming to say: use >> HIST*SIZE configs with muuuuch bigger values I would choose otherwise. >> But the issue makes the configuration pointless since I can't know how >> many lines of (different) lines my history really has - unless I >> carefully make/find a script or program to count it. But it should be >> the config number and that's all. >> >> The Savannah issue got no comment, pointer, or any apparent activity. So >> I decided to ask here. And the results can be everything, but no chance >> of being worse. So, why not? :)
