On 17/05/2024 17:11, Audrey Dutcher wrote:
On my FreeBSD system, downloading coreutils-9.5.tar.xz, then building
with `./configure --enable-single-binary && make` does not succeed,
with the error message `don't know how to make -Wl,-rpath. Stop`
I believe the root cause of this is
On 15/05/2024 03:46, Nikolaos Chatzikonstantinou wrote:
On Tue, May 14, 2024 at 4:03 PM Nikolaos Chatzikonstantinou
wrote:
On Tue, May 14, 2024, 3:59 PM Pádraig Brady wrote:
On 14/05/2024 17:36, Nikolaos Chatzikonstantinou wrote:
See attachment.
Well just above your new mention
On 14/05/2024 17:36, Nikolaos Chatzikonstantinou wrote:
See attachment.
Well just above your new mention of floating-point, we have:
"NUMBER need not be an integer".
How about I adjust your patch to adjust that text to say:
"NUMBER can be an integer or floating-point".
cheers,
Pádraig.
On 12/05/2024 16:06, Paul Eggert wrote:
On 2024-05-12 04:49, Pádraig Brady wrote:
@@ -1151,7 +1151,8 @@ main (int argc, char **argv)
{
/* Default cp operation. */
x.update = false;
- x.interactive = I_UNSPECIFIED
On 12/05/2024 00:03, Robert Hill wrote:
After upgrading coreutils from 9.0 to 9.5, the following change occurred:
In coreutils 9.0, the command "cp -Tipruvx /src-dir /dst-dir" requested
interactive confirmation before replacing an old destination file with a
newer source file, as expected.
In
On 11/05/2024 10:14, Dan Jacobson wrote:
join should have an option to return an error value in the shell's $?
if any lines are not matched.
Currently the man page doesn't even mention a return value. So it is not
set in stone yet.
Currently one must save -v output in a file then use test -s
On 13/04/2024 18:42, Pádraig Brady wrote:
On 13/04/2024 17:39, Pádraig Brady wrote:
install(1) defaults to mode 600 for new files, and uses set_acl() with that
(since 2007 https://github.com/coreutils/coreutils/commit/f634e8844 )
The psuedo code that install(1) uses is:
copy_reg()
if (x
On 07/05/2024 05:19, Bruce Jerrick wrote:
This wording in the pwd(1) man page is unclear:
-P, --physical
avoid all symlinks
"resolve all symlinks" would be much better wording.
Pushed that in your name.
Marking this as done.
thanks,
Pádraig
On 06/05/2024 08:38, Bernard Burette wrote:
Hi,
If I try:
$ cat <&-
cat: -: Bad file descriptor
cat: closing standard input: Bad file descriptor
$
The error on stdin beign closed is displayed twice plus "-" is for a FILE
argument to replace standard input, It would make more sense to
On 03/05/2024 05:12, Attila Fidan via GNU coreutils Bug Reports wrote:
Hi,
I wanted to use the new cp --update=none-fail option introduced in 9.5,
but it said "invalid argument ‘none-fail’ for ‘--update’". It turns out
that the commit (49912bac286eb3c0ef7d1567ae790193ad5eb2e8) adding it
forgot
On 02/05/2024 07:16, Nineteendo INC wrote:
coreutils version: stable 9.5 (bottled)
OS version: macOS 13.6.6 (22G630)
`realpath` doesn’t behave correctly for unreadable symlinks:
wannes@Stefans-iMac ~ % ln -s . src
wannes@Stefans-iMac ~ % grealpath -e src/..
/Users
wannes@Stefans-iMac ~ % chmod
On 01/05/2024 15:28, Art Shelest via GNU coreutils Bug Reports wrote:
Good morning,
I am seeing an aberrant behavior from the /usr/bin/paste utility when working
with Windows-style CR/LF text files.
The repro is for Mint Mate (Virginia).
If I change the line endings in the first file to Unix
On 23/04/2024 11:14, Dan Jacobson wrote:
In (info "(coreutils) sort invocation") be sure to add an example of a
way or workaround for counting fields from the end of the line. E.g., we
want to sort on the last field, but don't know for sure how many fields
a line might contain. E.g., sort by
On 16/04/2024 23:17, Paul Eggert wrote:
On 4/16/24 14:30, Toby Kelsey wrote:
The man page doesn't explain this format conflict, while the info page
(info '(coreutils) ls invocation' or 'info ls') claims '-f' implies '-1'
which is also incorrect: 'ls -1f' gives different output to to 'ls -f'.
On 16/04/2024 15:47, Alejandro Colomar wrote:
Hi Pádraig,
On Tue, Apr 16, 2024 at 03:25:22PM +0100, Pádraig Brady wrote:
What version of darwin is this? I can't repro on Darwin 21.6.0 (MacOSX 12.6).
The issue seems to be that /dev/stdin returns a varying inode which install(1)
doesn't like
On 16/04/2024 12:33, Pádraig Brady wrote:
On 16/04/2024 01:19, Alejandro Colomar wrote:
Hi!
I don't own a Darwin system, so I can't help much reproduce. However,
I've received a bug report to the Linux man-pages, that our build
system (GNUmakefile-based), which ends up calling
On 16/04/2024 01:19, Alejandro Colomar wrote:
Hi!
I don't own a Darwin system, so I can't help much reproduce. However,
I've received a bug report to the Linux man-pages, that our build
system (GNUmakefile-based), which ends up calling
... | install /dev/stdin $@
doesn't work on
On 15/04/2024 15:37, Andreas Grünbacher wrote:
Hello,
Am So., 14. Apr. 2024 um 00:43 Uhr schrieb Pádraig Brady :
On 13/04/2024 20:29, Bruno Haible wrote:
Hi Pádraig,
I wrote:
5) The same thing with 'cp -a' succeeds:
$ build-sparc64/src/cp -a /var/tmp/foo3941 $HOME/foo3941; echo $?
0
On 13/04/2024 20:29, Bruno Haible wrote:
Hi Pádraig,
I wrote:
5) The same thing with 'cp -a' succeeds:
$ build-sparc64/src/cp -a /var/tmp/foo3941 $HOME/foo3941; echo $?
0
$ build-sparc64-no-acl/src/cp -a /var/tmp/foo3941 $HOME/foo3941; echo $?
0
You wrote:
The psuedo code that install(1)
On 13/04/2024 17:39, Pádraig Brady wrote:
install(1) defaults to mode 600 for new files, and uses set_acl() with that
(since 2007 https://github.com/coreutils/coreutils/commit/f634e8844 )
The psuedo code that install(1) uses is:
copy_reg()
if (x->set_mode) /* install */
set_acl(d
scount
EACESS as a valid errno with FD operations, as CIFS was seen to
return that erroneously in some cases.
---
ChangeLog | 7 +++
lib/set-permissions.c | 8 +++-
2 files changed, 14 insertions(+), 1 deletion(-)
diff --git a/ChangeLog b/ChangeLog
index c72165e268..fd094d1091 10064
Things have changed a little since the original request.
alacritty sets $COLORTERM, and dircolors now auto accepts that since:
https://github.com/coreutils/coreutils/commit/75c9fc674
There are some complications with remote shells, but
they should boil down to setting up ssh to send/accept
On 09/04/2024 10:17, Collin Funk wrote:
On 4/9/24 12:57 AM, Paul Eggert wrote:
Indeed there is, and I merged your bug report into that old one. It'd be nice
if someone could get to the bottom of that bug.
I decided to look into this a bit, since I also have an unknown
'uname -i' and 'uname
On 06/04/2024 23:22, Paul Eggert wrote:
On 2024-04-06 03:09, Pádraig Brady wrote:
I'll apply this.
Heh, I beat you to it by looking for similar errors elsewhere and
applying the attached patches to fix the issues I found. None of them
look like serious bugs.
Cool. I thought the sort(1
tag 70219 notabug
close 70219
stop
On 06/04/2024 16:50, Branden R. Williams via GNU coreutils Bug Reports wrote:
-k, --kill-after=DURATION
also send a KILL signal if COMMAND is still running
this long after the initial signal was sent
If you read the
On 06/04/2024 03:52, Takashi Kusumi wrote:
Hi,
I have found a performance issue with the sort command when used on
pseudo files with zero size. For instance, sorting `/proc/kallsyms`, as
demonstrated below, takes significantly longer than executing with
`cat`, generating numerous temporary
On 01/04/2024 16:30, Petr Pisar wrote:
Hello,
while translating coreutils-9.5-pre2 I noticed this message:
#: src/chown.c:123
msgid ""
" --reference=RFILE use RFILE's ownership rather than specifying values\n"
" RFILE is always dereferenced if a symbolic link.\n"
On 31/03/2024 10:02, Adept's Lab wrote:
test-canonicalize.c:411: assertion 'strcmp (result1, "//") == 0' failed
^ the only error log message I get. Fail was not presented with previous
stable versions.
This is on musl 1.1.24 as detailed at:
https://github.com/coreutils/coreutils/issues/83
On 29/03/2024 12:40, Andreas Schwab wrote:
FAIL: test-localtime_r
==
test-localtime_r.c:58: assertion 'result->tm_hour == 18' failed
FAIL test-localtime_r (exit status: 134)
FAIL: test-localtime_r-mt
=
thread2 disturbed by thread1!
thread1 disturbed
On 25/03/2024 14:02, Göran Uddeborg wrote:
While translating the new version of coreutils to Swedish, I came
across this code from the end of chown-core.h:
printf (_("\
--from=CURRENT_OWNER:CURRENT_GROUP\n\
change the %sgroup of each file only if\n\
On 24/03/2024 16:57, Frédéric Marchal wrote:
Hi,
In src/chown-core.h:95 (coreutils-9.5-pre1), the following message is
impossible to translate as it is created by concatenating string fragments:
static inline void
emit_from_option_description (bool user)
{
printf (_("\
On 24/03/2024 12:40, Stephane Chazelas wrote:
Tags: patch
My bad, the patch was incorrect, it should have said
"replaced by the corresponding device major and minor numbers as two decimal
numbers separated by a comma and at least one space.", as
there's not always only once space between the
tag 69951 notabug
close 69951
stop
On 22/03/2024 20:22, Thomas Dreibholz wrote:
Hi,
I just discovered a printf bug for at least the nb_NO and nn_NO locales
when printing numbers with thousands separator. To reproduce:
#!/bin/bash
for l in de_DE nb_NO ; do
echo "LC_NUMERIC=$l.UTF-8"
On 22/03/2024 11:20, Vincent Lefevre wrote:
With GNU Coreutils 9.4, both "test -a -a -a" and "test -o -o -o" fail:
$ export POSIXLY_CORRECT=1
$ /usr/bin/test -a -a -a ; echo $?
/usr/bin/test: ‘-a’: unary operator expected
2
$ /usr/bin/test -o -o -o ; echo $?
/usr/bin/test: ‘-o’: unary operator
for the
inconvenient tabs, e.g. post-processing with pr -t -e.
Good call on the documentation. I'll add this now:
commit 91e69cd2d02f015fc296e02388e0b18a293faa56 (HEAD -> master)
Author: Pádraig Brady
Date: Thu Mar 21 15:26:48 2024 +
doc: pr: give solution to expanding T
On 16/12/2011 16:29, Jan Engelhardt wrote:
Hi,
chown(1) has a -h option by which it affects symlinks directly rather
than the pointed-to file. The bonus side effect is that the
pointed-to files don't get changed in any way, which is kinda welcome
if you attempt to "fix" permissions/ownership in
On 28/03/2012 21:28, Paul Eggert wrote:
On 03/28/2012 01:13 PM, Jim Meyering wrote:
$ ./chmod u+w f
./chmod: changing permissions of 'f': Operation not supported
Yeouch. I undid the change for now.
Hmm, why did "make check" work for me?
I'll have to investigate later, alas.
Patch
On 17/03/2024 11:32, Pádraig Brady wrote:
On 17/03/2024 06:10, Paul Eggert wrote:
On 2024-03-05 06:16, Pádraig Brady wrote:
I think I'll remove the as yet unreleased mv --swap from coreutils,
given that
util-linux is as widely available as coreutils on GNU/Linux platforms.
Although removing
On 17/03/2024 06:10, Paul Eggert wrote:
On 2024-03-05 06:16, Pádraig Brady wrote:
I think I'll remove the as yet unreleased mv --swap from coreutils,
given that
util-linux is as widely available as coreutils on GNU/Linux platforms.
Although removing that "mv --swap" implementation
On 15/03/2024 05:21, Paul Eggert wrote:
On 2024-03-14 06:03, Pádraig Brady wrote:
How about leaving it AC_COMPILE_IFELSE, but ensuring that -O1 or better
is used when the compiler supports -O1? That way we don't have to worry
about running the program, because (with the "volatile&qu
On 14/03/2024 13:35, Collin Funk wrote:
On 3/14/24 6:03 AM, Pádraig Brady wrote:
It would disable this feature for cross-compilation yes,
but this isn't the first instance of AC_RUN_IFELSE we use.
For completeness I should add that the above check can be
overridden if cross-compiling
On 14/03/2024 05:59, Paul Eggert wrote:
On 2024-03-12 19:24, Grisha Levit wrote:
- AC_COMPILE_IFELSE(
+ AC_RUN_IFELSE(
This sort of change would break cross-compilation, no?
It would disable this feature for cross-compilation yes,
but this isn't the first instance of AC_RUN_IFELSE we use.
On 25/01/2024 19:52, Grisha Levit wrote:
On Thu, Jan 25, 2024, 09:50 Pádraig Brady wrote:
This mostly looks good, except:
- No need to clear the errno before kill(3).
- Better to use SIG%d rather than the bare %d for signal _names_, as we already
parse this format
Makes sense, done below
On 13/03/2024 02:24, Grisha Levit wrote:
Recent clang provides __bf16 on aarch64 but it is broken.
If built with -O0, the conversion is wrong:
$ printf '\x3F\x80' | od --end=big -An -tfB | tr -d ' '
1.875
If built with -O1 or higher, compilation fails:
fatal error: error in
I'm erring on the side of applying this,
though I'm a bit wary of an endlessly expanding list,
as there is no end to what can be compressed for example.
cheers,
Pádraig
tag 69636 notabug
close 69636
stop
On 08/03/2024 12:29, User wrote:
Jim Meyering wrote:
Paul Eggert wrote:
* src/seq.c (validate_format): Remove. Migrate its checks into...
(long_double_format): Report an error and exit if an error is found,
instead of returning NULL. All callers
On 05/03/2024 04:10, Paul Eggert wrote:
On 3/4/24 16:43, Dominique Martinet wrote:
Adding Rob to the loop because this impacts compatibility with
toybox/maybe busybox implementations
Busybox does not use RENAME_EXCHANGE, so this isn't a Busybox issue.
Toybox mv added -x to its development
On 04/03/2024 15:47, Pádraig Brady wrote:
On 04/03/2024 00:44, Paul Eggert wrote:
Although I like the idea of exposing file swaps to the user, the first
cut of 'mv -x' has significant problems.
I expect 'mv -x A B' to act like 'mv A B' except the destination must
exist and is renamed back
On 04/03/2024 15:44, Daniel Hofstetter wrote:
Hi,
When specifying an invalid length value followed by a valid length
value I get the following error:
$ printf "hello" | cksum --algo=blake2b --length=12 --length=8
cksum: invalid length: ‘12’
cksum: length is not a multiple of 8
However, if the
On 04/03/2024 00:44, Paul Eggert wrote:
Although I like the idea of exposing file swaps to the user, the first
cut of 'mv -x' has significant problems.
I expect 'mv -x A B' to act like 'mv A B' except the destination must
exist and is renamed back to A. However, this is not true for 'mv -x A
B'
On 01/03/2024 15:33, lacsaP Patatetom wrote:
hi,
I did a few tests with tr and I'm surprised by the results...
$ echo éèçà
éèçà
these characters are encoded in utf-8 on 2 bytes :
$ echo éèçà | xxd
: c3a9 c3a8 c3a7 c3a0 0a .
now I use tr to remove
On 26/02/2024 23:05, Bruno Haible wrote:
Testing the current coreutils git master:
On a Debian 12 system, in which I have not installed a French UTF-8 locale,
I see a test failure of tests/misc/join-utf8.
The essential lines from test-suite.log:
+ test set = set
+ LC_ALL=none
On 24/02/2024 20:44, Aearil via GNU coreutils Bug Reports wrote:
Hi,
wc -w doesn't seem to recognize whitespace characters with a codepoint
over UCHAR_MAX (255) as word separators. For example, using the
character EM SPACE U+2003:
$ printf "foo\u2003bar" | ./wc -w
1
I should get a word count
On 24/02/2024 19:07, Ricardo Branco wrote:
The --zero option is useless if not supported by --check.
Attached patch fixes it.
https://github.com/coreutils/coreutils/pull/81
I'm not sure about this.
By adding this support we diverge the checksum file formats supported by check.
I.e. users
On 01/02/2024 00:36, Paul Eggert wrote:
On 1/31/24 06:06, Pádraig Brady wrote:
To my mind the most protective option takes precedence.
That's not how POSIX works with mv -i and mv -f. The last flag wins. I
assume this is so that people can have aliases or shell scripts that
make -i
On 04/02/2024 21:59, Paul Eggert wrote:
Thanks. One minor comment about this:
+@item B
+brain 16 bit float
+@item H
+half precision float
It might be helpful explain these two formats, e.g., to cite:
https://en.wikipedia.org/wiki/Bfloat16_floating-point_format
and
On 02/02/2024 01:47, Paul Eggert wrote:
On 2/1/24 13:59, Pádraig Brady wrote:
bfloat16 looks like a truncated single precision IEEE,
so we should be able to just pad the extra 16 bits with zeros
when converting to single precision internally for processing.
Sounds good. This would mean od
On 01/02/2024 19:16, Paul Eggert wrote:
Oh, and another thought: suppose someone wants to use od on bfloat16_t
values? They're popular in machine learning applications, and likely
will be more popular than float16_t overall. See:
n't tested
or thought about this much at all.
Any testing your could do would be appreciated.
thanks,
Pádraigcommit 82fc25ab7f34a8198a8f435c1396801d30e8c6b6
Author: Pádraig Brady
Date: Thu Feb 1 17:59:51 2024 +
od: support half precision floating point
* src/od.c: Suport -t f2 t
On 30/01/2024 18:31, Paul Eggert wrote:
On 2024-01-30 03:18, Pádraig Brady wrote:
So we now have the proposed change as:
- revert -n to old silent success behavior
- document -n as deprecated
- Leave --update=none as is (will be synonymous with -n)
- Provide --update=none-fail
On 29/01/2024 21:44, Paul Eggert wrote:
On 1/29/24 08:11, Pádraig Brady wrote:
Right, that's why I'm still leaning towards my proposal in the last mail.
Well, I won't insist on doing nothing; however, the proposal needs
ironing out and now's a good time to do it before installing changes
On 29/01/2024 14:01, Michael Stone wrote:
On Sun, Jan 28, 2024 at 11:14:14PM -0800, Paul Eggert wrote:
I'm not sure reverting would be best. It would introduce more
confusion, and would make coreutils incompatible with FreeBSD again.
Reverting makes more sense than the current situation. I do
On 17/12/2023 14:46, Pádraig Brady wrote:
On 16/12/2023 21:46, Bernhard Voelker wrote:
On 12/15/23 21:13, Michael Stone wrote:
On Fri, Dec 15, 2023 at 11:21:06AM -0800, Paul Eggert wrote:
Stlll, Pádraig gave a reasonable summary of why the change was made,
To clarify my summary a little
On 24/01/2024 20:40, Grisha Levit wrote:
Android reserves [1] some realtime signals and redefines [2] SIGRTMIN,
leaving a gap between the signals that have SIG* constants defined in
signal.h and SIGRTMIN.
When passed such a signal number, gnulib sig2str returns -1 and leaves
its signame
On 05/01/2024 16:44, Samuel Tardieu wrote:
* src/date.c (res_width): This function computes its result solely
from the value of its parameter and qualifies for the const attribute.
* src/tee.c (get_next_out): This function has no side effect and
qualifies for the pure attribute.
Those two
On 06/01/2024 13:08, Bjoern Voigt via GNU coreutils Bug Reports wrote:
After upgrading coreutils from version 9.3 to 9.4, "ls -l" shows error
messages, if the files or directories are in a cifs/smb3 mounted directory.
Example:
/mnt/cifstest here is mounted with "mount -t cifs -o username=myuser
tag 68256 notabug
close 68256
stop
On 05/01/2024 09:22, Nada Machkova wrote:
hello
I have just upgraded Debian Bullseye
and simple df command respond at user CLI
$ df -hT
df: /run/user/1000/doc: Operation not permitted
...
but when I do the same as root there is NO error.
So I UNmounted
On 02/01/2024 22:45, ja...@johnstone.net.au wrote:
Hi Pádraig,
iflag=fullblock seems to resolve this experience and the man page
excerpt provided makes sense though those lines make no appearance in
the man pages on Archlinux. I will follow up with the distro maintainers.
As would explicitly
forcemerge 8171 68216
stop
On 02/01/2024 10:45, ja...@johnstone.net.au wrote:
Hi all,
It seems an instance of `dd` with only an output file doesn't report
the count of records accurately despite bs= being described as
influencing both ibs= and obs=
dd'ing from an unstable remote over ssh
tag 68064 notabug
close 68064
stop
On 27/12/2023 17:29, Larry Ploetz wrote:
It seems like there might be a problem with date addition when the base
date is specified as “day Monthname” instead of “Monthname day”, where
the offset is being interpreted as an absolute year value. This may be
On 16/12/2023 21:46, Bernhard Voelker wrote:
On 12/15/23 21:13, Michael Stone wrote:
On Fri, Dec 15, 2023 at 11:21:06AM -0800, Paul Eggert wrote:
Stlll, Pádraig gave a reasonable summary of why the change was made,
To clarify my summary a little, there I said that -n now _immediately_ fails.
On 15/12/2023 15:56, Michael Stone wrote:
I tend to think this was a serious mistake: it breaks the behavior of
existing scripts with no deprecation period. A stated advantage is
better compatibility with freebsd, but I don't understand why that is
more desirable than compatibility with all
ig
commit 0d9547474d001e2903c18164d8929f5d2d2c0dd7 (HEAD -> master)
Author: Pádraig Brady
Date: Mon Dec 11 17:03:33 2023 +
maint: remove obsolete AC_PROG_GCC_TRADITIONAL
* configure.ac: Remove obsolete macro call.
Recent autoconf warns that it is obsolete.
AC_PROG_CPP sets up the -tradition
On 11/12/2023 09:38, Daniel Hofstetter wrote:
Hi,
The manual entry for -f on
https://www.gnu.org/software/coreutils/manual/html_node/Sorting-the-output.html#index-_002df-9
contains:
"[...] This is equivalent to the combination of --all (-a),
--sort=none (-U), -1, --color=none, and
| 6 ++
build-aux/bootstrap | 4 ++--
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/ChangeLog b/ChangeLog
index 1a3429e03b..b0d748029d 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,9 @@
+2023-12-10 Pádraig Brady
+
+ bootstrap: fix option propagation
tag 67690 notabug
close 67690
stop
On 07/12/2023 14:36, Oleg Moiseichuk via GNU coreutils Bug Reports wrote:
Hello!
I've got a list of IP addresses, each of them is prepended by its frequency
counter (please find attached in the file list-1.txt). I need to sort them from
most frequent to
tag 67680 notabug
close 67680
stop
On 07/12/2023 08:13, Bob Hepple wrote:
$ nohup --version
nohup (GNU coreutils) 9.3
$ uname -a
Linux achar-void 6.5.12_1 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 18:31:50
UTC 2023 x86_64 GNU/Linux
This is on void, but it also behaves the same on fedora-38
I have
On 06/12/2023 09:03, Arsen Arsenović via GNU coreutils Bug Reports wrote:
Hi,
In the manpage of touch, 'touch' flag --time is described as:
--time=WORD
change the specified time: WORD is access, atime, or use:
equivalent to -a WORD is modify or mtime:
tag 67626 notabug
close 67626
stop
On 04/12/2023 16:43, Remigiusz Suwalski via GNU coreutils Bug Reports wrote:
Hi,
today I have discovered accidentally that column utility behaves oddly when
piped to another command, as shown on example below. I am not sure whether this
is a bug or intended
tag 67619 notabug
close 67619
stop
On 04/12/2023 07:41, Dan Jacobson wrote:
Seen on Chromebook:
$ stty speed
38400
$ stty speed 1200
38400
$ stty speed 1200
1200
coreutils 9.4
"speed" only prints the current setting.
A number on its own, sets the input and output speeds.
So depending on the
On 03/12/2023 09:37, Paul Eggert wrote:
That's not a bug, in that 'split' is behaving as documented. The first
input line is one byte shorter than the second one. 'Split' divides the
input into two regions, and because the first region happens to be one
byte longer than the second region both
On 01/12/2023 01:54, Paul Eggert wrote:
On 11/30/23 12:11, Pádraig Brady wrote:
Though that will generally give 128K, which is good when processing all
of a file,
but perhaps overkill when processing just the last part of a file.
The 128 KiB number was computed as being better for apps like
Much clearer thanks.
On my system:
$ stat /sys/kernel/profiling
File: /sys/kernel/profiling
Size: 4096 Blocks: 0 IO Block: 4096 regular file
I can easily repro by setting the buffer size < PAGE_SIZE.
So this patch handles the case where sysfs reports a file is a
On 27/11/2023 16:24, dann frazier wrote:
* src/tail.c (file_lines): Use fstat() to determine a file's block
size and dynamically allocate a buffer of that size for traversing
backwards.
Thanks for the patch.
Could you describe it a bit more.
What happens if we use smaller reads?
Also what
On 26/11/2023 16:09, Sven Köhler wrote:
So Pádraig's patch does allow for parsing lowercase k, but it does not
change numfmt to use lowercase k in its output in si mode.
As Pádraig has shown, ls uses lowercase k in --si mode. So it uses
lowercase k for 1000. I think that numfmt should behave
On 25/11/2023 21:27, Sven Köhler wrote:
Not only --from=si is broken. Also --to=si is broken:
$ numfmt --to=si 3000
3,0K
In order to not break backwards compatibility, you probably have to
introduce a switch --lowercase-kilo such that --to=si produces proper SI
compliant output. Then have
tag 67160 notabug
close 67160
stop
On 14/11/2023 06:42, r n wrote:
I have a lenovo slim 3 chromebook with linux version 5.15.130-etc and when
expr encounter an asterisk for multiplying args, it return a syntax error
unexpected argument 'code 1'. All other arithmetic operators are correctly
On 03/11/2023 15:00, Vitaly Chikunov wrote:
Hi,
coreutils 9.4.0.24.75e248 seems to have regression where ls -l output is
misaligned starting from size column. Example:
/tmp$ ls -la
total 8
drwxrwxrwt 18 root root 380 Nov 3 17:50 .
drwxr-xr-x 26 root root 4096 Jul 24 18:44 ..
On 25/10/2023 02:30, Paul Eggert wrote:
On 10/23/23 06:08, Pádraig Brady wrote:
However the default operation should be the
most common requirement (and also the RFC documented operation in this
case).
A similar case I hit very frequently is pasting hex into bc, and it's
very annoying to have
On 23/10/2023 13:50, Niels Möller wrote:
Pádraig Brady writes:
Will apply the attached later.
Marking this as done.
Thanks! It would make some sense to me to also have options
--upper/--lower; on encoding, they would specify case of the output, on
decoding, they would reject the other case
On 23/10/2023 10:37, Niels Möller wrote:
Hi,
the docs for basenc --base16 says "hex encoding (RFC4648 section 8)".
The referenced section in that RFC says
Essentially, Base 16 encoding is the standard case-insensitive hex
encoding and may be referred to as "base16" or "hex".
I think it
tag 66519 notabug
close 66519
stop
On 13/10/2023 13:31, Simon Richter M. Sc. wrote:
I noticed some broken checksums with leading backslash and wrong
filenames in my checksum files because the original filenames contained
a backslash.
Way to reproduce:
% touch test\\test.file
% b2sum
Pushed.
Marking this as done.
cheers,
Pádraig
On 29/09/2023 15:11, Pádraig Brady wrote:
On 29/09/2023 10:46, Paul Millar wrote:
Hi,
RFC 4648 says[1]:
> In some circumstances, the use of padding ("=") in base-encoded data
> is not required or used.
Currently, the 'base64' application always includes the paddi
On 29/09/2023 10:46, Paul Millar wrote:
Hi,
RFC 4648 says[1]:
> In some circumstances, the use of padding ("=") in base-encoded data
> is not required or used.
Currently, the 'base64' application always includes the padding when
encoding, and prints an warning/error message (on stderr)
On 28/09/2023 11:43, Jorge Stolfi wrote:
The full documentation of the "--general-numeric-sort" option of
{sort} says that NaN values are sorted "in a consistent but
machine-dependent order".
This is not good. The point of the IEEE floating-point standard was to
make the results of
On 28/09/2023 11:11, Jorge Stolfi wrote:
The full documentation of sort explains that numeric sorting (as in
"sort -n") accepts a leading "-" sign, decimal points, thousands
separators, etc, but does not accept an explicit "+" sign. Values with
explicit "+" are treated as numeric 0 and ties are
tag 66056 notabug
close 66056
stop
On 17/09/2023 19:37, Pádraig Brady wrote:
On 17/09/2023 18:32, Manfred Alfare wrote:
Hi!
Details described here:
https://forums.linuxmint.com/viewtopic.php?t=404074
I don't think anything in tee has changed between 8.30 and 8.32,
wrt carriage return
On 17/09/2023 18:32, Manfred Alfare wrote:
Hi!
Details described here:
https://forums.linuxmint.com/viewtopic.php?t=404074
I don't think anything in tee has changed between 8.30 and 8.32,
wrt carriage return handling, especially on linux.
My best guess is that fsarcher has changed to do
the
On 02/09/2023 10:38, Simon Heimberg wrote:
Hello
Depending on what a process is mainly limited by, the ideal number of
processes to run concurrently varies.
A frequent use case is to run one process on each _physical_ core
(which is available) than on each logical processing unit.
I propose to
1 - 100 of 3104 matches
Mail list logo
