Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug

gnu.bash.bug

5684 articles (numbers 11058 – 16896) — threaded view

| Advanced

Subject Author Date [asc]
[PATCH] Use memmove instead of strcpy "Bernhard M. Wiedemann" <bwiedemann@suse.de> 2018-07-07 07:25 +0200
[PATCH] Use memmove instead of strcpy "Bernhard M. Wiedemann" <bwiedemann@suse.de> 2018-07-07 08:04 +0200
[PATCH] Fix null environ crash in getenv() provided by lib/sh/getenv.c Keeley Hoek <keeley@hoek.io> 2018-07-08 21:21 +1000
Re: [PATCH] Use memmove instead of strcpy Chet Ramey <chet.ramey@case.edu> 2018-07-09 09:52 -0400
Re: [PATCH] Fix null environ crash in getenv() provided by lib/sh/getenv.c Chet Ramey <chet.ramey@case.edu> 2018-07-09 10:16 -0400
Number with sign is read as octal despite a leading 10# Isaac Marcos <isaacmarcos100010@gmail.com> 2018-07-09 21:24 -0400
Re: Number with sign is read as octal despite a leading 10# Clint Hepner <clint.hepner@gmail.com> 2018-07-09 21:37 -0400
Word boundary anchors \< and \> not parsed correctly on the right side of =~ marcelpaulo@gmail.com 2018-07-09 22:46 -0300
Re: Number with sign is read as octal despite a leading 10# Ilkka Virta <itvirta@iki.fi> 2018-07-10 13:44 +0300
Re: Number with sign is read as octal despite a leading 10# Ilkka Virta <itvirta@iki.fi> 2018-07-10 14:14 +0300
Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~ Greg Wooledge <wooledg@eeg.ccf.org> 2018-07-10 08:27 -0400
Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~ Ilkka Virta <itvirta@iki.fi> 2018-07-10 15:52 +0300
Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~ Paulo Marcel Coelho Aragão <marcelpaulo@gmail.com> 2018-07-10 10:02 -0300
Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~ Greg Wooledge <wooledg@eeg.ccf.org> 2018-07-10 09:09 -0400
Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~ Paulo Marcel Coelho Aragão <marcelpaulo@gmail.com> 2018-07-10 10:15 -0300
Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~ Chet Ramey <chet.ramey@case.edu> 2018-07-10 10:37 -0400
Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~ Chet Ramey <chet.ramey@case.edu> 2018-07-10 10:47 -0400
Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~ Chet Ramey <chet.ramey@case.edu> 2018-07-10 10:50 -0400
Re: Number with sign is read as octal despite a leading 10# Chet Ramey <chet.ramey@case.edu> 2018-07-10 11:00 -0400
Re: Number with sign is read as octal despite a leading 10# Greg Wooledge <wooledg@eeg.ccf.org> 2018-07-10 11:04 -0400
Re: Word boundary anchors \< and \> not parsed correctly on the right side of =~ Paulo Marcel Coelho Aragão <marcelpaulo@gmail.com> 2018-07-10 12:07 -0300
Re: Number with sign is read as octal despite a leading 10# Chet Ramey <chet.ramey@case.edu> 2018-07-10 11:09 -0400
Re: Number with sign is read as octal despite a leading 10# Chet Ramey <chet.ramey@case.edu> 2018-07-10 11:11 -0400
Re: Number with sign is read as octal despite a leading 10# Pierre Gaston <pierre.gaston@gmail.com> 2018-07-10 19:16 +0300
Re: Number with sign is read as octal despite a leading 10# Ilkka Virta <itvirta@iki.fi> 2018-07-10 21:41 +0300
Re: Number with sign is read as octal despite a leading 10# Isaac Marcos <isaacmarcos100010@gmail.com> 2018-07-10 16:57 -0400
Re: Number with sign is read as octal despite a leading 10# Eduardo Bustamante <dualbus@gmail.com> 2018-07-10 15:12 -0700
Re: Number with sign is read as octal despite a leading 10# Isaac Marcos <isaacmarcos100010@gmail.com> 2018-07-10 18:46 -0400
Re: Number with sign is read as octal despite a leading 10# Isaac Marcos <isaacmarcos100010@gmail.com> 2018-07-10 20:44 -0400
INT still propagating to child processes when trapped Daniel Mills <danielmills1@gmail.com> 2018-07-10 22:59 -0400
Re: Number with sign is read as octal despite a leading 10# Chet Ramey <chet.ramey@case.edu> 2018-07-10 23:17 -0400
Re: Number with sign is read as octal despite a leading 10# Chet Ramey <chet.ramey@case.edu> 2018-07-10 23:31 -0400
Crash on jobs 2^32-2 Simon Wörner <simon.woerner@rub.de> 2018-07-11 15:41 +0200
Re: Crash on jobs 2^32-2 Piotr Grzybowski <narsil.pl@gmail.com> 2018-07-11 16:05 +0200
Re: Crash related to mkseq Chet Ramey <chet.ramey@case.edu> 2018-07-12 11:50 -0400
Re: Crash related to execute_builtin Chet Ramey <chet.ramey@case.edu> 2018-07-12 16:16 -0400
Re: Crash on jobs 2^32-2 Chet Ramey <chet.ramey@case.edu> 2018-07-12 16:53 -0400
Re: Number with sign is read as octal despite a leading 10# Robert Elz <kre@munnari.OZ.AU> 2018-07-13 11:35 +0700
Re: Crash on jobs 2^32-2 isabella parakiss <izaberina@gmail.com> 2018-07-13 14:17 +0100
Re: Crash on jobs 2^32-2 Chet Ramey <chet.ramey@case.edu> 2018-07-13 09:24 -0400
Re: INT still propagating to child processes when trapped Chet Ramey <chet.ramey@case.edu> 2018-07-13 10:33 -0400
bash history for each folder it was ran in. Clayton G <teslaenergy@gmail.com> 2018-07-14 08:03 -0600
Issue – Invalid command documented – BASH_BUILTINS(1) – Ricky Tigg <ricky.tigg@gmail.com> 2018-07-14 16:38 +0200
Re: Issue – Invalid command documented – BASH_BUILTINS(1) – Chet Ramey <chet.ramey@case.edu> 2018-07-14 11:46 -0400
Re: Issue – Invalid command documented – BASH_BUILTINS(1) – Peter & Kelly Passchier <peterkelly@passchier.net> 2018-07-14 23:05 +0700
Re: Issue – Invalid command documented – BASH_BUILTINS(1) – Ricky Tigg <ricky.tigg@gmail.com> 2018-07-14 19:57 +0200
${parameter@A} doesn't work should no value be set Michal Pesa <pesathem@gmail.com> 2018-07-14 21:10 +0200
Parameter indirection konsolebox <konsolebox@gmail.com> 2018-07-16 02:19 +0800
Re: Parameter indirection Chet Ramey <chet.ramey@case.edu> 2018-07-15 18:00 -0400
Re: ${parameter@A} doesn't work should no value be set Chet Ramey <chet.ramey@case.edu> 2018-07-15 18:19 -0400

« Previous 1 ... 50 51 52 53 54 ... 114 Next »


csiph-web