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
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'
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 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
