Re: Does [ -f FILE ] have a bug on testing a symlink ?

2015-02-10 Thread Jonathan Hankins
The OP's issue isn't bash-specific. The behavior of test WRT symbolic links is specified in POSIX, cf. http://pubs.opengroup.org/onlinepubs/9699919799/utilities/test.html Specifically: "With the exception of the -h pathname and -L pathname primaries, if a pathname argument is a symbolic link, te

Re: Does [ -f FILE ] have a bug on testing a symlink ?

2015-02-10 Thread Stephane Chazelas
2015-02-09 14:59:06 -0700, Bob Proulx: [...] > The idea is that symlinks should be completely transparent and > invisible to most applications. The idea is that when normal things > are run they don't realize they are using a symlink. Behavior would > be exactly the same as if it were a regular f

Re: Command line prefixed with space is not saved

2015-02-10 Thread Vladimir Kanazir
Bob Proulx wrote: Well... It has been packaged that way for years and years and years. I didn't look to see how long but this really isn't anything new. Ah! I kept my home folder for about a decade, copying everything to new drives (and I used slack, fedora and suse before ubuntu). But, thi

Re: Command line prefixed with space is not saved

2015-02-10 Thread Bob Proulx
Vladimir Kanazir wrote: > Bob Proulx wrote: > >The bash default is not to set that variable. But it looks like you > >are using Ubuntu and the Ubuntu package default is to set it in the > >default .bashrc file as a user level customization. > > Yes, they broke many things in 14.04 LTS... Well...

Re: Command line prefixed with space is not saved

2015-02-10 Thread Vladimir Kanazir
Bob Proulx wrote: The bash default is not to set that variable. But it looks like you are using Ubuntu and the Ubuntu package default is to set it in the default .bashrc file as a user level customization. Yes, they broke many things in 14.04 LTS... Thank you! -- Regards Vladimir Kanazir

Re: Command line prefixed with space is not saved

2015-02-10 Thread Bob Proulx
Vladimir Kanazir wrote: > uname output: Linux canny 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 > 15:45:27 $ > When you type space before the command, the command is not > saved in the history. > You can't see it when arrow up / CTRL+P is pressed. It is > like the command

Re: Command line prefixed with space is not saved

2015-02-10 Thread Chet Ramey
On 2/10/15 4:00 AM, Vladimir Kanazir wrote: > Bash Version: 4.3 > Patch Level: 11 > Release Status: release > > Description: > When you type space before the command, the command is not > saved in the history. > You can't see it when arrow up / CTRL+P is pressed. It is > like the

Re: Command line prefixed with space is not saved

2015-02-10 Thread Pádraig Brady
On 10/02/15 09:00, Vladimir Kanazir wrote: > 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='l$ > uname output: Linux canny 3.13.0-34-generic #60-

Command line prefixed with space is not saved

2015-02-10 Thread Vladimir Kanazir
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='l$ uname output: Linux canny 3.13.0-34-generic #60-Ubuntu SMP Wed Aug 13 15:45:27 $ Machine Type: x86_64-

Re: Does [ -f FILE ] have a bug on testing a symlink ?

2015-02-10 Thread Hans J Albertsson
The current behaviour is according to the intended functionality of symlinks when they first appeared, i e to create first-rank local references across få boundaries. cf hard links. Hans J. Albertsson >From my Nexus 5 Den 10 feb 2015 10:04 skrev "Jonathan Hankins" : > $ touch foo > $ ln -s foo ba

Minor issue in bash manual. Obscure/invalid sentence in chapter "4.3.1 The Set Builtin".

2015-02-10 Thread Victor Yarema
Hello. In the latest version of online manual for gnu bash, in chapter "4.3.1 The Set Builtin" (https://www.gnu.org/software/bash/manual/html_node/The-Set-Builtin.html) there is obscure explanation to option "-a". The sentence says "Mark variables and function which are modified or created for exp

Re: Does [ -f FILE ] have a bug on testing a symlink ?

2015-02-10 Thread Jonathan Hankins
$ touch foo $ ln -s foo bar $ [[ -f foo ]] && [[ ! -h foo ]] && echo "exists and is not a symlink" exists and is not a symlink $ [[ -f bar ]] && [[ ! -h bar ]] && echo "exists and is not a symlink" $ -Jonathan Hankins On Mon, Feb 9, 2015 at 6:00 PM, Cheng Rk wrote: > > > On Monday, February 9,