middle ground between the two concerns.
I understand that, ultimately, you have to chose the solution that you feel is
the best balance overall.
Thanks for your maintenance of a critical piece of modern infrastructure!
-- John
On Monday, March 10, 2025 at 09:51:44 AM EDT, Chet Ramey
wrote:
On Monday, March 10, 2025 at 12:38:38 PM EDT, Zachary Santer
wrote:
> Another alternative would be for bash to print a warning whenever it
> encounters this syntax.
There are precedents for this kind of behavior in languages like perl which
issue warnings
for deprecated features for several rel
be documented here
would serve both aims?
-- John
On Monday, March 10, 2025 at 09:23:08 AM EDT, Chet Ramey
wrote:
On 3/7/25 12:23 PM, John Wiersba wrote:
> You're discouraging it's use by not documenting it. BTW, according to
> those links below, apparently zsh documen
Thanks, Greg!!!
On Friday, March 7, 2025 at 01:19:28 PM EST, Greg Wooledge
wrote:
On Fri, Mar 07, 2025 at 17:23:57 +, John Wiersba via Bug reports for the
GNU Bourne Again SHell wrote:
> - Is our conversation being recorded somewhere in the gnu archives, so
>that I can l
constructs?
- Is our conversation being recorded somewhere in the gnu archives, so that
I can link to it in my stackoverflow question? Otherwise, I'll just clip
quotes from it to paste there.
-- John
On Friday, March 7, 2025 at 12:03:18 PM EST, Chet Ramey
wrote:
On 3/7/25 9:23 A
at
https://unix.stackexchange.com/questions/306940/what-is-the-purpose-of-the-do-keyword-in-bash-for-loops/306944#306944
Thanks!-- John Wiersba
27;s not documented?
>
I think I can answer 'yes' to that, even if I can't quote any one post
as saying "This isn't documented in the manpage." These two users
(https://superuser.com/a/1620055) seem to have had some trouble, to
the point that they had the right answer first and "un-corrected" it
(see the edit history) to the wrong one: "I could have swore it used
to be different, but so goes my memory!" - user at that link. Again
though, kind of moot, if it's being removed so not much to discuss
there.
- John Devin
On line 3987 of bash.1 (here:
https://git.savannah.gnu.org/cgit/bash.git/tree/doc/bash.1#n3987),
`The\fBextglob\fP` is missing a space between 'The' and 'extglob'.
I'm not sure how small typos have to be before they're not worth an
email, so if this is, let me know.
- John Devin
Hey Chet,
Thanks for getting back so fast. Just a couple points to make.
On Thu, Sep 12, 2024 at 4:38 PM Chet Ramey wrote:
>
> On 9/11/24 3:19 PM, John Devin wrote:
> > While hunting down some problems on a terminal, I ran across the
> > option 'prefer-visible-bell
ate: "The convert-meta variable has no
effect if input-meta is off." From the manpage I would think so, but
I'm just not confident. I also can't tell conclusively whether the
output-meta variable is affected by convert-meta, or vice-versa.
Thanks for your time,
John Devin
Hi!
I believe the Bash Reference Manual is missing a key note for using "set
-o".
On the man page for "bash"
(https://tiswww.case.edu/php/chet/bash/bash.html), the following line is
present
* If *-o* is supplied with no /option-name/, the values of the current
options are printed. If *
if you wanted this for your script - read all then start semantics, as
opposed to read-as-you-execute - would it work to rewrite yourself inside a
function?
function main() { ... } ; main
On Sun, Apr 7, 2024, 22:58 Robert Elz wrote:
> Date:Mon, 8 Apr 2024 02:50:29 +0100
> From:
I was unaware of TMOUT. Now I have a backup as well. Thanks for tolerating my
inexperience.
On Sat, Feb 17, 2024 at 2:54 PM, Greg Wooledge wrote: On
Sat, Feb 17, 2024 at 07:41:43PM +, John Larew wrote:
> After further examination, the examples with "fg $$" and "
After further examination, the examples with "fg $$" and "fg $!" clearly do not
bring the subshell into the foreground, as they are evaluated prior to the
subshells background execution.
I'm trying to bring the subshell to the foreground to perform an exit, after a
delay.
Ultimately, it will be
Configuration Information [Automatically generated, do not change]:Machine:
x86_64OS: linux-gnuCompiler: gccCompilation CFLAGS: -g -O2 -flto=auto
-ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong
-Wformat -Werror=format-security -Wall uname output: Linux
HP-ProBook-6450b-5
interfacing with an external tool absolutely seems like the correct answer
to me. a fact worth mentioning to back that up is that `jq` exists. billed
as a sed/awk for json, it fills all the functions you'd expect such an
external tool to have and many many more. interfacing from curl to jq to
bash
Léa, I see that in the section Ilkka quoted you were using it in the
plural. However Ilkka is exactly right; despite "they" being technically
plural, using it for somebody of undetermined gender has been in the
mainstream since long before inclusive language. "Someone left *their*
book, there's no
I can see a couple reasons why it would be a good thing, and in the con
column only "I personally don't have time to go through the manual and make
these changes". but I'd happily upvote a patch from somebody that does.
On Sat, Jun 5, 2021, 09:24 Vipul Kumar
wrote:
> Hi,
>
> Isn't it a good ide
From: john
To: bug-bash@gnu.org
Subject: ls dumps bash
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -march=x86-64 -mtune=generic -O2 -pipe -fno-plt
-DDEFAULT_PATH_VALUE='/usr/local/sbin:/usr/local/bin
I think the underlying question here is not exactly "how do I gather this
from the docs" as much as it is "how was I supposed to know about this and
act on it before I had to debug it?" The bash manual is always "adequate"
in the sense that almost any question can be answered by carefully
consultin
On 3/26/20, George wrote:
> On Thu, 2020-03-26 at 19:05 +0200, Vaidas BoQsc wrote:
> I think shells would really benefit from things like
> more powerful data structures, better facilities for passing complex data
> to, and parsing complex data from different programs, better scoping,
> better fil
about POSIX sh scripts?
>
> This seems like a fairly big proposal for something I'm not even seeing
> a definite argument as being actually wrong.
>
> --
> Eli Schwartz
> Arch Linux Bug Wrangler and Trusted User
>
>
--
People in sleeping bags are the soft tacos of the bear world.
Maranatha! <><
John McKown
of adding these alternatives?
>
I think this would need to go to the bash-dev list. Have you tried tcsh? I
understand it tries to be C like.
--
People in sleeping bags are the soft tacos of the bear world.
Maranatha! <><
John McKown
Ah, got it sorted out.
Not a bug, of course (:
Bash, when not in posix mode, clears the '-e' flag in subshell environments.
On 10/3/19, John W wrote:
> I'm seeing some strange behavior w/regard to `set -e` when invoking a
> shell function through a `$(...)` construct.
>
r"?
Is this documented behavior, and I missed it?
Or a bug?
Or makes sense under some interpretation of things that I'm not grasping?
Thanks for any advice
-John
baz'
But
$ ls foo\[\]/
Expands to 'foo[]//' and does not list 'baz' or the directory contents.
I had a knowledgeable person in #bash (freenode) confirm this bug and they
said it happens in the development branch as well.
It does work correctly in bash 4.4.12.
Thanks,
John Van Sickle
; ``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRUc...@case.eduhttp://tiswww.cwru.edu/~chet/
>
>
--
I just burned 2000 calories!
That's the last time I'll nap with brownies in the oven.
Maranatha! <><
John McKown
When the read builtin is invoked with -n/-N , the documentation
specifies that at most characters will be read from stdin. This
statement is not true when stdin emits null characters: read discards
the null character and keeps reading without incrementing its counter,
continuing until it has consu
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: darwin17.5.0
Compiler: clang
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='darwin17.5.0' -DCONF_MACHTYPE='x86_64-apple-darwin17.5.0'
-DCONF_VENDOR='apple' -DLOCALEDIR='/usr/loca
> > If ncursesw is now the default, maybe it would make sense to check for that
> > rather than a symlink?
> >
> I added a check for it, but I think its impact will be minimal.
>
Thanks :)
> > Using bash-4.4.18
> > Intel core i7 laptop running 32-bit or 64-bit linux Using gcc-8.2.0
> >
> > The configure script does not find libncursesw on a system where
> > only the wide version of ncurses exists - even when readine is linked
> > against ncursesw.
> >
> I haven't seen a distro whe
Using bash-4.4.18
Intel core i7 laptop running 32-bit or 64-bit linux
Using gcc-8.2.0
The configure script does not find libncursesw on a system where only the wide
version of ncurses exists - even when readine is linked against ncursesw.
The configure scripts does not find libreadline when it
Using bash-4.4.18
Intel core i7 laptop running 32-bit or 64-bit linux
Using gcc-8.2.0
The configure script does not find libncursesw on a system where only the wide
version of ncurses exists - even when readine is linked against ncursesw.
The configure scripts does not find libreadline when it
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-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
.0.1 sleep
&
Try:
ssh -f -o ControlMaster=no -o ControlPath=/tmp/socket.tmp 127.0.0.1 sleep
--
Windows. A funny name for a operating system that doesn't let you see
anything.
Maranatha! <><
John McKown
On Sat, Jun 3, 2017 at 8:51 PM, L A Walsh wrote:
>
>
> John McKown wrote:
>
>> On Sat, Jun 3, 2017 at 4:48 PM, L A Walsh > b...@tlinx.org>> wrote:
>>
>>
>
> OK, I did a port of BASH to an IBM "mainframe" system (IBM z) which uses
>&g
back end work. There is
another mid-range IBM system which also uses EBCDIC, but I don't know if it
has a BASH port or not.
--
Windows. A funny name for a operating system that doesn't let you see
anything.
Maranatha! <><
John McKown
On Tue, May 23, 2017 at 1:55 PM, John McKown
wrote:
>
>
> On Tue, May 23, 2017 at 1:39 PM, Chet Ramey wrote:
>
>>
>> The best thing to read to learn about how the shell is structured -- other
>> than the code itself -- is the unedited version of the chapter I wrote
``Ars longa, vita brevis'' - Hippocrates
> Chet Ramey, UTech, CWRUc...@case.eduhttp://cnswww.cns.cwru.edu/~
> chet/
>
>
--
Windows. A funny name for a operating system that doesn't let you see
anything.
Maranatha! <><
John McKown
00 U.S.; example (not
recommendation): http://www.thinkmate.com/system/rax-xs4-1160v4. Honestly:
you need to change your algorithm for processing your problem. In your
example, perhaps a series of nested loops.
--
"Irrigation of the land with seawater desalinated by fusion power is
ancient. It's called 'rain'." -- Michael McClary, in alt.fusion
Maranatha! <><
John McKown
ee Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
[tsh009@it-johnmckown-linux tmp]$
[/transcript]
--
"Irrigation of the land with seawater desalinated by fusion power is
ancient. It's called 'rain'." -- Michael McClary, in alt.fusion
Maranatha! <><
John McKown
in, then you are doomed to disappointment. If you want
a replacement for "echo -n", you might try using a function (defined in
~/.bashrc) similar to:
function echo-n() { printf '%s ' "$@" | sed -r 's/ $//'; }
>
> Thanks & Regards
> --Jyoti
>
> --
There’s no obfuscated Perl contest because it’s pointless.
—Jeff Polk
Maranatha! <><
John McKown
another told me "echo is _evil_". You could use "printf" instead:
$ printf '%s\n' '-n'
-n
--
There’s no obfuscated Perl contest because it’s pointless.
—Jeff Polk
Maranatha! <><
John McKown
pvs'?
>
>
Probably a part of LVM (Logical Volume Manager),
VS(8)
System Manager's Manual
PVS(8)
NAME
pvs — report information about physical volumes
--
There’s no obfuscated Perl contest because it’s pointless.
—Jeff Polk
Maranatha! <><
John McKown
provides, and send patches to add said
> functionality to bash.
>
> [1] http://pubs.opengroup.org/onlinepubs/9699919799/utilities/make.html
> [2] https://www.gnu.org/software/make/
> [3] http://lists.gnu.org/archive/html/bug-make/
>
>
--
Heisenberg may have been here.
Unicode: http://xkcd.com/1726/
Maranatha! <><
John McKown
token is
> "/home/user")
>
>
>
> Repeat-By:
>
> Use $((~0)) (without spaces) to generate the error.
>
--
Heisenberg may have been here.
Unicode: http://xkcd.com/1726/
Maranatha! <><
John McKown
e
> by
> 6-7%.
>
Am I understand you correctly? You say that it __increases__ overall
execution time? That is, using rm as a builtin makes the script take more
time to execute (slows it down)?
>
> Tim
>
--
Heisenberg may have been here.
Unicode: http://xkcd.com/1726/
Maranatha! <><
John McKown
27;\0';
This would cause sample[-2] to be set to 0. Most likely it would set
part of fd to 0, but all that depends on the compiler.
Since fd is not in use at this point, the under run would not be noticed.
Regards,
-John
F_VENDOR='apple'
-DLOCALEDIR='/usr/local/Cellar/bash/4.3.42/share/locale' -DPACKAGE='bash'
-DSHELL -DHAVE_CONFIG_H -DMACOSX -I. -I. -I./include -I./lib
-I./lib/intl -I/private/tmp/bash20150913-75517-1rfmxak/bash-4.3/lib/intl
-DSSH_SOURCE_BASHRC
uname output: Darwin
wrote:
>
>
>
> As far as I'm aware, the inability to use symlinks owned by another user
> in a sticky directory is a security feature of some kernels. It helps to
> prevent symlink attacks.
>
>
>
>
--
Klein bottle for rent -- inquire within.
Maranatha! <><
John McKown
Hi,
I came across some unusual behaviour in bash using the '-c' parameter.
If I do the following:
bash -c "ping 127.0.0.1 > $HOME/console.log" &
This starts two processes bash and ping:
john 18038 17951 0 09:26 pts/14 00:00:00 bash -c ping 127.0.0.1 >
On Wed, Apr 13, 2016 at 6:45 AM, Pierre Gaston
wrote:
>
>
> On Wed, Apr 13, 2016 at 2:34 PM, John McKown > wrote:
>
>> On Wed, Apr 13, 2016 at 1:10 AM, Geir Hauge wrote:
>>
>> ...
>>
>>
>>> though printf should be preferred over echo:
&
ve used it myself in special cases, such as wanting leading zeros
(i=0;printf '%03d\n' "${i}";)
>
> --
> Geir Hauge
>
>
--
How many surrealists does it take to screw in a lightbulb? One to hold the
griffon and one to fill the bathtub with brightly colored LEDs.
Maranatha! <><
John McKown
section
echo "Congratulations, you decided to continue on!"
--
How many surrealists does it take to screw in a lightbulb? One to hold the
giraffe and one to fill the bathtub with brightly colored power tools.
Maranatha! <><
John McKown
ht you were "funnin"
him. But this page looks like it _might_ be an interesting start:
https://gist.github.com/sshaw/8017032
--
A fail-safe circuit will destroy others. -- Klipstein
Maranatha! <><
John McKown
Please reply to the list and not just me. There are a lot of helpful people
out there. Perhaps a "reply all"?
On Sun, Mar 6, 2016 at 5:26 PM, Val Krem wrote:
> Hi John,
> Thank you very much!
> I chose to put it as a function in my .bashrc.
> what happened is that
>
r is expected or me being stupid, or
> something else going on.
>
> Regards,
>
> Nick
> --
> Gosh that takes me back... or is it forward? That's the trouble with
> time travel, you never can tell."
> -- Doctor Who "Androids of Tara"
>
>
--
The man has the intellect of a lobotomized turtle.
Maranatha! <><
John McKown
man has the intellect of a lobotomized turtle.
Maranatha! <><
John McKown
;INSERT INTO file1 VALUES(\"" $1 "\"," $2 "," $3 ");"} '
file1.txt
awk 'NR > 1 {print "INSERT INTO file2 VALUES(\"" $1 "\"," $2 "," $3 ");"} '
file2.txt
cat < wrote:
>
>
&g
ntenance -- Jim Horning
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
hich we view adding a new wing
to a building as being maintenance -- Jim Horning
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
5 at 8:31 AM, Greg Wooledge wrote:
> On Mon, Dec 21, 2015 at 08:21:04AM -0600, John McKown wrote:
> > find . -maxdepth 2 -mindepth 2 -type f -name '*.csv' -o -name '*.txt' |\
> > egrep '^\./[0-9]' |\
> > xargs awk 'ENDFILE {print FILENAME &q
ing
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
in the APL language as my has [grin]. Hum, SQL set logic
might cause similar "damage".
--
Computer Science is the only discipline in which we view adding a new wing
to a building as being maintenance -- Jim Horning
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
ont of the pattern to
"anchor" it at the start of the line created by "find". OK, it probably
would have run correctly without it, but I'm a bit anal about such things.
On Mon, Dec 21, 2015 at 7:45 AM, John McKown
wrote:
> Sorry about delay, for some reason Google pu
uff" on my tablet, not my PC
(which is where I read most of my email - can't stand email on tablet).
On Sun, Dec 20, 2015 at 8:12 PM, Krem wrote:
>
> John,
>
> After trail and error the following works for me but still has to be
> refined.
>
> find . -type f
to the order you wanted
it to be in.
--
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
store is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
Domain Name Registrar
>\o/ Hosting For Geeks and more...
> Gandi.net No Bullshit !
>
>
--
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
here at home.
--
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
= ?
+++ exited with 0 +++
--
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
Thanks, Chet!
From: Chet Ramey
To: John Wiersba ; "bug-bash@gnu.org"
Cc: chet.ra...@case.edu
Sent: Thursday, November 26, 2015 12:41 PM
Subject: Re: OLDPWD unset when bash starts
On 11/18/15 2:44 PM, John Wiersba wrote:
> Why does bash clear OLDPWD when a ch
PE='x86_64' -DCONF_OSTYPE='l$
uname output: Linux john-mint-mate-17 3.13.0-37-generic #64-Ubuntu SMP Mon Sep $
Machine Type: x86_64-pc-linux-gnu
Bash Version: 4.3
Patch Level: 11
Release Status: release
Description:
Why does bash clear OLDPWD when a child script is started?
OLDPWD is exported a
1.2(1)-release (x86_64-redhat-linux-gnu)
Can bash be fixed to preserve the value of any OLDPWD in its initial
environment, like it does with PWD?
Thanks!
-- John Wiersba
d Al. Great guys to look up to.
>
--
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
echo -n "${x}" > sample.first #put it in file
echo -n "${x}" > sample.second # do it again
}
I'm really not sure if the -n switch is the right thing to do on the
"echo" commands or not
--
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
n of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
ondition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
*, char *, int));
SHELL_VAR is a struct declared in variables.h.
So passing it const char * should be causing problems.
Regards,
-John
On 4/19/15, 5:24 PM, "Chet Ramey" wrote:
>On 4/17/15 4:55 PM, John Fremlin wrote:
>> Did some benchmarks, for the while true; do (:) & (:); done simple
>>example
>> this goes from 215 to 313 iterations/s, and changes sys+user CPU from
>>152%
>>
Did some benchmarks, for the while true; do (:) & (:); done simple example
this goes from 215 to 313 iterations/s, and changes sys+user CPU from 152%
to 45%
Any long running bash script will tend to exhibit this issue --
On 4/15/15, 5:59 PM, "John Fremlin" wrote:
>Over tim
On 4/15/15, 6:35 PM, "Chet Ramey" wrote:
>On 4/14/15 12:54 AM, John Fremlin wrote:
>> Bash instances running in loops get slower over time, as the bgpids data
>> structure grows. Here is a small patch to alleviate one issue :)
>>
>> The jobs.c:bgpids data
it is dominated by copying page table entries on fork
user 94.14
sys 657.74
Without patch most time is spent in bgp_* functions
user 1637.16
sys 1337.58
Number of iterations of this busy loop is much higher with the patch too :)
Any feedback much appreciated!
From: John Fremlin
Date: Mond
structure. This has a *huge* performance implication for
long running bash processes that naturally spawn many sub-shells over their
life, and can gradually slow down.
First set ulimit -u 3 (this is used by bash to determine the size of bgpids)
With the patch:
john@dev:~/Programs/bash$ (time
ocumented that aliases
are not expanded when quoted.
--
If you sent twitter messages while exploring, are you on a textpedition?
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
t;
> Expected:
>
> $ "a nonexistent command name with spaces"
> bash: a nonexistent command name with spaces: command not found...
>
--
If you sent twitter messages while exploring, are you on a textpedition?
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
ot; (at least to
me) files.
>
>
> --
> Eric Blake eblake redhat com+1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
--
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
could see the top command.
> Thousands of bash were being opened, I would report this bug.
>
> One question, I tried to fix myself but I did not really bash the error
> files.
>
> In this case how it could contribute?
>
> Thank U
--
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
ontribute?
>
> Thank U
--
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
On Tue, Feb 24, 2015 at 2:10 PM, Chet Ramey wrote:
> On 2/24/15 1:32 PM, John McKown wrote:
> > I run with "set -o noclobber". I know to use >| to redirect stdout and
> > overwrite an existing file. But I often want to redirect both stdout
> > and stderr to
PLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Yes, I'm a lazy typist. :-)
--
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
PLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Yes, I'm a lazy typist. :-)
--
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
While compiling Bash, I couldn't help but notice that all over GNU's website it
is spelled with a capital B. However, when I tried to compile Bash, I noticed a
message that said "GNU bash, version 4.3.30(1)-release (i686-pc-linux-gnu)" in
a box surrounded by stars. Why is the B not capitalized h
ld probably be more clear.
No need to return a pointer to a static empty string.
Regards,
-John
wb8tyw@qsl.network
Thanks for the clarification. I had not seen that e-mail and was
expecting the parse.y changes would result in y.tab.c being regenerated
in the build.I have since run across a system with an earlier
version of Bison that cannot handle the latest parse.y.
Thanks again.
-- John
On 10/2
I am curious; why does Bash 4-3 patch 28 contain patches for y.tab.c.
Is this really what was intended.
-- John Wolfe Xinuos, Inc.
e not current.
Regards,
-John
wb8tyw@qsl.network
On 01/11/2014 06:18 PM, Chet Ramey wrote:
You don't want the value generated in all cases. This has an effect on
some variables: RANDOM, for example. I believe the current behavior is
preferable.
I guess I don't understand why returning stale values for the dynamic variables
under any circum
On 01/11/2014 04:55 PM, Chet Ramey wrote:
On 1/10/14, 6:06 PM, John R. Graham wrote:
Some of the automagically created special array variables (GROUPS and DIRSTACK
for soer; perhaps others) appear to not be fully initialized. Their values
don't appear correctly in some corner cases
0" [1]="11" [2]="14" [3]="18" [4]="19" [5]="20" [6]="27"
[7]="35" [8]="80" [9]="85" [10]="100" [11]="250" [12]="995" [13]="996"
[14]="10" [15]="1003" [16]="1013")
~ $ # Hmm again. Now shown correctly.
~ $ exit
exit
So far the Bash source code is a somewhat abstruse to me so I thought I'd ask
for a little help.
Thanks in advance.
- John
1 - 100 of 278 matches
Mail list logo
