Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #14211 > unrolled thread

Re: Bash don't interpret ~ path with multiple options.

Started byL A Walsh <bash@tlinx.org>
First post2018-06-03 11:27 -0700
Last post2018-06-03 11:27 -0700
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: Bash don't interpret ~ path with multiple options. L A Walsh <bash@tlinx.org> - 2018-06-03 11:27 -0700

#14211 — Re: Bash don't interpret ~ path with multiple options.

FromL A Walsh <bash@tlinx.org>
Date2018-06-03 11:27 -0700
SubjectRe: Bash don't interpret ~ path with multiple options.
Message-ID<mailman.1067.1528050485.1292.bug-bash@gnu.org>
Bash will only replace '~' when it has a space before it
and it is not in quotes.  It also won't expand '~' if it
has special characters in it.  In your lines, the '~'
after the equal won't be replaced but the one
at the end should be.






Jungsub Shin wrote:
> When i try mount aufs, i find some problem with bash.
>
> # mount -o remount,append=~/test_aufs/ro1=ro+wh ~/test_aufs/mount
>
> mount failed with ~/test_aufs/ro1 path isn't exist message.
> So i try to debug with strace and i find out bash don't replace ~
> path to absolute path.
>
> So i try again with split options lile below.
>
> # mount -o remount -o append=~/test_aufs/ro1=ro+wh ~/test_aufs/mount
>
> It works well. is this bug?? 
> Thanks.
>
>   

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web