Re: stty settings override ~/.inputrc?

Chet Ramey <[EMAIL PROTECTED]> wrote: > Readline, beginning with version 5.0, reads the stty special character > settings and binds them to their readline equivalents each time > readline() is called. It reads ~/.inputrc once per `program'. Suggestion: when reading .inputrc, update the stty setti

Re: bash expr problem/bug... 0$val

[EMAIL PROTECTED] wrote: > # a=500; b="0$[a]"; c=$[b]; echo -e "a: $a\nb: $b\nc: $c\n" > a: 500 > b: 0500 > c: 320 man bash, under ARITHMETIC EVALUATION: Constants with a leading 0 are interpreted as octal numbers. paul __

shared library installation

readline/shlib/Makefile uses INSTALL_DATA to install shared libraries. INSTALL or INSTALL_PROGRAM would seem more appropriate; at least on GNU/Linux, gcc creates shared libraries with the execute bit set, and ldd warns if it is not set. paul ___ Bug-b

Re: failure in pipeline not reflected in $?

[EMAIL PROTECTED] wrote: > If a command in a pipeline of commands fails, there appears to be no > way of knowing this. Check the man page regarding the PIPESTATUS array. paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mai

Re: pipeline outlives TERMed bash

Denis Vlasenko <[EMAIL PROTECTED]> wrote: > The problem is that svc -d (or manual kill -TERM) > kills bash but nmeter and logger continue to run, > until I kill nmeter manually. It's best not to put a long-running pipeline in a daemontools run script, for just this reason (among others). Instead,

Re: ansi escape sequences in prompt mess-up the command prompt

Antonis <[EMAIL PROTECTED]> wrote: > Using ansi escape sequences in the prompt causes Bash to incorrectly > calculate the available width of the terminal and messes-up the command > prompt when a certain amount of characters are typed in. See entry E3 in the bash FAQ. paul

Re: programmable auto completion with embedded ":" not working?

"fabien" <[EMAIL PROTECTED]> wrote: > when programming an auto-completion with embedded ":" in the > complete names, the auto-completion does not look good. By default, ":" is treated like whitespace for completion, to help when setting variables like $PATH. Check the man page for COM

Re: error in math args?

Scott Dylewski <[EMAIL PROTECTED]> wrote: > I get an error when running: > echo $(( 008 / 2 )) Numbers starting with 0 are interpreted as octal, and so can only use digits 0-7. You'll have to strip off the leading zeros to make the number be interpreted as decimal. paul __

Re: HERE document mystery

"Com MN PG P E B Consultant 3" <[EMAIL PROTECTED]> wrote: > echo THIS DOES NOT WORK > foo=$(cat exp_test < V=1234 > abcd > BAD 0. Since you passed a file name to cat, it will ignore stdin. 1. Since the here-document belongs to the command in $(), the here-document must also be entirely inside $

Re: Can't get the set-user-id bit to work

Sebastian Tennant <[EMAIL PROTECTED]> wrote: > I have a 3-line script; foo: The setuid bit works only for binaries, not scripts. This is a limitation of the kernel, necessary for security. > A cron.daily script handles mandb. I elected to install it with the > set-user-id bit set, as you can se

Re: Can't get the set-user-id bit to work

Sebastian Tennant <[EMAIL PROTECTED]> wrote: > OK, but mandb _is_ a member of the root group, so shouldn't it be able > to write files in /tmp with the permissions as they stand? No, you'd have to make it setuid to root, or setgid to the root group. The user/group associations in /etc/passwd and

Re: "echo: write error: Broken pipe" even when DONT_REPORT_SIGPIPE set

Chet Ramey <[EMAIL PROTECTED]> wrote: > `echo' now displays an error message on write errors. In the case of a SIGPIPE trap, is it intended that echo sees EPIPE before the SIGPIPE handler runs? paul ___ Bug-bash mailing list Bug-bash@gnu.org http://l

Re: Conditional expression problem: both "-a file" and "! -a file" return true

