Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
5684 articles (numbers 11058 – 16896) — threaded view
| Advanced| Subject | Author | Date [asc] |
|---|---|---|
| Re: expression evaluation problem | Ilkka Virta <itvirta@iki.fi> | 2019-07-25 21:15 +0300 |
| Optimize bash string handling? | Alkis Georgopoulos <alkisg@gmail.com> | 2019-07-26 12:55 +0300 |
| Re: expression evaluation problem | L A Walsh <bash@tlinx.org> | 2019-07-26 03:04 -0700 |
| T/F var expansion? | L A Walsh <bash@tlinx.org> | 2019-07-28 21:17 -0700 |
| Re: T/F var expansion? | Martin Schulte <gnu@schrader-schulte.de> | 2019-07-29 07:01 +0200 |
| Have var+func sourced in a subroutine but they don't seem to end up in same scope | L A Walsh <bash@tlinx.org> | 2019-07-28 23:25 -0700 |
| valid kernel patch? using -e to catch errors? | L A Walsh <bash@tlinx.org> | 2019-07-29 00:16 -0700 |
| Re: T/F var expansion? | L A Walsh <bash@tlinx.org> | 2019-07-29 00:57 -0700 |
| Fwd: valid kernel patch? using -e to catch errors? | L A Walsh <bash@tlinx.org> | 2019-07-29 01:02 -0700 |
| Re: T/F var expansion? | David <bouncingcats@gmail.com> | 2019-07-29 18:08 +1000 |
| Re: T/F var expansion? | Stephane Chazelas <stephane.chazelas@gmail.com> | 2019-07-29 10:28 +0100 |
| Re: Have var+func sourced in a subroutine but they don't seem to end up in same scope | Greg Wooledge <wooledg@eeg.ccf.org> | 2019-07-29 09:43 -0400 |
| Re: Have var+func sourced in a subroutine but they don't seem to end up in same scope | Ilkka Virta <itvirta@iki.fi> | 2019-07-29 19:25 +0300 |
| x[ | Isabella Bosia <izaberina@gmail.com> | 2019-07-29 17:55 +0100 |
| Re: x[ | Clint Hepner <clint.hepner@gmail.com> | 2019-07-29 13:01 -0400 |
| Re: x[ | Eli Schwartz <eschwartz@archlinux.org> | 2019-07-29 13:09 -0400 |
| Re: x[ | Greg Wooledge <wooledg@eeg.ccf.org> | 2019-07-29 13:14 -0400 |
| Re: x[ | Stephane Chazelas <stephane.chazelas@gmail.com> | 2019-07-29 18:53 +0100 |
| How does this wait -n work to cap parallelism? | Earnestly <zibeon@googlemail.com> | 2019-07-29 19:12 +0100 |
| Re: x[ | Chet Ramey <chet.ramey@case.edu> | 2019-07-29 14:30 -0400 |
| Re: How does this wait -n work to cap parallelism? | Greg Wooledge <wooledg@eeg.ccf.org> | 2019-07-29 14:38 -0400 |
| Re: How does this wait -n work to cap parallelism? | Earnestly <zibeon@googlemail.com> | 2019-07-29 20:02 +0100 |
| Re: How does this wait -n work to cap parallelism? | Earnestly <zibeon@googlemail.com> | 2019-07-29 21:27 +0100 |
| Re: x[ | Martijn Dekker <martijn@inlv.org> | 2019-07-30 00:01 +0200 |
| Re: x[ | Eli Schwartz <eschwartz@archlinux.org> | 2019-07-29 19:53 -0400 |
| Re: x[ | Koichi Murase <myoga.murase@gmail.com> | 2019-07-30 09:30 +0900 |
| ulimit call lists invalid options | L A Walsh <bash@tlinx.org> | 2019-07-29 19:57 -0700 |
| Re: ulimit call lists invalid options | Robert Elz <kre@munnari.OZ.AU> | 2019-07-30 12:09 +0700 |
| Re: Fwd: valid kernel patch? using -e to catch errors? | Robert Elz <kre@munnari.OZ.AU> | 2019-07-30 12:49 +0700 |
| Re: ulimit call lists invalid options | Robert Elz <kre@munnari.OZ.AU> | 2019-07-30 14:27 +0700 |
| Re: ulimit call lists invalid options | L A Walsh <bash@tlinx.org> | 2019-07-30 00:46 -0700 |
| Re: valid kernel patch? using -e to catch errors? | L A Walsh <bash@tlinx.org> | 2019-07-30 00:55 -0700 |
| Re: ulimit call lists invalid options | Robert Elz <kre@munnari.OZ.AU> | 2019-07-30 15:59 +0700 |
| Incorrect passing of argc argv with multiple redirects | Morgan McClure <mcclure.morgan@gmail.com> | 2019-07-30 10:08 -0700 |
| Re: Incorrect passing of argc argv with multiple redirects | Eduardo Bustamante <dualbus@gmail.com> | 2019-07-30 10:56 -0700 |
| Re: Incorrect passing of argc argv with multiple redirects | Chet Ramey <chet.ramey@case.edu> | 2019-07-30 14:00 -0400 |
| memleak in execute_function? | fireshen <shenyining@huawei.com> | 2019-07-31 08:26 -0700 |
| syntax errors produced by interaction between process substitution and a SIGCHLD trap | Travis Everett <travis.a.everett@gmail.com> | 2019-07-31 13:35 -0500 |
| Re: Optimize bash string handling? | Chet Ramey <chet.ramey@case.edu> | 2019-07-31 15:15 -0400 |
| Re: memleak in execute_function? | Chet Ramey <chet.ramey@case.edu> | 2019-07-31 19:19 -0400 |
| Re: memleak in execute_function? | fireshen <shenyining@huawei.com> | 2019-07-31 17:57 -0700 |
| Re: memleak in execute_function? | Chet Ramey <chet.ramey@case.edu> | 2019-07-31 21:35 -0400 |
| bash man page lacks mention of case flipping | l@latitude.scarydevilmonastery.net | 2019-08-02 19:49 +0200 |
| Re: bash man page lacks mention of case flipping | Chet Ramey <chet.ramey@case.edu> | 2019-08-02 14:38 -0400 |
| History not saved when closing terminal while bash is sourcing a script | Tomas Janousek <tomi@nomi.cz> | 2019-08-03 17:05 +0200 |
| Async processes started in functions not reliably started | Steffen Nurpmeso <steffen@sdaoden.eu> | 2019-08-04 00:40 +0200 |
| Re: Async processes started in functions not reliably started | Steffen Nurpmeso <steffen@sdaoden.eu> | 2019-08-04 01:17 +0200 |
| Re: History not saved when closing terminal while bash is sourcing a script | Chet Ramey <chet.ramey@case.edu> | 2019-08-04 13:42 -0400 |
| Re: Async processes started in functions not reliably started | Steffen Nurpmeso <steffen@sdaoden.eu> | 2019-08-05 14:05 +0200 |
| Re: Async processes started in functions not reliably started | Chet Ramey <chet.ramey@case.edu> | 2019-08-05 09:00 -0400 |
« Previous 1 ... 31 32 33 34 35 ... 114 Next »
csiph-web