Chet Ramey wrote:
> Chris Down wrote:
> > Peter Cordes wrote:
> >> Oh, also, the online bug-bash archive has a bad habbit of replacing
> >> code with address@hidden. There was a whole thread about setting
> >> PS1=whatever that is now a complete mystery to non-subscribers!
> >
> > Yes, let's plea
On Thu, Nov 28, 2013 at 12:40:34PM -0500, Chet Ramey wrote:
> On 11/28/13, 7:23 AM, Peter Cordes wrote:
> > I submitted this on savannah a couple days ago:
> > https://savannah.gnu.org/support/?108450
> >
> > As I said there, the warning message for bash re-using a PID that
> > it's tracking for
Allodoxaphobia wrote:
> Chris Down wrote:
> > Peter Cordes wrote:
> > > Oh, also, the online bug-bash archive has a bad habbit of replacing
> > > code with address@hidden. There was a whole thread about setting
> > > PS1=whatever that is now a complete mystery to non-subscribers!
> >
> > Yes, let'
Thank you. I will therefore change my mind and suggest this feature _not_ be
included.
(I could also try
$ stty kill '@'
for the same reason.)
Sent from my iPad
> On Nov 25, 2013, at 4:09 PM, Bob Proulx wrote:
>
> Ryan Campbell Cunningham wrote:
>>I would like to request that Bash d
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown'
-DLOCALEDIR='/usr/local/apps/ba
On 2013-11-28 13:01:49 -0500, Chet Ramey wrote:
> I think this is a global setting
Ouch.
> and probably does more good than the annoyance it causes.
I don't think so. From my anecdotal experience, I've only ever had it
cause irritation when reading the archives. There are a million better
ways t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/28/13, 10:09 AM, Chris Down wrote:
> On 2013-11-28 08:23:01 -0400, Peter Cordes wrote:
>> Oh, also, the online bug-bash archive has a bad habbit of replacing
>> code with address@hidden. There was a whole thread about setting
>> PS1=whatever th
On 11/28/13, 7:13 AM, Peter Cordes wrote:
> Does anyone look at the bug tracker on Savannah?
> https://savannah.gnu.org/support/?group=bash
>
> I submitted a bug there, after going to the GNU project page for bash
> http://www.gnu.org/software/bash/ and following the link to the
> Savannah page
On 11/28/13, 7:27 AM, utilisateur_hxexp_expl wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: powerpc
> OS: aix5.3.0.0
> Compiler: cc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='powerpc'
> -DCONF_OSTYPE='aix5.3.0.0' -DCONF_MACHTYPE='powerpc-ibm-a
On 11/28/13, 7:23 AM, Peter Cordes wrote:
> I submitted this on savannah a couple days ago:
> https://savannah.gnu.org/support/?108450
>
> As I said there, the warning message for bash re-using a PID that
> it's tracking for exitted processes in suspended pipelines or w/e has
> an off-by-one err
On Thu, 28 Nov 2013 09:09:28 -0600, Chris Down wrote:
> On 2013-11-28 08:23:01 -0400, Peter Cordes wrote:
>> Oh, also, the online bug-bash archive has a bad habbit of replacing
>> code with address@hidden. There was a whole thread about setting
>> PS1=whatever that is now a complete mystery to no
On 2013-11-28 08:23:01 -0400, Peter Cordes wrote:
> Oh, also, the online bug-bash archive has a bad habbit of replacing
> code with address@hidden. There was a whole thread about setting
> PS1=whatever that is now a complete mystery to non-subscribers!
Yes, let's please stop this useless obfusca
I submitted this on savannah a couple days ago:
https://savannah.gnu.org/support/?108450
As I said there, the warning message for bash re-using a PID that
it's tracking for exitted processes in suspended pipelines or w/e has
an off-by-one error (jobs.c:892).
To summarize what I wrote on savann
Configuration Information [Automatically generated, do not change]:
Machine: powerpc
OS: aix5.3.0.0
Compiler: cc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='powerpc'
-DCONF_OSTYPE='aix5.3.0.0' -DCONF_MACHTYPE='powerpc-ibm-aix5.3.0.0'
-DCONF_VENDOR='ibm' -DLOCALEDIR='/usr/local/share/lo
(I'll send another email for the bug I found, instead of having 2
topics in 1 thread).
Does anyone look at the bug tracker on Savannah?
https://savannah.gnu.org/support/?group=bash
I submitted a bug there, after going to the GNU project page for bash
http://www.gnu.org/software/bash/ and follo
15 matches
Mail list logo