Eric Blake <[EMAIL PROTECTED]> wrote: > But the RATIONALE (XCU line 35443) states that "The ! operator has higher > precedence than the -a operator, and the -a operator has higher precedence > than the -o operator." Therefore, when -a is defined as a unary operator, > an XSI compliant test is requ

Re: can't expand after colon

Dan Jacobson <[EMAIL PROTECTED]> wrote: > Must one use \: to make this work? That, or adjust $COMP_WORDBREAKS to not include ":". paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

Re: Possible bash bug when dealing with CR/LF in variable expansion

"Johannes Thoma" <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED]:~/bash/bash-3.1$ zak=`printf '\x0d\x0a'` As documented in the man page under "Command Substitution", this strips off any trailing newlines from the program's output before assigning the variable's value. So zak contains only a carria

Re: exit somtimes not exit's the script

[EMAIL PROTECTED] wrote: > a exit inside a loop inside a pipe exits's the loop and not the > script. may bee a error. This is normal. Each element of a pipeline is run in a child process. paul ___ Bug-bash mailing list Bug-bash@gnu.org h

Re: problem ? bug ?

[EMAIL PROTECTED] wrote: > [kaneda<-ogorasek]~$if [ ! -a /etc/passwd ] ; then echo si ; fi -a is used as a binary "and" operator here. The expressions "!" and "/etc/passwd" are nonempty strings, so both are considered true, and the overall result is true. paul

Re: eval in functions in pipelines doesn't set variables globally

[EMAIL PROTECTED] wrote: > Normally, the eval builtin used in functions to set variables > makes these variables available globally otutside the function. > However, when the function gets input from a pipline, the variables > are set only locally. Read the bash FAQ, entry

Re: BUG: ls -ld directory/

G C McNeil-Watson <[EMAIL PROTECTED]> wrote: > If you do an > > ls -ld directory/ > > for some existing directory then the output contains TWO trailling > slashes: > > drwx-- 2 pypgcm users 4096 Aug 16 2005 directory// > > The directory and the first slash appear in blue on my terminal, tra

Re: trap handler scope wrong?

Phillip Susi <[EMAIL PROTECTED]> wrote: > Chet Ramey wrote: >> That's about right, but you need >&3 in the trap command. > > I did have > &3 in the trap command, see? You have "> &3". You need ">&3", without a space. > I'm a bit worried though about hard coding the fd 3. Is there a way > to get

Re: How to suppress async messages for background jobs

Francesco Montorsi <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED]:~$ kwrite & > =>[1] 20986 > [EMAIL PROTECTED]:~$ > =>[1]+ Donekwrite > [EMAIL PROTECTED]:~$ > > is there a way to tell bash not to print those lines marked with => ? If you don't need to refer to the proce

Re: document that echo can't be given a NULL

Dan Jacobson <[EMAIL PROTECTED]> wrote: > No way to hand echo or /bin/echo a NULL. For /bin/echo, that's because execve() uses null-terminated strings. For bash's builtin echo, it could be done, but then it would be inconsistent with external commands, which might be surprising. paul _

Re: Using variables in variables names

"Dirk H. Schulz" <[EMAIL PROTECTED]> wrote: >> ac=12 dings$ac=wasannersder >> -bash: dings12=wasannersder: command not found Variable names in assignments are not subject to expansion. So since "dings$ac", as-is, does not fit the syntax for variable names, it isn't treated as an assignment. Thi

Re: Using variables in variables names

"Dirk H. Schulz" <[EMAIL PROTECTED]> wrote: > Paul Jarc schrieb: >> ac=12 eval "dings$ac=wasannersder" > > And how do I reference it then? ac=12 eval "value=\$dings$ac" echo $value Or: ac=12 name=dings$ac echo ${!name} paul _

Re: Question about variables and for loop

Bob <[EMAIL PROTECTED]> wrote: > XXX='a "b c" d' > for x in $XXX ; do > echo $x > done XXX='a "b c" d' eval "set $XXX" for x in "$@" ; do echo $x done If the first element in XXX might start with "-", then it takes a little more work to ensure it isn't misi

