bug-coreutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#70860: Add an option to remove filenames for wc util


From: Chris Elvidge
Subject: bug#70860: Add an option to remove filenames for wc util
Date: Fri, 10 May 2024 17:47:10 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 Lightning/5.4

Why not use 'wc [options] <filename'
Obv. only works on a single filename.

On 10/05/2024 at 12:36, Laurent Lyaudet wrote:
Hello :),

Thanks for your hard work :)
I had a need for a variant of wordcount without filenames in the output,
tuesday.
https://github.com/LLyaudet/DevOrSysAdminScripts/blob/main/build_and_checks_dependencies/lines_filters.sh
https://github.com/LLyaudet/DevOrSysAdminScripts/commit/f0cb3291de4ad0bc63e40baf31364d1af6849f12
I started to make a patch on GNU coreutils on that day,
but I had to interrupt and continue today.
Here is the patch joined to this email.


Best summary of the feature is just to copy-paste my commit message:
wc: Add an option -n --no-filenames.

wc now has an option -n or --no-filenames to remove the filenames
from the output lines.
It is useful when used in conjunction with a single option
-c, -m, -l, -L, or -w,
since the result is a single number per line that can be easily used
in shell (Bash) scripts,
without having to pipe the result with cut.

doc/coreutils.texi: Add option -n to documentation.
NEWS: Mention the change option -n added and justify it.
src/wc.c: Modify the source code to have an option -n.
tests/wc/wc-no-filenames.sh: Test --no-filenames option for wc.


Note that it should be a -f --filenames option if the default was different.
If the default was configurable,
then we should have -f --filenames -n --no-filenames options,
like is possible in some of the latest versions of argparse in Python
(argparse.BooleanOptionalAction).
I don't know how to handle that in C code.
Please accept my patch and improve upon it if needed.

Best regards,
      Laurent Lyaudet



--

Chris Elvidge







reply via email to

[Prev in Thread] Current Thread [Next in Thread]