History log of /dragonfly/bin/ls/print.c (Results 1 – 25 of 34)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
# d9d30518 05-Nov-2022 Antonio Huete Jimenez <tuxillo@quantumachine.net>

bin/ls: Fix mismatched parentheses.

Submitted-by: piecuch (closes #3322)


Revision tags: v6.2.2, v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0
# 5ca0a96d 28-Dec-2020 Sascha Wildner <saw@online.de>

Remove last remains of FSMID support from userland.

The kernel side was added in 2005 (7d15906a7a159575b1983f7c1fadde4b)
and removed again in 2009 (d98152a8b8a4b368ca0e08b84302f2f2).

Approved-by: d

Remove last remains of FSMID support from userland.

The kernel side was added in 2005 (7d15906a7a159575b1983f7c1fadde4b)
and removed again in 2009 (d98152a8b8a4b368ca0e08b84302f2f2).

Approved-by: dillon

show more ...


Revision tags: v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3
# 3f7b7260 23-Oct-2019 Sascha Wildner <saw@online.de>

world/kernel: Use the rounddown2() macro in various places.

Tested-by: zrj


Revision tags: v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc
# 4c605ac6 26-Dec-2017 zrj <rimvydas.jasinskas@gmail.com>

ls(1): Add -_ option to include nanotime in ls -l.

Very useful when debugging Makefile races in rules with
vfs.timestamp_precision=1 set.
Yes, ls -l_ seems strage, but we are running out of letters

ls(1): Add -_ option to include nanotime in ls -l.

Very useful when debugging Makefile races in rules with
vfs.timestamp_precision=1 set.
Yes, ls -l_ seems strage, but we are running out of letters and
FreeBSD already has the "-," flag in their ls(1).

show more ...


# dc3f655c 26-Dec-2017 zrj <rimvydas.jasinskas@gmail.com>

ls(1): Add -D option to set date-time format in ls -l.

Taken-from: FreeBSD


# 6a6a7e62 26-Dec-2017 zrj <rimvydas.jasinskas@gmail.com>

ls(1): Sort flags by order in usage() and manpage.

Add missing 'S' in SYNOPSIS.

While there, move out trailing space separator handling to caller.


# 9e5de6b5 25-Dec-2017 zrj <rimvydas.jasinskas@gmail.com>

ls(1): Minor cleanup.

No functional change.


Revision tags: v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc
# c0a9d818 22-Nov-2015 John Marino <draco@marino.st>

ls(1): New long format for named locales

The use of the basic version of ISO 8601 was not very popular. After
a discussion on IRC, the Long Format of named locales is the following:

DD-MMM-YYYY

ls(1): New long format for named locales

The use of the basic version of ISO 8601 was not very popular. After
a discussion on IRC, the Long Format of named locales is the following:

DD-MMM-YYYY hh:mm

DD is day number with leading zeros
MMM is abbreviated month *in english* (regardless of locale)
YYYY is 4-digit year
hh is 24-hour with leading zeros
ss is seconds with leading zeros

show more ...


# 877e2cd4 20-Nov-2015 John Marino <draco@marino.st>

ls(1): Take II on fixing future time listings

Really make sure all future timestamps are display with a year.
The logic of the first attempt was incorrect, and it did the opposite.


# d4428785 20-Nov-2015 John Marino <draco@marino.st>

ls(1): Return previous long format for C/POSIX locales

The output of ls -l for POSIX locales is covered by the POSIX standard.
The previous implementation was not compliance with the handling of
fut

ls(1): Return previous long format for C/POSIX locales

The output of ls -l for POSIX locales is covered by the POSIX standard.
The previous implementation was not compliance with the handling of
future timestamps. The standard requires that future timestamps always
show the year where as previously it would only show the year if the
file's modification time was less than 6 months into the future.

This change detects if C/POSIX LC_TIME is specified, and if so, it
implements the long format as specified by the POSIX standard. The
ISO 8601 format is still used for named locales.

Reported by: swildner

show more ...


# 0b35d94f 20-Nov-2015 John Marino <draco@marino.st>

ls(1): Alter time portion of "long format"

One side effect of moving to the CLDR standard for locale definitions
is that abreviated months are no longer guaranteed to align. We altered
the definiti

ls(1): Alter time portion of "long format"

One side effect of moving to the CLDR standard for locale definitions
is that abreviated months are no longer guaranteed to align. We altered
the definitions for CJK to ensure this, but we do not want to manually
adjust every locale.

The most obvious manifestation is seen with ls(1) using the long format
(-l option). Not only is the month abbreviation no longer guaranteed to
be 3 characters wide, it's not even guaranteed to be a uniform width. As
a result, the file listing may no longer line up, as seen with French:

ironwolf# env LANG=fr_FR.UTF-8 ls -l | head
drwxr-xr-x 2 root wheel 512 26 mars 2015 ariadne
drwxr-xr-x 2 root wheel 512 26 mars 2015 artemis
drwxr-xr-x 3 root wheel 512 9 sept. 19:45 avida
drwxr-xr-x 3 root wheel 512 9 sept. 19:45 babel
drwxr-xr-x 3 root wheel 512 15 juin 20:38 bcftools
drwxr-xr-x 2 root wheel 512 20 sept. 11:27 biococoa
drwxr-xr-x 2 root wheel 512 26 mars 2015 biojava
drwxr-xr-x 3 root wheel 512 26 mars 2015 blat
drwxr-xr-x 3 root wheel 512 7 nov. 08:44 bwa

ironwolf# env LANG=fr_FR.UTF-8 ls -lT | head
drwxr-xr-x 2 root wheel 512 26 mars 10:15:28 2015 ariadne
drwxr-xr-x 2 root wheel 512 26 mars 10:15:28 2015 artemis
drwxr-xr-x 3 root wheel 512 9 sept. 19:45:04 2015 avida
drwxr-xr-x 3 root wheel 512 9 sept. 19:45:04 2015 babel
drwxr-xr-x 3 root wheel 512 15 juin 20:38:55 2015 bcftools
drwxr-xr-x 2 root wheel 512 20 sept. 11:27:40 2015 biococoa
drwxr-xr-x 2 root wheel 512 26 mars 10:15:28 2015 biojava
drwxr-xr-x 3 root wheel 512 26 mars 10:15:28 2015 blat
drwxr-xr-x 3 root wheel 512 7 nov. 08:44:24 2015 bwa

To address both issues (misalignment and differing widths as a function
of locale), I've modified ls(1) to use valid forms of ISO 8601, an
international standard for the representation of time.

The default long format produces the last modified timestamp in the form
of YYYYMMDDTHH (Year|Month|Day|T|Hour with no spaces). This is known as
the "basic" format which includes the optional "T" concatenator. The
result is the time is represented by a single column using 1-3 characters
less than before.

ironwolf# env LANG=fr_FR.UTF-8 ls -l | head
drwxr-xr-x 2 root wheel 512 20150326T10 ariadne
drwxr-xr-x 2 root wheel 512 20150326T10 artemis
drwxr-xr-x 3 root wheel 512 20150909T19 avida
drwxr-xr-x 3 root wheel 512 20150909T19 babel
drwxr-xr-x 3 root wheel 512 20150615T20 bcftools
drwxr-xr-x 2 root wheel 512 20150920T11 biococoa
drwxr-xr-x 2 root wheel 512 20150326T10 biojava
drwxr-xr-x 3 root wheel 512 20150326T10 blat
drwxr-xr-x 3 root wheel 512 20151107T08 bwa

The -T option uses the extended format of ISO 8601 without the T symbol,
but with the minutes and seconds representation. The result is two
characters wider than the approach FreeBSD is taking to address the same
issue (FreeBSD is padding the month section and expanding the field by
two characters to accommodate 5-character wide month names). The output
on DragonFly looks like this:

ironwolf# env LANG=fr_FR.UTF-8 ls -lT | head
drwxr-xr-x 2 root wheel 512 2015-03-26 10:15:28 ariadne
drwxr-xr-x 2 root wheel 512 2015-03-26 10:15:28 artemis
drwxr-xr-x 3 root wheel 512 2015-09-09 19:45:04 avida
drwxr-xr-x 3 root wheel 512 2015-09-09 19:45:04 babel
drwxr-xr-x 3 root wheel 512 2015-06-15 20:38:55 bcftools
drwxr-xr-x 2 root wheel 512 2015-09-20 11:27:40 biococoa
drwxr-xr-x 2 root wheel 512 2015-03-26 10:15:28 biojava
drwxr-xr-x 3 root wheel 512 2015-03-26 10:15:28 blat
drwxr-xr-x 3 root wheel 512 2015-11-07 08:44:24 bwa

The long format no longer changes if the last modified time is within six
months (future or past), thus file times are more quickly comparable with
a quick visual scan versus switching between year and hours:seconds.

Reported by: bapt@FreeBSD.org

show more ...


Revision tags: v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0, v4.0.6, v4.3.0, v4.2.0rc, v4.0.5, v4.0.4, v4.0.3, v4.0.2, v4.0.1, v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1, v3.6.0, v3.7.1, v3.6.0rc, v3.7.0, v3.4.3
# dc71b7ab 31-May-2013 Justin C. Sherrill <justin@shiningsilence.com>

Correct BSD License clause numbering from 1-2-4 to 1-2-3.

Apparently everyone's doing it:
http://svnweb.freebsd.org/base?view=revision&revision=251069

Submitted-by: "Eitan Adler" <lists at eitanadl

Correct BSD License clause numbering from 1-2-4 to 1-2-3.

Apparently everyone's doing it:
http://svnweb.freebsd.org/base?view=revision&revision=251069

Submitted-by: "Eitan Adler" <lists at eitanadler.com>

show more ...


Revision tags: v3.4.2, v3.4.0, v3.4.1, v3.4.0rc, v3.5.0, v3.2.2, v3.2.1, v3.2.0, v3.3.0, v3.0.3, v3.0.2, v3.0.1, v3.1.0, v3.0.0
# 86d7f5d3 26-Nov-2011 John Marino <draco@marino.st>

Initial import of binutils 2.22 on the new vendor branch

Future versions of binutils will also reside on this branch rather
than continuing to create new binutils branches for each new version.


Revision tags: v2.12.0, v2.13.0, v2.10.1, v2.11.0, v2.10.0, v2.9.1, v2.8.2, v2.8.1, v2.8.0, v2.9.0, v2.6.3, v2.7.3, v2.6.2, v2.7.2, v2.7.1, v2.6.1, v2.7.0, v2.6.0, v2.5.1, v2.4.1, v2.5.0, v2.4.0, v2.3.2, v2.3.1, v2.2.1
# 76dc7fb4 26-Feb-2009 Sascha Wildner <saw@online.de>

ls(1): Fix amd64 warnings.


Revision tags: v2.2.0, v2.3.0, v2.1.1, v2.0.1
# 6cbddef6 24-Jun-2008 YONETANI Tomokazu <y0netan1@dragonflybsd.org>

One more place where an inode is still printed as a 32 bit quantity.


# ea7e77b6 04-May-2008 Matthew Dillon <dillon@dragonflybsd.org>

Print the 64 bit inode as a 64 bit quantity rather then a 32 bit quantity.


# f966adb2 21-May-2007 Matthew Dillon <dillon@dragonflybsd.org>

Use 0x%08x for all minor numbers, not just those > 255.


# 1f0f7b35 06-Nov-2005 Sascha Wildner <swildner@dragonflybsd.org>

Cleanup:

- In function definitions, move the type on a line of its own.
- Ansify function definitions.
- Remove (void) casts for discarded return values.


# cd07f2f6 19-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Synchronise with FreeBSD:

Use humanize_number().


# 15a6c54c 19-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Synchronise with v1.73:

Remove from the printfns the assumption that dp->list != NULL. Even
if there are no entries, these functions may be called to print the
total number of blocks (0) for consis

Synchronise with v1.73:

Remove from the printfns the assumption that dp->list != NULL. Even
if there are no entries, these functions may be called to print the
total number of blocks (0) for consistency's sake.

show more ...


# aae9ea87 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Synchronise with FreeBSD:

Treat filenames as multibyte character strings (according to the current
LC_CTYPE setting) when determining which characters are printable.
This is an often-requested featu

Synchronise with FreeBSD:

Treat filenames as multibyte character strings (according to the current
LC_CTYPE setting) when determining which characters are printable.
This is an often-requested feature.

Use wcwidth() to determine the number of column positions a character
takes up, although there are still a few places left where we assume
1 byte = 1 column position, e.g. line-wrapping when handling the -m option.

The error handling here is somewhat more complicated than usual: we do
our best to show what we can of a filename in the presence of conversion
errors, instead of simply aborting.

show more ...


# 20d719bf 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Synchronise with FreeBSD:

Bump Id where needed.

Constify parameters that do not get touched.

Do something sensible if both -h and -k are given.

If we are asked to print the total number of blocks

Synchronise with FreeBSD:

Bump Id where needed.

Constify parameters that do not get touched.

Do something sensible if both -h and -k are given.

If we are asked to print the total number of blocks, do so even if we
have no entries to print (either due to an empty directory or an
error). This makes the -l and -s options more consistent, like
Solaris and (Debian) Linux. To make this happen, tweak two
optimizations on the second call to display():

- Don't skip display() altogether, even if list == NULL.
- Don't skip the call to the printfn in display() if we
need to print the total.

Small clean ups and casts.

show more ...


# b534d61c 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Synchronise with FreeBSD:

make printlink()'s FTSENT parameter const, it doesn't get modified at all
during the function call, reflect that.

Use the unit_t typedef for the unitp array.

Use u_int fo

Synchronise with FreeBSD:

make printlink()'s FTSENT parameter const, it doesn't get modified at all
during the function call, reflect that.

Use the unit_t typedef for the unitp array.

Use u_int for unit_sz as other unsigned integers do.

Cast ilogb()'s return value to u_int to match unit_sz (ilogb() returns an int).

Cast UNIT_MAX to u_int because enum types are int.

show more ...


# b03b411e 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Use warnx() instead of home-rolled fprintf() constructions.
Update FreeBSD Id.


# 05695ef9 18-Sep-2005 Jeroen Ruigrok/asmodai <asmodai@dragonflybsd.org>

Make len size_t, since strlen() returns a size_t, case i to size_t later
on to silence a comparison warning.


12