Re: Grouped pipeline clobbering question

Phillip Susi <[EMAIL PROTECTED]> wrote: > cat file | ( head --lines=1 ; sed -e x ) > > I thought that head should consume the first line from the pipe, leaving > the rest queued for sed to consume, but this does not seem to be the > case. head may read an arbitrary amount of data from the pi

Re: bash ignoring .inputrc (or am I dumb)

William Yardley <[EMAIL PROTECTED]> wrote: > I would still like to know if there's a way to bind ^W to > backward-kill-word within bash, so if anyone has suggestions, I'd > appreciate them. Check out the "bind" builtin command in the man page or "help bind". paul __

Re: pattern matching: range expression

Wolf-Rainer Novender <[EMAIL PROTECTED]> wrote: > e.g. ls [A-Z]* should yield in all names starting with capital letters. > Does not work! I get >>all<< names! http://www.gnu.org/software/coreutils/faq/#Sort-does-not-sort-in-normal-order_0021 paul __

Re: Selinux bash prompt decorations

Steve Grubb <[EMAIL PROTECTED]> wrote: > On Tuesday 04 April 2006 15:51, Chet Ramey wrote: >> How about commands whose output may be assigned to shell variables? > > Yes, they can be acquired in a number of ways. But what we are trying to do > is > set things up so that people using this in a cla

Re: test -f with no args is true

Charlie Bennett <[EMAIL PROTECTED]> wrote: > Is this expected behavior? > > [EMAIL PROTECTED] .ssh]# [ -f ] > [EMAIL PROTECTED] .ssh]# echo $? > 0 Yes. A single argument is considered true if it is not the mepty string, even if it happens to coincide with the spelling of an operator. This is ho

Re: unwanted expansion of variable with nested strings

