GNU bug report logs - #24054
tr bug? [:space:] acts like "a"

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 24054 in the body.
You can then email your comments to 24054 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: <pmun <at> tutanota.de>
To: <bug-coreutils <at> gnu.org>
Subject: tr bug? [:space:] acts like "a"
Date: Fri, 22 Jul 2016 19:58:43 +0100 (BST)

[Message part 1 (text/plain, inline)]

For the last few weeks tr [:space:] isn't working the way it used to for me under Ubuntu 14.04. Instead of acting on spaces it acts on "a"s.:

me <at> U:~$ echo "thisstring abcde what the heck?" | tr [:space:] '_'
thisstring _bcde wh_t the heck?
me <at> U:~$

This is 64 bit 14.04 built up from the mini.iso with just plain Openbox as the only DE, in lxterminal using bash.



--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com

[Message part 2 (text/html, inline)]

Message #8 received at 24054 <at> debbugs.gnu.org (full text, mbox):

From: Assaf Gordon <assafgordon <at> gmail.com>
To: pmun <at> tutanota.de, 24054 <at> debbugs.gnu.org
Subject: Re: bug#24054: tr bug? [:space:] acts like "a"
Date: Fri, 22 Jul 2016 17:18:27 -0400

tag 24054 notabug
close 24045
stop

Hello,

On 07/22/2016 02:58 PM, pmun <at> tutanota.de wrote:
> For the last few weeks tr [:space:] isn't working the way it used to for me under Ubuntu 14.04. Instead of acting on spaces it acts on "a"s.:
>
> me <at> U:~$ echo "thisstring abcde what the heck?" | tr [:space:] '_'
> thisstring _bcde wh_t the heck?
>
> This is 64 bit 14.04 built up from the mini.iso with just plain Openbox as the only DE, in lxterminal using bash.

This is not a bug, but a result of your shell (bash) performing filename completion on single-letter filenames in your current directory.

In bash, the syntax [X] without quotes does filename completion, just like "*" or "?".

I would guess that in the last few weeks you created a file called 'a' in the directory,
and so '[:space:]' matched it  (technically it means: match filenames of one character, one of :,s,p,a,c or e).

It used to "just work", because if the shell does not find matching files, it passes the parameter as-is to the program.

The following will demonstrate:

    $ mkdir empty
    $ cd empty

    $ echo [:space:]
    [:space:]

    $ touch a

    $ echo [:space:]
    a

    $ touch ':'

    $ echo [:space:]
    : a

    $ echo '[:space:]'
    [:space:]

Since the shell replaced '[:space:]' with 'a', the 'tr' command became:

    tr a '_'

which is the behavior you encountered.

The solution is to always quote such parameters:

    $ echo "thisstring abcde what the heck?" | tr '[:space:]' '_'
    thisstring_abcde_what_the_heck?_

(The last underscore is the newline, which also counts as whitespace).

To learn more about bash's filename expansion capabilities, see here:
  https://www.gnu.org/software/bash/manual/bashref.html#Filename-Expansion


As such I'm closing this bug report, but discussion can continue by replying to this thread.

regards,
 - assaf

Message #15 received at 24054 <at> debbugs.gnu.org (full text, mbox):

From: <pmun <at> tutanota.de>
To: <24054 <at> debbugs.gnu.org>
Subject: Thanks. Answer applies to all bracketed expressions?
Date: Sat, 23 Jul 2016 19:23:53 +0100 (BST)

[Message part 1 (text/plain, inline)]

Yep, that fixed it. I tested [:print:] and it works like that also. I presume this applies to ALL the bracketed special expressions mentioned in man tr. If anyone knows differently, please correct me. I'm surprised I haven't bashed into this pitfall sooner.

Thanks, Mr. Gordon, for replying in a flash.

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.