Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #11282
| From | Linda Walsh <bash@tlinx.org> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: BUG?: (or what's going on?) test for NL == NL fails (bash-4.3.39(3)-release) |
| Date | 2015-08-02 15:11 -0700 |
| Message-ID | <mailman.7771.1438553489.904.bug-bash@gnu.org> (permalink) |
| References | <55BE6FB8.4080200@tlinx.org> <55BE759D.8030700@gmail.com> |
Charles Daffern wrote:
> 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:
>
> variable=$(command; echo x); variable=${variable%?x}
----
I see what you mean --- erk...
I think the process substitution doesn't, since you need
to explicitly use a -t switch if you want to strip the "\n"'s off
Thanks!
Back to gnu.bash.bug | Previous | Next | Find similar
Re: BUG?: (or what's going on?) test for NL == NL fails (bash-4.3.39(3)-release) Linda Walsh <bash@tlinx.org> - 2015-08-02 15:11 -0700
csiph-web