Mike Frysinger <[EMAIL PROTECTED]> wrote: > $ foo="a b c" > $ gawk 'BEGIN {foo="'${foo}'"}' > gawk: BEGIN {foo="a > gawk:^ unterminated string This is normal. man bash: # Word Splitting # The shell scans the results of parameter expansion, command substitu- # tion, an

Re: unwanted expansion of variable with nested strings

Mike Frysinger <[EMAIL PROTECTED]> wrote: > On Thursday 04 May 2006 00:44, Paul Jarc wrote: >> What do you mean by "fail"? What do you want to happen in this case? > > i meant gawk hates it ... not bash Ok, and what about the second question? What are you trying

Re: Selinux bash prompt decorations

Steve Grubb <[EMAIL PROTECTED]> wrote: > Its not poor practice to make something usable for people. ... > For the moment, we are going the route of doing this via `id -Z`. But I > thought there was a common problem across secure distributions that we could > create a standard for. TSOL could link

Re: How to use [[ string =~ regexp ]]?

Peter Volkov <[EMAIL PROTECTED]> wrote: > $ [[ "string" =~ "[a-z]" ]] && echo something > something [a-z] matches only one charater, but the pattern is not required to match against the entire string. You can force it to match the whole string by using "^" to anchor the pattern to the beginning o

Re: here document and STDIN

"Cai Qian" <[EMAIL PROTECTED]> wrote: > For following code, > > sh < read > EOF > > I have no idea why will not block. The "read" command reads from the shell's stdin, which is the here document. At the point where the "read" command is executed, the shell has already read the "read" comman

Re: here document and STDIN

I wrote: > sh < read <&3 > EOF Sorry, that first line should be: sh 3<&0

Re: here document and STDIN

"Cai Qian" <[EMAIL PROTECTED]> wrote: > The information is helpful. The problem by using > > perl -e ' >X > ' > > is that there seems no way to using single quota in Perl code any more. It's not very concise, but you can do this: perl -e ' ... '\'' ... ' >From the shell's point of vi

Re: EOF does not work in echo

"Cai Qian" <[EMAIL PROTECTED]> wrote: > It suggests that "cat" has not seen EOF (004) generated by echo. The character 004 is not EOF. When typing at a terminal which is set to "cooked" mode, you use the keystroke control-D to tell the terminal driver that it should send EOF to the program readin

Re: Aliases fail in command substitution in noninteractive mode.

[EMAIL PROTECTED] wrote: > Aliases don't work correctly in command substitution when in > noninteractive mode. They do work when in interactive mode. man bash, under "ALIASES": Aliases are not expanded when the shell is not interactive, unless the expand_aliases shell

Re: Bash expansion nuance or bug?

Linda Walsh <[EMAIL PROTECTED]> wrote: > Two aliases: >alias ls='ls -CFG --show-control-chars --color=tty ' >alias dir='ls' > > If I type "ls dir" (created a test dir called dir), I > get: >"ls dir" > I get: >ls: ls: No such file or directory. man bash, under ALIASES: # If the last

Re: while do done has problems with global variables

[EMAIL PROTECTED] wrote: >ls -1 | while read f; do Read entry E4 in the bash FAQ. paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

Re: terminating lines with accidental eof

[EMAIL PROTECTED] (Martin Wheatley) wrote: > (ie commands are only executed when the user hits enter and NOT > executed when an I/O error occurs on the input stream). EOF is not an error. If there is an error, then certainly bash should not execute an partial command it has buffered, but that won

Re: automatic code generation

box <[EMAIL PROTECTED]> wrote: > void ${NAME}Panel::showEvent(QShowEvent *e) { > ...code > } > > I want to be able to run my script, have it read the contents of the files > while replacing ${NAME} with a variable that is defined elsewhere in my > script. NAME=... eval "cat < output-file

Re: Python and Bash

"Andrew Kezys" <[EMAIL PROTECTED]> wrote: > So, when I'm running the shell script that calls on this python script > and end it with ctrl-c, it only ends the shell script, and not the > python script, which continues putting serial data to a file. Ctrl-C should be sending SIGINT to both bash and p

Re: !* goofs here-strings

mwoehlke <[EMAIL PROTECTED]> wrote: > I thought the syntax was only two '<'s? "<<" gives you a here-document. "<<<" gives you a here-string. Check the man page for details. paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman

Re: null command and parameter expansion for "Display error if null or unset"

"Dave Rutherford" <[EMAIL PROTECTED]> wrote: > On 7/31/06, Poor Yorick <[EMAIL PROTECTED]> wrote: >> : ${FAKEVAR?} || echo hello > > Try this and then run your script: > > export FAKEVAR="echo This could have been rm -rf $HOME" That won't do anything. The contents of $FAKEVAR, if any, are just pa

Re: null command and parameter expansion for "Display error if null or unset"

mwoehlke <[EMAIL PROTECTED]> wrote: > Poor Yorick wrote: >> The following line does not perform the "echo" command. >> : ${FAKEVAR?} || echo hello > > What you probably want is: > [ "$FAKEVAR" ] || echo hello That doesn't distinguish between an unset variable and a variable set to an empty value.

Re: unable to capture return value using backticks and local

"Adam Monsen" <[EMAIL PROTECTED]> wrote: > foo() > { >local TICKED=`false` >echo RV: $? > } > > foo > # prints "RV: 0", but I would expect "RV: 1" You get 0 here because that's the status from the "local" command. To get the status from a backtick command, you need the assignment to be al

Re: Bug with 'test' built-in.

John Wenker <[EMAIL PROTECTED]> wrote: > The following construct _always_ evaluates true, regardless of > whether the file exists or not. > > if [ ! -a file ]; then > echo "This line always prints no matter what." > else > echo "This line never

Re: Bug with 'test' built-in.

mwoehlke <[EMAIL PROTECTED]> wrote: > I *know* '! [ -a file ]' is not portable. I tried to use it in some > script, somewhere, at some time, and it was sometimes treated as history > expansion. Quoting the "!" would take care of that particular problem, but there are some older shells, like Sola

Re: Espace characters need -e, wrong behaviour

Nico Schottelius <[EMAIL PROTECTED]> wrote: >Please remove the need for -e and ignore -e for a some time, until >it vanished from user programs. There is too much variation among implementations of "echo" to ever hope for uniformity. Different implementations all react differently to opti

Re: Job queing

Mårten Segerkvist <[EMAIL PROTECTED]> wrote: > i. e. being able to split a one-liner like: > > command1 && command2 && command3 > > into several, separate command lines: You can write that one-liner on multiple lines: command1 && command2 && command3 paul __

Re: functions and set -e

Greg Schafer <[EMAIL PROTECTED]> wrote: > #!/bin/sh > set -e > > func () { > false && echo false > true && echo true > false && echo false > } > > func > > echo done > > > It never echoes "done" because func() returns 1. That's the correct behavior. The last "false" within the function does

Re: functions and set -e

Greg Schafer <[EMAIL PROTECTED]> wrote: > Thanks for trying to clarify it for me. Let me put it another way: If I > change Line 1 above to an if/then style statement instead of "&&" ie: > > if false; then echo false; fi > > it works exactly like I'd expect instead of the counter-intuitive behavio

Re: incorrect brace expansion when using default values

Mike Frysinger <[EMAIL PROTECTED]> wrote: > this little bit of code doesnt work right: > foo() { echo "${1:-a{b,c}}" ; } Brace expansion happens before parameter expansion (man bash, EXPANSION). So the first "}" ends the parameter expression, and the second "}" isn't special. The result of param

Re: completion inconsistencies involving symlinks

"Kartik K. Agaram" <[EMAIL PROTECTED]> wrote: > I conclude that the 'logical path' is maintained only by the shell, not in > the filesystem. If I'm right, then the whole notion of logical path is a > leaky abstraction honored only by 'cd -L' (are there any others?). I would > really like to

Re: completion hosed by :

"Ilya N. Golubev" <[EMAIL PROTECTED]> wrote: > If `0:0', `0i', `0.tar' files exists in current directory, `0:' is > completed with `0\:0' to obtain `0:0\:0'. Using 3.0.16 or 3.1.17, only "0" is added by completion for me. So I end up with "0:0", and further TABs show me the three possible matches

Re: make bash use authentication type?

Jaqui Greenlees <[EMAIL PROTECTED]> wrote: > In a recet discussion about ssh, the ida was put forth > to get opnssh to export a variable that defines the > authentication method used. The idea being to limit > access to su use to only those authenticating through > a public / privat key pairing. >

Re: process null-delimited input

"Nathan Coulter" <[EMAIL PROTECTED]> wrote: > cat <&0 | xargs -0 -n2 bash -c ' > This is beside the point, but "<&0" is a no-op and be removed. Same for "cat |". paul ___ Bug-bash mailing list Bug-bas

Re: [BUG][bash][auto completion] if COMPREPLY contents ":" auto completion doesn't work properly

Vasily Tarasov <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] $ myfunc > Press tab once: > [EMAIL PROTECTED] $ myfunc qwe:o > Press tab secondary: > [EMAIL PROTECTED] $ myfunc qwe:qwe:o You can work around this by removing : from $COMP_WORDBREAKS. Ii looks like a bug, since the : inserted by comp

