Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #13790 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2018-03-02 10:59 -0500 |
| Last post | 2018-03-02 10:59 -0500 |
| 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.
Re: tilde character not interpreted in variable set Chet Ramey <chet.ramey@case.edu> - 2018-03-02 10:59 -0500
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2018-03-02 10:59 -0500 |
| Subject | Re: tilde character not interpreted in variable set |
| Message-ID | <mailman.10028.1520006371.27995.bug-bash@gnu.org> |
On 3/2/18 7:14 AM, Koncz, Istvan (Extern) wrote: > Bash Version: 4.4 > Patch Level: 18 > Release Status: release > > Description: > when i use ~/ for home folder it works in command line e.g. ls > -la ~/.vimrc works, but when i add it to a variable e.g. foo="~/.vimrc" > then ~/ will not be replaced to $HOME value like in command line, but i > think it should be. ~ is a special character so must be escapped like > \~ if i want the char, but without escape it should provide the home > like in ls -la ~/ command. In my oppinion it is a bug. It's not a bug. The tilde is quoted, and is not one of the special characters that is interpreted inside double quotes. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to top | Article view | gnu.bash.bug
csiph-web