Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #16216
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Suggestions for improving Bash |
| Date | 2020-04-21 08:46 -0400 |
| Organization | ITS, Case Western Reserve University |
| Message-ID | <mailman.877.1587473186.3066.bug-bash@gnu.org> (permalink) |
| References | <87wo69wp5x.fsf@hobgoblin.ariadne.com> <20200421111738.GA845@eeg.ccf.org> <2e9570c9-0638-d19e-0b47-7017c3fc4de8@case.edu> |
On 4/21/20 7:17 AM, Greg Wooledge wrote: > On Mon, Apr 20, 2020 at 10:25:30PM -0400, Dale R. Worley wrote: >> Is this the proper place to make suggestions for improving Bash? > > Yes. It should also be noted that there is no public bug tracker, That's not quite true. There is a bug tracker on savannah (https://savannah.gnu.org/support/index.php). It's just not as frequently used. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar
Re: Suggestions for improving Bash Chet Ramey <chet.ramey@case.edu> - 2020-04-21 08:46 -0400
csiph-web