Re: ...Limitation?

mwoehlke <[EMAIL PROTECTED]> wrote: > I am trying to figure out how to run a command and pipe the output > through tee, and then check the status of the original command. This uses a bash-specific feature: cmd > >(tee file); status=$? This should work on any sh: exec 3>&1 && status=`exec 4>&1 &&

Re: [BUG][bash][auto completion] if COMPREPLY contents ":" auto completion doesn't work properly

Chet Ramey <[EMAIL PROTECTED]> wrote: > Vasily Tarasov wrote: > >> I suppose I've found a bug; > > I need to make this part of the FAQ. The `:' is special to readline: it > splits words for the word completion code. That explains some of what's going on in this case, but not all. For the first

Re: [BUG][bash][auto completion] if COMPREPLY contents ":" auto completion doesn't work properly

Chet Ramey <[EMAIL PROTECTED]> wrote: >> Chet Ramey <[EMAIL PROTECTED]> wrote: >> Also, after two tabs, we have "qwe:qwe:o", but further tabs don't add >> any more "qwe:"'s for some reason I don't understand. > > Because the colon is still a word break character, and readline passes `o' > to the co

Re: no parameter expansion and no special meaning to control operator

Lorenzo Viali <[EMAIL PROTECTED]> wrote: > eval "\"$CMDFILE\" $list" > because i need $CMDFILE to receive more than > one argument; but what happens is that if in the > script's option's arguments, there are substrings like > $i, those variable are expanded That will also happen wi

