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: history shows edited lines not the lines actually ran | Chet Ramey <chet.ramey@case.edu> | 2018-06-18 09:29 -0400 |
| Re: [PATCH] Add nofirstword completion option | Luca Boccassi <bluca@debian.org> | 2018-06-19 15:27 +0100 |
| Re: [PATCH] Add nofirstword completion option | Chet Ramey <chet.ramey@case.edu> | 2018-06-19 11:43 -0400 |
| $OPTIND varibale value is different from sh | Hyunho Cho<mug896@naver.com> | 2018-06-20 17:16 +0900 |
| Re: $OPTIND varibale value is different from sh | Greg Wooledge <wooledg@eeg.ccf.org> | 2018-06-20 08:39 -0400 |
| propagating environment variable via internal command | Tomáš Čech <sleep_walker@gnu.org> | 2018-06-20 15:25 +0200 |
| Re: Variables can’t contain NUL | George <tetsujin@scope-eye.net> | 2018-06-20 10:22 -0400 |
| Re: propagating environment variable via internal command | Chet Ramey <chet.ramey@case.edu> | 2018-06-20 10:42 -0400 |
| Re: Variables can’t contain NUL | Clark Wang <dearvoid@gmail.com> | 2018-06-20 23:36 +0800 |
| Re: $OPTIND varibale value is different from sh | Ilkka Virta <itvirta@iki.fi> | 2018-06-20 19:45 +0300 |
| Re: $OPTIND varibale value is different from sh | Martijn Dekker <martijn@inlv.org> | 2018-06-20 19:09 +0100 |
| Re: $OPTIND varibale value is different from sh | Martijn Dekker <martijn@inlv.org> | 2018-06-20 19:22 +0100 |
| Re: propagating environment variable via internal command | Tomas Janousek <tomas.janousek@gooddata.com> | 2018-06-20 21:11 +0200 |
| Re: $OPTIND varibale value is different from sh | Chet Ramey <chet.ramey@case.edu> | 2018-06-20 16:03 -0400 |
| Bash 5.0-alpha tries to expand exclamation marks in quoted strings | "Bernhard Rosenkraenzer" <bero@lindev.ch> | 2018-06-21 00:29 +0200 |
| Re: Bash 5.0-alpha tries to expand exclamation marks in quoted strings | Chet Ramey <chet.ramey@case.edu> | 2018-06-20 22:11 -0400 |
| "help" translates arguments of builtin commands but not command description | Ralf Goertz <me@myprovider.invalid> | 2018-06-21 09:41 +0200 |
| Re: "help" translates arguments of builtin commands but not command description | Chet Ramey <chet.ramey@case.edu> | 2018-06-21 11:24 -0400 |
| announcing bashj | pg <philippe.gonze@gmail.com> | 2018-06-23 19:08 +0200 |
| Re: announcing bashj | Eduardo Bustamante <dualbus@gmail.com> | 2018-06-23 13:45 -0500 |
| Re: announcing bashj | L A Walsh <bash@tlinx.org> | 2018-06-23 12:44 -0700 |
| Re: announcing bashj | Chet Ramey <chet.ramey@case.edu> | 2018-06-23 17:04 -0400 |
| Re: announcing bashj | Bob Proulx <bob@proulx.com> | 2018-06-23 15:52 -0600 |
| Directing into a variable doesn't work | Peter Passchier <peter@passchier.net> | 2018-06-24 10:08 +0700 |
| Re: Directing into a variable doesn't work | Martijn Dekker <martijn@inlv.org> | 2018-06-24 12:38 +0200 |
| Re: Directing into a variable doesn't work | Peter Passchier <peter@passchier.net> | 2018-06-24 22:26 +0700 |
| Re: Directing into a variable doesn't work | Robert Elz <kre@munnari.OZ.AU> | 2018-06-25 00:27 +0700 |
| Re: Directing into a variable doesn't work | Peter Passchier <peter@passchier.net> | 2018-06-25 00:35 +0700 |
| Re: Directing into a variable doesn't work | Pierre Gaston <pierre.gaston@gmail.com> | 2018-06-24 21:12 +0300 |
| Re: Directing into a variable doesn't work | Chet Ramey <chet.ramey@case.edu> | 2018-06-25 09:11 -0400 |
| Re: Directing into a variable doesn't work | Peter Passchier <peter@passchier.net> | 2018-06-25 20:54 +0700 |
| Re: Directing into a variable doesn't work | L A Walsh <bash@tlinx.org> | 2018-06-25 15:11 -0700 |
| ./parse.y: warning: 1 shift/reduce conflict [-Wconflicts-sr] | Piotr Grzybowski <narsil.pl@gmail.com> | 2018-06-27 12:59 +0200 |
| Re: ./parse.y: warning: 1 shift/reduce conflict [-Wconflicts-sr] | Chet Ramey <chet.ramey@case.edu> | 2018-06-27 08:57 -0400 |
| Re: ./parse.y: warning: 1 shift/reduce conflict [-Wconflicts-sr] | Piotr Grzybowski <narsil.pl@gmail.com> | 2018-06-27 16:33 +0200 |
| Re: Directing into a variable doesn't work | tetsujin@scope-eye.net | 2018-06-27 15:03 -0400 |
| Re: ./parse.y: warning: 1 shift/reduce conflict [-Wconflicts-sr] | Chet Ramey <chet.ramey@case.edu> | 2018-06-27 15:16 -0400 |
| Re: announcing bashj | Eduardo Bustamante <dualbus@gmail.com> | 2018-06-28 05:26 -0500 |
| Re: Directing into a variable doesn't work | Piotr Grzybowski <narsil.pl@gmail.com> | 2018-06-28 14:12 +0200 |
| -- paramter does not work in bash 4.4 | bashreport@oninoni.de | 2018-06-30 15:06 +0200 |
| Re: -- paramter does not work in bash 4.4 | Eric Blake <eblake@redhat.com> | 2018-07-02 16:41 -0500 |
| bash 4.3.48(1) and repo: processing of commands halts at first semicolon | toww <toww@nvidia.com> | 2018-07-02 16:58 -0700 |
| Re: bash 4.3.48(1) and repo: processing of commands halts at first semicolon | Eduardo A. Bustamante López <dualbus@gmail.com> | 2018-07-02 17:25 -0700 |
| Re: bash 4.3.48(1) and repo: processing of commands halts at first semicolon | Chet Ramey <chet.ramey@case.edu> | 2018-07-02 19:20 -0600 |
| Re: Redirect to variable | Robert Durkacz <robert.durkacz@gmail.com> | 2018-07-03 22:43 +1000 |
| Re: Redirect to variable | Ilkka Virta <itvirta@iki.fi> | 2018-07-03 15:52 +0300 |
| Re: Redirect to variable | Greg Wooledge <wooledg@eeg.ccf.org> | 2018-07-03 08:53 -0400 |
| Re: bash 4.3.48(1) and repo: processing of commands halts at first semicolon | Chet Ramey <chet.ramey@case.edu> | 2018-07-03 10:34 -0600 |
| Re: bash 4.3.48(1) and repo: processing of commands halts at first semicolon | Chet Ramey <chet.ramey@case.edu> | 2018-07-03 10:59 -0600 |
| Re: bash 4.3.48(1) and repo: processing of commands halts at first semicolon | toww <toww@nvidia.com> | 2018-07-03 13:52 -0700 |
« Previous 1 ... 51 52 53 54 55 ... 114 Next »
csiph-web