On Thu, 5 Jan 2012 10:12:34 +, Dave wrote:
>
> Recently upgraded to 3.2
That's *not* an upgrade. That's merely a 'change' in obsolescence.
On Fri, 27 Apr 2012 04:18:21 +0800, jida...@jidanni.org wrote:
> This would also save on later having to clean the massive blob out of
> the history list.
And, the Murphy's Law case(s) where one of the pasted lines
contains a 'legitimate' linux command...
Been there -- got a T-shirt.
Jonesy
On Thu, 11 Oct 2012 20:01:40 -0700 (PDT), Tinni wrote:
>
> I am very new to the shell scripting.. Need some pointers for getting
> the return value in shell scripting.
comp.unix.shell
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 Fri, 13 Feb 2009 00:43:48 -0800 (PST), Joe Murray99 wrote:
>
> I hope I am asking this in the correct place.
comp.unix.shell
On Sat, 4 Apr 2009 08:37:32 -0300, Sergio Charpinel Jr. wrote:
> Hi,
> I'm in this mailing list, and I dont know if I am in the right place. If it
> doesnt, tell me.
comp.unix.shell
I know, it's not very intuitive...
Jonesy
--
Marvin L Jones| jonz | W3DHJ | linu
On Wed, 14 Oct 2009 15:05:09 -0400, Greg Wooledge wrote:
> On Wed, Oct 14, 2009 at 12:24:30PM -0600, Bob Proulx wrote:
>> Pierre Gaston wrote:
>> > Please consider asking in a sed mailing list like:
>> > http://sed.sourceforge.net/#mailing
>> > or maybe in the usenet group comp.unix.shell
>>
>> I
(Didn't have the OP on the server to followup to. SRI)
> On 30 Nov 2009, at 12:12, Gerard wrote:
>>
>> I apologize for asking what is probably a dumb question, but where can
>> I find a definitive listing of what features are available in each
>> version of Bash.
>>
>> For example, I only have
On Tue, 18 May 2010 10:08:54 -0700 (PDT), Afflictedd2 wrote:
>
> I'm tryin to build a script
>
> Any help appreciated.
comp.unix.shell
In moving a bash ver. 4.3.48 (Ubuntu) program to a bash ver. 5.0.11
(FreeBSD) environment I encountered either a bug, a quirk, or
an undocumented feature.
I was using a null regexp as a "match for anything" case when an
optional command line parameter (a test pattern) was omitted.
I boiled down
On Mon, 23 Sep 2019 09:21:44 -0400, Chet Ramey wrote:
> On 9/22/19 5:44 PM, Allodoxaphobia wrote:
>
>> In moving a bash ver. 4.3.48 (Ubuntu) program to a bash ver. 5.0.11
>> (FreeBSD) environment I encountered either a bug, a quirk, or
>> an undocumented feature.
>
>
On Tue, 4 Feb 2020 11:45:45 -0500 (COT), ivandarioarr...@gmail.com wrote:
> Dear Engineers,
>
> When I write this message, I think I am writing to the best software
> developers in the world, or to those who are in the process of being
> one.
It will be interesting to see what other ng's this po
On Thu, 26 Mar 2020 19:05:58 +0200, Vaidas BoQsc wrote:
> I keep on wondering why these shells can't come up with something better
> than improving previous shell syntax by little by only providing poor
> better alternatives.
> I somehow think there is a need to rethink shells from scratch to make
Earlier today I performed the `bash` security upgrade on my
| [userid~]uname -rs
| FreeBSD 10.0-RELEASE-p9
machine. I thought to check the version level of `bash` to
see what I now have:
| [userid~]man bash
| :
| :
| --version
| Show version information for this instance of ba
On Thu, 25 Sep 2014 23:04:46 -0400, Chet Ramey wrote:
> On 9/25/14, 9:41 PM, Allodoxaphobia wrote:
>> Earlier today I performed the `bash` security upgrade on my
>> | [userid~]uname -rs
>> | FreeBSD 10.0-RELEASE-p9
>> machine. I thought to check the version level of
On 26 Sep 2014 03:13:57 GMT, Allodoxaphobia wrote:
> On Thu, 25 Sep 2014 23:04:46 -0400, Chet Ramey wrote:
>> On 9/25/14, 9:41 PM, Allodoxaphobia wrote:
>>> Earlier today I performed the `bash` security upgrade on my
>>> | [userid~]uname -rs
>>> | FreeBSD 10.
On Fri, 26 Sep 2014 10:25:32 -0400, Chet Ramey wrote:
> On 9/26/14, 10:15 AM, Allodoxaphobia wrote:
>
>> There was another bash upgrade in the FreeBSD ports this A.M.
>> Thinking it might resolve my bash --version problem, I applied it.
>>
>> sigh...
>>
>
On Sun, 8 Mar 2015 22:05:29 +, Stephane Chazelas wrote:
> 2015-03-07 18:01:18 -0600, Eduardo A. Bustamante López:
>> > But I am wondering if there is a walkaround to deal with errors in
>> > <(). The ideal behavior should be that if there is a error in <(),
>> > then we should not consider comm
On Tue, 31 Mar 2015 15:39:13 -0500, John McKown wrote:
> Hum, on my system, I get the message you are expecting. Transcript:
<-snip->
And, here...
This is puzzling.
On an older Ubuntu 10.04 system I still use (I know, I know...) I
get _no_ response. But the return code appears correct:
jonesy@n
On Sun, 20 Dec 2015 23:59:32 -0500, Bill Duncan wrote:
> We had 3 this year..
>
> $ for y in {1950..2050} ; do for m in {1..12};do cal $m $y|awk
> 'FNR==1{m=$0}/^ 1/{print m}';done;done| awk '{a[$2]=a[$2]" "$1}END{for (i in
> a) print i,a[i]}'| sort| awk '{t=$1;$1="";a[$0]=a[$0]" "t}END{for (i in
On Sun, 14 Feb 2016 00:25:46 + (UTC), Val Krem wrote:
> Hi all,
>
> I have a file (5000 rows and 65,000 columns).
>
>
> 1. For each row I want find and count the number of missing variable
> represented by (NA) and then print out.
>
> Sample data
>
> 1. fgh1 1 1 2 1 NA 2 2
>
> 2. fgh2
On Mon, 15 Feb 2016 08:19:37 -0500, Greg Wooledge wrote:
> On Sun, Feb 14, 2016 at 03:02:58AM +0000, Allodoxaphobia wrote:
>> err... u... What's your *bash bug* ???
>
> I think what he meant to say is, "Questions of this type should be
> sent to help-b...@gnu.org
22 matches
Mail list logo