Re: How to detect bash?

mwoehlke <[EMAIL PROTECTED]> wrote: > And since when does '#! /bin/bash' mean "use whatever 'bash' you > find in $PATH"? Silly me, I thought it meant "use '/bin/bash'". Dave did say "hash-bang", but he didn't say "#! /bin/bash". Possibly he's thinking of "#!/usr/bin/env bash", which should do wha

Re: Tilde expansion not performed during variable evaluation

Karen Etheridge <[EMAIL PROTECTED]> wrote: > Tilde expansion is not being performed when variables are being evaluated. That's normal, documented behavior. man bash, EXPANSION: The order of expansions is: brace expansion, tilde expansion, parameter, variable and arithmetic expan

Re: botched configure check for /dev/stdin

Chet Ramey <[EMAIL PROTECTED]> wrote: > Hardcoding `/bin/test' is a tricky business: How about "(exec test ...)"? Or "env test ..."? paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

Re: Why is this executed inside a subshell?

"Com MN PG P E B Consultant 3" <[EMAIL PROTECTED]> wrote: > But it seems that within a $(...), even shell functions are executed > in a child process. Is this supposed to work that way? Yes. $() passes the output of the inner command to the outer shell via a pipe, with the inner command running i

Re: mkfifo and tee within a function

Nathan Coulter <[EMAIL PROTECTED]> wrote: > My real goal is to feed data to a function and then source it: > > $> cmd_print () { mkfifo zout ; (cat - > zout ) & ; source zout ; rm zout; } > $> cmd_print < $> date > $> EOF > $> As Andreas said, this will be problematic using a fifo. You could do

Re: Quotes problem ?

Markos <[EMAIL PROTECTED]> wrote: > #Delete "logo_1.gif" string from every line in results_1, > #leaving only the path to prepare for "cd" step > > sed 's/logo_1.gif//' /tmp/results_1 >/tmp/results This would be more precisely expressed as: sed 's:/logo_1\.gif$:/:' /tmp/results_1 >/tmp/results If

Re: Quotes problem ?

Markos <[EMAIL PROTECTED]> wrote: > You said that line > cd $path > should be better with quotes to avoid problems with dir names containing > spaces, so did you mean this? > cd "$path" Yes. paul ___ Bug-bash mailing list Bug-bash@gnu.org http://li

Re: long lines not wrapping correctly in Mac OS X

agl <[EMAIL PROTECTED]> wrote: > PS1=$'\[\e]2;\]\h\[\a\]\h:\w \u\$ ' Try this: PS1=$'\[\e]2;\h\a\]\h:\w \u\$ ' The first \h doesn't move the cursor position, so it should be kept within \[ and \] along with the escape sequences. paul ___ Bug-bash ma

Re: man page "-c" explanation clarity

"Paul A. Clarke" <[EMAIL PROTECTED]> wrote: > The man page states, for the "-c" option: >-c string If the -c option is present, then commands are read from > string. If there are arguments after the string, they are > assigned to the positional param

Re: can't pass a response from bash script to an app's interactive dialog

snowcrash+bugbash <[EMAIL PROTECTED]> wrote: > CMD="$GPG --output revoke.txt --gen-revoke $ME" > > /usr/bin/expect -c "\ > spawn `$CMD`;\ > stty -echo;\ > expect 'Create a revocation certificate for this key? (y/N) ';\ > send 'y\n'" You have backticks around $CMD. That means bash will run t

Re: reading the first colums of text file

"Brian J. Murrell" <[EMAIL PROTECTED]> wrote: > < <(cat $file) http://partmaps.org/era/unix/award.html paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

Re: Just created alias doesn't work in a string of commands

"Gurjeet Singh" <[EMAIL PROTECTED]> wrote: > 1$ cat setenv.sh > #!/bin/sh > > alias llrt='ls -lrt' ... > 5$ . ./setenv.sh && llrt && . ./unsetenv.sh > sh: llrt: command not found Aliases are expanded when a command is read, not when it is executed. The entire && chain of commands forms a single co

Re: /etc/bash.bashrc derivation and "misuses"

Chet Ramey <[EMAIL PROTECTED]> wrote: > In my opinion, if a system vendor chooses to enable that sort of > functionality (and many do, for all sorts of reasons), then they > need to add something to the documentation noting that. Could that be done automatically by ./configure when this is enabled

Re: while read subcommand problem

rleeden <[EMAIL PROTECTED]> wrote: > NOTE: This is just an example, so I don't need alternatives for how I could > achieve the specifics shown above. I need to find a good solution where I > can do things with a file (whether it be with sed, awk, tail, head etc.) > then pipe it into a 'while read'

Re: while read subcommand problem

Richard van der Leeden <[EMAIL PROTECTED]> wrote: > The examples in the FAQ do work for the their examples, but I can't figure > out a clean way to implement it with a while loop when reading in lines from > the output of a piped command(s). The redirection applied to "read" in those examples woul

Re: while read subcommand problem

Andreas Schwab <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] (Paul Jarc) writes: >> while ...; do var=...; done <> $(generate-input-for-while) >> EOT >> use "$var" > > This has the disadvantage that generator and consumer no longer run > co

Re: parameter expansion malinterpretation

[EMAIL PROTECTED] wrote: > [EMAIL PROTECTED] ~ $ hello="hello"; echo ${hello:-1} Read entry E12 in the bash FAQ. paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

Re: Syntax question

"Caleb Cushing" <[EMAIL PROTECTED]> wrote: > the line > FEATURES="parallel-fetch ccache distlocks"# userfetch userpriv usersandbox > > I was told my bug is not a bug because there was no space in between the "# > > putting a space does fix the problem but I can't recall that I've ever seen > any do

Re: shouldn't prompt printing be smarter?

Francesco Montorsi <[EMAIL PROTECTED]> wrote: > why would you ever want to have the prompt printed at non-zero column of > the terminal? One possible reason: so you can know whether the previous command ended its output with a newline. Otherwise the output becomes slightly ambiguous. >> If you

Re: Problem with array element assignment

homac <[EMAIL PROTECTED]> wrote: > cat test.txt | while read s l ; do Read entry E4 in the bash FAQ: http://tiswww.case.edu/php/chet/bash/FAQ paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash

Re: Bash arithmetic doesn't give error message on wrap.

[EMAIL PROTECTED] (Bob Proulx) wrote: > On some cpus the result is done one way and on others the result is > done a different way. It is in these cases where typically POSIX > would give up and declare it undefined behavior. Yes, and those are exactly the cases where a message would be helpful,

Re: Bash arithmetic doesn't give error message on wrap.

Richard Neill <[EMAIL PROTECTED]> wrote: > I thought testing for overflow was quite simple? > Isn't it just a case of looking at the carry-bit, and seeing whether it > gets set? That's usually how it's done in assembly. In C, it's somewhat more compilcated. For example: result=a*b; if (result/a

Re: Bash arithmetic doesn't give error message on wrap.

Andreas Schwab <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] (Paul Jarc) writes: >> result=a*b; >> if (result/a!=b) { report overflow; } > > That won't work, since (signed integer) overflow is undefined in C. A > compiler is allowed to optimize the condition

Re: How to remove a specific line in a file

Matthew Woehlke <[EMAIL PROTECTED]> wrote: > It seems like there should be a way to delete the first match in pure > sed, but I didn't figure it out in the few seconds testing I did. sed '/foo/{x;/^$/d;}' paul ___ Bug-bash mailing list Bug-bash@gnu.

Re: Characters aren't being properly escaped/evaluated in a Bash

[EMAIL PROTECTED] wrote: > The problem is that if I did this out of the box > like the following, it 'flattens' the list: > > Example: > for j in `cat $i`; do > echo $j > done > >

Re: read 1 var in when executing command

jdh239 <[EMAIL PROTECTED]> wrote: > I would prefer, again, just to execute the command with the domain name > following Not sure how to do it. You can define the command as a shell function (see "Shell Function Definitions" in the man page under "SHELL GRAMMAR"). You can refer to the first a

Re: Generating unique file names

matte <[EMAIL PROTECTED]> wrote: >The count would be sufficient, as each folder will always hold ONLY these >archives, and no hidden files. >Thus, my directory would be: >myArcName_1.tar.gz >myArcName_2.tar.gz >myArcName_3.tar.gz This will do it, starting the numbering at 0

Re: backwards menu-complete with shift+tab

<[EMAIL PROTECTED]> wrote: > Specifying the key combo shift+tab is not documented. Your terminal program probably doesn't distinguish tab from shift+tab. To check, try running od, and type tab, enter, shift+tab, enter, and see if od prints the same codes for both. paul ___

Re: Infinite loop and crash Linux via BASH command

[EMAIL PROTECTED] wrote: > I don't know by this means (perhaps anybody here with bigger > experiences to can explain us) this simple command creates a job in > background and in loop that quickly consome all the processing. Yes, because that's exactly what you're telling bash to do, if you run

Re: set function and special builtin set

Benno Schulenberg <[EMAIL PROTECTED]> wrote: > Andreas Schwab wrote: >>: >> >> If a simple command results in a command name and an optional >> list of arguments, [...] > > But set() is not a simple command

Re: Timing an operation

Matthew_S <[EMAIL PROTECTED]> wrote: > Can i have something like; > > if > difference between dates <5seconds > echo fail > fi date1=`perl -e 'print time()'` ... date2=`perl -e 'print time()'` interval=`expr "$date2" - "$date1"` if test 5 -gt "$interval"; then echo fail fi On some systems, yo

Re: Pattern replacement inconsistency

Chet Ramey <[EMAIL PROTECTED]> wrote: > Anchored pattern matches that specify removing or replacing each match > don't make sense. The combination is meaningless. It seems meaningful to me, but since only one occurrence could match an anchored pattern, "every match" just means the same thing as "

Re: tracing inside functions

Nic James Ferrier <[EMAIL PROTECTED]> wrote: > Using bash 2.05, does anyone know of a way to get a trace of what's > happening inside a function? You can add "set -x" at the top of the function body. I don't know of any way to get a similar effect without editing the script. paul

Re: variable lost when while loop piped

[EMAIL PROTECTED] wrote: > A variable set inside a while loop loses its value if > the while loop is piped to a command, e.g., sed. This is normal. Read entry E4 in the bash FAQ. paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lis

Re: Bash command completion when not connected to a terminal

raner <[EMAIL PROTECTED]> wrote: > The completion seems to work, but I do not receive the completed filename > from the shell's stdout. It's written to stderr, not stdout. paul ___ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/l

Re: wrong logical evaluation of expressions involving true or false commands

Matthew Woehlke <[EMAIL PROTECTED]> wrote: > Stephane Chazelas wrote: >> [ -n "$foo" -a -n "$bar" ] >> is not the expression to test whether both "$foo" and "$bar" are >> non-empty, as it would fail for some specific values of $foo or >> $bar (try it when $foo contains "=" for instance). > > Huh? W

  1   2   >