Mac OS
___
Follow-up Comments:
---
Date: Thu 04 Apr 2024 09:57:30 PM UTC By: Richard Waite
I noticed that BASHPID expands to a different PID value compared to the value
outside of it.
pesize.h:
+${DEFDIR}/pipesize.h: $(BUILTINS_LIBRARY)
@(cd $(DEFDIR) && $(MAKE) $(MFLAGS) pipesize.h ) || exit 1
$(SDIR)/man2html$(EXEEXT): ${SUPPORT_SRC}/man2html.c
Cheers,
Richard
There was discussion on Twitter today
(https://twitter.com/PttPrgrmmr/status/1132351142938185728) about how the
Bash manual appears to not be indexable by search engines.
https://www.gnu.org/software/bash/manual/bashref.html
redirects to
That was exactly it. I kept thinking of openlog as opening a pointer to a
file.
Thanks, all for you insights.
On Aug 23, 2016 9:44 AM, "Chet Ramey" <chet.ra...@case.edu> wrote:
> On 8/22/16 4:10 PM, Richard Lohman wrote:
> > Hey all:
> >
> > In my attempts
Hey all:
In my attempts to log commands from bash via syslog, I've come upon a snag.
The output is of the form:
Mmm dd HH:MM:SS hostname -bash: command
This was obtained by uncommenting the define in config-top.h and changing
the call to syslog in bashhist.c as such:
Hi, all:
I've seen this topic come up a time or two, but the responses don't quit
match my situation. ...and, if there's a better place to post, please do
feel free to let me know.
I need to log all commands entered at the shell for all users on a host
(business need, not technical). There is a
/divbr =
class=3D/div/body/html=
- --Apple-Mail=_51A7C042-5A82-40D5-B8FA-5586341517FA--
- --Apple-Mail=_0FFE68EB-40A8-4B26-B362-C6D78F1EEECE--
--- End of forwarded message ---
--
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org
steps to produce
hide cursor
setterm -cursor off
call the bash built-in read command as follows: silent, wait 1 second, read
1 character to variable KEY
read -s -t 1 -n 1 KEY
while the read command is in a loop, control + c is trapped successfully
and the cursor is un-hidden
setterm
Chet Ramey chet.ra...@case.edu writes:
On 3/20/14 12:41 AM, Richard Tollerton wrote:
I suppose that this change in behavior makes array variables more
consistent with normal variables, but I couldn't find anything in
CHANGES which obviously relates to this, so I'm not sure if this is a
bug
couldn't find anything in
CHANGES which obviously relates to this, so I'm not sure if this is a
bug or not.
Was I always mistaken in figuring that declaring an array also
initialized it?
--
Richard Tollerton rich.toller...@ni.com
,
Richard
This is probably not a good thing to be doing in the first place (I ran
into this before realizing that GROUPS was a special variable):
#!/bin/bash
crashy () { local -a GROUPS=(a b); }
crashy
But it probably shouldn't be doing this (tested in bash 4.2.42 on
archlinux x86_64, and bash 4.2.10 on
.]
Best wishes,
Richard
Message: 4
Date: Wed, 14 Mar 2012 13:40:36 -0600
From: Bob Proulxb...@proulx.com
To: bug-bash@gnu.org
Subject: Re: compgen is slow for large numbers of options
Message-ID:20120314194036.ga12...@hysteria.proulx.com
Content-Type: text/plain; charset=us-ascii
Richard
in which we are using completion on package-management.
In this case, the number is 43031.
I hope this is helpful.
Richard
this. This is already how
Automake does things; the bug comes down to bash's build system not
following existing convention. It's not reasonable to have to duplicate
CFLAGS in LDFLAGS to avoid the reported link error.
--Daniel
--
NAME = Daniel Richard G. _\|/_Remember, skunks
MAIL = sk
or mismatched ABI for -ldl
Fatal error.
gmake[1]: *** [mkbuiltins] Error 1
gmake[1]: Leaving directory `/tmp/bash-4.2.build/builtins'
gmake: *** [builtins/builtext.h] Error 1
The attached patch (against the 4.2 source) fixes the problem for me.
--Daniel
--
NAME = Daniel Richard G
]]; then
echo OK 1: $b -- $myfile
fi
done
# Example 2
myfolder=/Users/myuser/
unset b
for b in $myfolder*; do
if [[ $b == $myfile ]]; then
echo OK 2: $b -- $myfile
fi
done
-
Richard Taubo
Mike Stroyan wrote:
On Tue, Sep 22, 2009 at 02:36:30AM -0700, thahn01 wrote:
Hello, If I try something like:
$ touch a.c b.c A.c
$ ls [a-z]*.c
a.c A.c b.c
then I get A.c in the output, even if no capital letters are to be found.
The [a-z] range expression matches characters between a
of the builtin takes about 11
seconds, while 1E4 invocations of the standalone binary
takes 17 seconds. The builtin echo is therefore about
150 times faster.
What do you think?
Richard
functionally identical to
/bin/grep.
Then I could make a system-wide change, replacing the regular bash shell
with the fat-bash, and still have everything work...
Richard
André Johansen wrote:
Description:
When using tab-completion, Bash crashes.
I'm using the bash_completion package from
http://www.caliban.org/bash/index.shtml#completion.
...
Repeat-By:
Press tab to get a completion; if Bash enters a programmed completion
(i.e. not a simple file
Chris F.A. Johnson-3 wrote:
This completion function worked in previous versions, but fails in
bash4.0 when I press TAB:
_cpsh() {
COMPREPLY=( `
cd $HOME/scripts || return 3
printf %s\n ${COMP_WORDS[$COMP_CWORD]}*-sh`
)
COMPREPLY=(
Chet Ramey wrote:
Interesting. This happens only on Linux. FreeBSD, MacOS X, and Solaris
all interrupt and return to $PS1.
Chet
Actually, this was happening for me on Solaris too, so looks like not just a
Linux thing.
But your patch fixed the issue on Solaris as well.
Richard
into the middle.
What do you think?
Richard
P.S. I am sure lots of people will complain (correctly) that Goto is
considered harmful. I'd agree that, in most cases, it is. But in some
cases, such as the above, it's quite useful. Maybe the feature could be
called debug-goto in order to emphasise
the point.
Incidentally, if this is useful, it would be nice to support the
rather prettier counterpart to the operator, and permit this usage:
$TEXT grep -o 'hello'
What do you think?
Regards,
Richard
sure that
variables defined at [a] can be made to still exist at [b] ?
Thanks,
Richard
read to iterate over its standard input
without creating a subshell? If it's of interest, the actual part of
the script I use is below - the aim is to parse the output of ffmpeg
-formats to see whether certain codecs are supported by that build.
Regards,
Richard
Thank you. That's a really neat solution - and it would never have
occurred to me. I always think from left to right!
Richard
Paul Jarc wrote:
Richard Neill [EMAIL PROTECTED] wrote:
the aim is to parse the output of ffmpeg -formats to see whether
certain codecs are supported by that build
Dear All,
When using read, it would be really neat to be able to pre-fill the form
with a default (or previous) value.
For example, a script which wants you to enter your name, and thinks
that my name is Richard, but that I might want to correct it.
Alternatively, this would be useful within
.
# de
i.e. ${string:x:y}
* returns the string, from start position x for y characters.
* but, if x is negative, start from the right hand side
* if y is negative, print up to (the end - y)
Thanks very much,
Richard
Jan Schampera wrote:
Richard Neill wrote:
$ echo ${stringZ:2: -1} #Wish: start at 2, read till
ERROR#1 before the end. i.e.
# cde
$ echo ${stringZ: -3: -1}#Wish: start 3 back, read till
ERROR
with examples.
bug-example.sh demonstrates the problem.
bug-example2.sh is where bash gets it right.
Thanks very much,
Richard
[EMAIL PROTECTED] ~]$ cat bug-example.sh
-
#!/bin/bash
#This is an example of bash being unhelpful
Chet Ramey wrote:
Richard Neill wrote:
Dear All,
In some cases, bash gives exceptionally unhelpful error messages, of the
sort Unexpected end of file. This is next-to-useless as a debugging
aid, since there is no way to find out where the error really lies.
For better or worse, bash
Bob Proulx wrote:
Richard Neill wrote:
b)Consistent with other cases, where bash does give warnings. For example:
$ X=$((3+078))
bash: 3+078: value too great for base (error token is 078)
$ echo $?
1
That is not really a comparable case. The problem there is that the
leading zero
message would be allowed.
The error message would be:
a)Most helpful to the user (least surprise)
b)Consistent with other cases, where bash does give warnings. For example:
$ X=$((3+078))
bash: 3+078: value too great for base (error token is 078)
$ echo $?
1
Regards,
Richard
for overflow...
but I'd suggest this represents a bug, not a feature.
Regards,
Richard
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Paul Jarc wrote:
Can you explain what was unsatisfactory about the alternatives given
in the FAQ, so we have a better idea of what would be acceptable?
Here's one possibility:
... | { while ...; do var=...; done; use $var; }
Thanks for the reply, and a possible solution.
The
Thank you Paul, Andreas and Kevin.
Both the here document solution and the Process substitution solution both
work well. I haven't had a good look to see the subtle differences between
the two yet.
Thank you again.
--
View this message in context:
Other than lsof is there a way to determine what file descriptors are
open?
Thanks
Richard
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Dear Grzegorz,
Thanks for your helpful reply.
Grzegorz Adam Hankiewicz wrote:
On 2006-12-27, Richard Neill [EMAIL PROTECTED] wrote:
1)substr support for a negative length argument.
For example,
stringZ=abcdef
echo ${stringZ:2:-1} #prints cde
i.e. ${string:x:y}
returns the string, from
.
Richard
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
Just curious: why is it that your version displays 6 within parenthesis,
whereas mine displays 2?
Shame on me. Decided to stop being lazy and get the answer from the
source: man bash... ;)
Curiosity satistied: please kindly disregard.
Richard
Have just read the archives... ;) Forwarding to the list accordingly!
-- Forwarded Message --
Subject: Re: Bash-3.1.17 gets lost looking for end of string in certain
contexts
Date: Wednesday 03 May 2006 22:36
From: Richard [EMAIL PROTECTED]
To: Eric Blake [EMAIL
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu'
-DCONF_VENDOR='pc' -DLOCALEDIR='/mnt/STG1/share/locale'
I have Linux built mostly from source. I upgraded to GLibc-2.3.6 and
BinUtils-2.16.1. I am currently using GCC-3.4.4 due to some problems
with GCC-4.0.2. I have applied all 16 Bash-3.0 patches.
Bash builds fine using shared libraries, but when I tried to upgrade my
statically linked shell
Are there any good bash_profile links,
of showing how to create a good simple bash_profile,
that would also include $PATH.
Thanks -
Richard
___
Bug-bash mailing list
Bug-bash@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-bash
46 matches
Mail list logo