Re: A background ssh can take over the tty from bash?

>> But, from the man page: >> >> -f Requests ssh to go to background just before command execution. >> This is useful if ssh is going to ask for passwords >> or passphrases, but the user wants it in the background. >> This implies -n. The recommended way to start X11 programs

Re: consistency probs var & function re-use

>First problem: If you are assigning a string to a variable, > you need to put quotes around the string. That shows that "-p" > doesn't insert newlines: > > > x="$'foo\nbar'" > > declare -p x > declare -- x="\$'foo\\nbar'" You do not have any newlines in that string, so of course the

Re: -eq and strings

On 6 March 2017 14:09:39 GMT+00:00, Rob la Lau wrote: >On 06-03-17 14:18, Greg Wooledge wrote: >> You're misunderstanding. In a math context, which you are creating >here >> by using -eq, the word 'x' is interpreted as a variable name, which >may >> contain another variable

Re: BUG??

On 29/12/16 01:09, Peter & Kelly Passchier wrote: > Is this a bug? These both output "q=1" > > q=1 > [[ ((q==1)) ]] && echo q=1 > > q=0 > [[ ((q==1)) ]] && echo q=1 > > This looks like an incorrect use of [[/((. The correct phrasing would be: q=1 ((q==1)) && echo q=1 q=0 ((q==1)) && echo q=1

Re: Could bash do what make does?

On 29/11/16 05:41, Robert Durkacz wrote: > make has survived all this time but it is not very well accepted today > with a lot of competing build systems trying to do better. bash is > very secure and moreover the Bourne shell was there first. make is > falling out of favour as far as I can see

Re: bug in [ -f file ] test

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. signature.asc Description: OpenPGP digital signature

Re: [Help-bash] help

On 07/03/16 03:44, Val Krem wrote: > Hi John and all, > > I created several files *.txt and when I execute the this command, > > > autil +10 *txt > > > It is listing the first file only!!! > Your function only deals with 2 arguments, but you are passing it several arguments, not just 2. Bash

Re: r.f.e.

On 03/03/16 23:00, Jude DaShiell wrote: > This would have been cleaner had bash been able to wait until a > command it was given had finished execution before doing its next > command: Bash does that. However, you are passing wget the "--background" option, which explicitly works around this

Re: Add a mirror to github

On 15/02/16 17:53, strom...@gmail.com wrote: > On Monday, February 15, 2016 at 6:19:56 AM UTC-8, Chet Ramey wrote: >> How does setting up a different place for people to get the code >> contribute to a software monoculture? > github is becoming too popular for free software's own good. > > It's

Re: BUG?: (or what's going on?) test for NL == NL fails (bash-4.3.39(3)-release)

On 02/08/15 21:30, Linda Walsh wrote: Am just looking for an efficient way to test for 0x0a as last char in a var, ... after another 20 minutes of trying things at random, found this: printf %d\n '${a:0-1:1}' 10 Oddly, the final single quote in the string seems unnecessary. But that

Re: BUG?: (or what's going on?) test for NL == NL fails (bash-4.3.39(3)-release)

On 02/08/15 20:30, Linda Walsh wrote: if [[ $(printf \n) == $'\n' ]]; then echo T; else echo F; fi F The command substitution operators ($(...) and `...`) strip all trailing linefeeds. You are left with an empty string here. The usual workarounds I see (where necessary) are hacks like this:

Re: GNU Guile integration

On 14/07/15 06:49, Dmitry Bogatov wrote: Guile is for situations, when script is mainly calls other programs, but still needs moderately complex logic of text manipulation, compraison and mapping. Recently I wrote script, that had to emulate map(data structure). Well, I would prefer that is

Re: Bash 4.2.53 cursor position bug

On 03/07/15 23:09, Chet Ramey wrote: [...] the weird `/~' at the beginning of your prompt. On 03/07/15 03:59, gam wrote: PS1=\W\$ 1. Type a short input line /~$ just a line for illustration Maybe your $PROMPT_COMMAND is hiding something nasty. If it is printing that slash,

Re: Bug Reporting

On 09/06/15 09:27, Pierre Gaston wrote: Well it tries to execute the file and show the lines where it gets an error, it's a useful behavior when you try to write a script. If you have read access to these files and can run bash, you can print them anyway eg: bash -c 'echo $(/etc/passwd) '

Re: eval a=b\ c

On 25/05/15 20:33, d...@yost.com wrote: if [[ -n $ZSH_VERSION ]] ; then echo [ ${(q)@} ] eval${(q)@} else echo [ $@ ] eval$@ fi I believe the bash equivalent here would be something along the lines of: quoted=$(printf '%q ' $@) quoted=${quoted% } echo [

autocd shell option breaks on dir names beginning with hyphen

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-unknown-linux-gnu' -DCONF_VENDOR='unknown'