bug#68892: 'tr' function | Outputs printed before the command prompts

2024-02-02 Thread Davide Brini via GNU coreutils Bug Reports
On Fri, 2 Feb 2024 16:40:26 +0200, Ricky Tigg wrote: > OS: Fedora v86_64. coreutils v.: 9.3. Shell: bash v. 5.2.26. > > Hello. Normally outputs are printed after the command prompt; "#" "$" on > my system. > > (...)@(...):~$ rpm -ql coreutils | head -2 > /usr/bin/[ > /usr/bin/arch > > Unexpectedl

bug#52873: expr unexpected syntax error

2021-12-29 Thread Davide Brini
On Wed, 29 Dec 2021 12:42:24 +, Martin Rixham wrote: > I'm getting an error from the following: > > [martin@fedora ~]$ expr ')' : '.*' > expr: syntax error: unexpected ')' > > There also seems to be a similar problem with: > > expr '(' : '.*' I think you need to use '+' before th

bug#51011: [GNU sort] Numerical sort with delimiter may be broken (bug)

2021-10-04 Thread Davide Brini
On Mon, 4 Oct 2021 10:36:52 -0400, Juncheng Yang wrote: > Hi coreutils developers, > I have encountered a bug in GNU sort in which sort produces incorrect > results when numerical sort with delimiters. For example, sort -nk1 -t , > file cannot sort the a file with the following lines (sort by

bug#42711: Tail does not recognize line number spec for multiple files

2020-08-04 Thread Davide Brini
On Tue, 4 Aug 2020 18:19:11 +, Anonymousemail wrote: > This command gives an error: > > $ tail -5 foo bar baz > tail: option used in invalid context -- 5 > > For comparison, the equivalent head commans works exactly as expected: Even if head works, the - syntax is obsolete and should be repl

bug#21672: env is not splitting command and argument as suggested by the synopsis

2015-10-12 Thread Davide Brini
On Mon, 12 Oct 2015 10:48:55 +0200, Esli wrote: > Hello, > > > > env is not splitting command and argument as suggested by the synopsis: > > SYNOPSIS > >env [OPTION]... [-] [NAME=VALUE]... [COMMAND [ARG]...] > > > > Example: > > #!/usr/bin/env perl -w > > produces: > > /usr

bug#14299: Incorrect output of `printf "\\n"`

2013-04-29 Thread Davide Brini
On Sun, 28 Apr 2013 18:44:23 +, Pavel Elkind wrote: > Dear developers, > > I found the following potential bug in printf (version 8.17). > > Actual result: > `printf "\\n"` prints a newline caracter. > > Expected result: > `printf "\\n"` prints a sequence of two individual characters, '\'

bug#10819: [BUG][RM]

2012-02-16 Thread Davide Brini
On Wed, 15 Feb 2012 15:06:05 -0700, Eric Blake wrote: > tag 10819 needinfo > thanks > > On 02/15/2012 08:05 AM, jeremy.mag...@epitech.eu wrote: > > Hello, > > > > I'm writing to you to inform you of a possible bug in the linux "rm" > > command. > > I've experienced that when using by error the

bug#10287: [wishlist] uniq can remove non adjacent lines

2011-12-13 Thread Davide Brini
On Mon, 12 Dec 2011 21:20:18 -0700, Bob Proulx wrote: > Stéphane Blondon wrote: > > I think `uniq` should have an additional option (for example -a, > > --all) to remove same lines but not adjacent. > > > > The man page explains a workaround based on `sort` but it can be > > complex to use. Few

bug#9504: ls oddity

2011-09-14 Thread Davide Brini
On Wed, 14 Sep 2011 12:58:14 +0100, Dave Pawson wrote: > ls -al works as expected > > ls *.xml ... fails? > > [dpawson@localhost pawson]$ ls *.xml > ls: invalid option -- ':' > Try `ls --help' for more information. > > > Not sure if it's a bug or my setup? You have some filename that confuse

bug#9449: Bug report on 'wc' : characters count adds one character

2011-09-06 Thread Davide Brini
On Tue, 6 Sep 2011 15:49:24 +0200, "Laurent TARRISSE" wrote: > Hi, > > Documentation on 'wc' says: > -- > wc -m, --chars > print the character counts > > -- > > But here follows the output I g

bug#9418: closed (Re: bug#9418: case sensitivity buggy in sort)

2011-09-02 Thread Davide Brini
On Fri, 2 Sep 2011 08:46:23 +0200, Michał Janke wrote: > I definitely don't agree with "locale issue" explanation. This is not > a problem of some letter being treated as > or < than other > - the problem is that it is _sometimes_ one way, sometimes the other! > Please have a closer look at this

bug#9019: wc -l bug

2011-07-07 Thread Davide Brini
On Thu, 7 Jul 2011 12:31:16 +0400 Andrey Sheyko wrote: > Hello! > I've found out that wc -l doen't count the last line if there is no CR in > the end of line That is correct. The description for -l says: -l Write to the standard output the number of characters in each input file. Also

bug#8587: Curious bug.

2011-04-29 Thread Davide Brini
On Fri, 29 Apr 2011 21:09:43 +0200 Francois Boisson wrote: > On a debian squeeze amd64. > > francois@totoche:~$ echo ABCD Directory | tr [:lower:] [:upper:] > ABCD DIRECTORY > francois@totoche:~$ cd /tmp > francois@totoche:/tmp$ echo ABCD Directory | tr [:lower:] [:upper:] > tr: construit [:up

bug#7182: sort -R slow

2010-10-09 Thread Davide Brini
On Sat, 9 Oct 2010 14:52:41 +0200 Ole Tange wrote: > I recently needed to randomize some lines. So I tried using 'sort -R'. > I was astonished how slow that was. So I tested how slow a competing > strategies are. GNU sort is two magnitudes slower than unsort and more > than one magnitude slower t

bug#6960: mv refuses to move a symlink over a hard link to the same file

2010-08-31 Thread Davide Brini
On Tue, 31 Aug 2010 17:30:19 -0600 Eric Blake wrote: > Not quite. POSIX specifies that: > http://www.opengroup.org/onlinepubs/9699919799/utilities/mv.html > > If the source_file operand and destination path name the same existing > file, then the destination path shall not be removed, and one

bug#6960: mv refuses to move a symlink over a hard link to the same file

2010-08-31 Thread Davide Brini
On Tue, 31 Aug 2010 17:21:08 -0400 Matt McCutchen wrote: > If mv is asked to move a symlink over a hard link to the same file, it > fails with the message, "A and B are the same file". There is no reason > why it should complain rather than perform the move. Example: > > $ ~/coreutils/coreutil

bug#6780: Problem with the cut command

2010-08-02 Thread Davide Brini
On Mon, 02 Aug 2010 05:56:31 -0700 Bill wrote: > I'm not sure if this is a bug, a question or a feature request, > but there is a problem with the cut command, specifically with > it's delimiter option '-d'. > > In older times disk space was scarce and every byte was > conserved. Fields in dat

bug#6605: +N lines broken with /usr/bin/tail (GNU coreutils) 7.4

2010-07-15 Thread Davide Brini
On Thu, 15 Jul 2010 13:34:50 -0700 (PDT) Forest Oakwater wrote: > Paul, > > Thank you for the information.  Would you consider updating the builtin > documentation and man page to match the behavior of the program? It *is* correct. Nowhere it says that you can use "tail -2" or "tail +2". Inste

bug#6605: +N lines broken with /usr/bin/tail (GNU coreutils) 7.4

2010-07-10 Thread Davide Brini
On Sat, 10 Jul 2010 03:50:32 -0700 (PDT) Forest Oakwater wrote: > Using this data file: > d...@elrond:~/backgrounds/frazetta$ cat data.txt > line 1 > line 2 > line 3 > line 4 > > and this command: > d...@elrond:~/backgrounds/frazetta$ /usr/bin/tail +2 data.txt > /usr/bin/tail: cannot open `+2' f

bug#6511: df output difficult to parse

2010-06-25 Thread Davide Brini
On Friday 25 June 2010, Valerio Pachera wrote: > Package: GNU coreutils > Version: 8.5 > > Severity: wishlist > > Description: > I'm trying to parse di output of df command to check how much free > space is left on my disks. > I need to check this by a script. > The problem is that, when the dev

bug#6356: How to avoid showing the 'total' line with wc -l?

2010-06-05 Thread Davide Brini
On Saturday 05 June 2010, Peng Yu wrote: > When I use wc -l *.txt, it show the total number of lines at the end. > I don't necessary need this last line. Is there a way to disable it? It's dictated by POSIX. You can try wc -l *.txt | head -n -1 -- D.

bug#6353: cp and mv with single wild card argument acts as if multiple arguments were entered.

2010-06-04 Thread Davide Brini
On Friday 04 June 2010, Darwin Gregory wrote: > If you execute "cp /path/*" the command expands the wildcard, and treats > the last file as the destination directory. If the last file in /path/ is > not a directory the command fails, but not with the appropriate error. > However, if the last