summaryrefslogtreecommitdiffstats
path: root/bin/ls
Commit message (Collapse)AuthorAgeFilesLines
* Drop support for -DRELEASE_BUILD_FIXIT and -DCRUNCHED_BINARY inru2001-04-031-1/+1
| | | | ${CFLAGS}. The only supported method thus is -DRELEASE_CRUNCH.
* Silence minor cc warningache2001-03-211-1/+1
|
* Use nl_langinfo instead of %Efache2001-03-211-6/+7
|
* mdoc(7) police: use the default ``file ...'' feature of the .Ar macro.ru2001-02-131-1/+1
|
* mdoc(7) police: split punctuation characters + misc fixes.ru2001-02-011-2/+2
|
* grammar gnit: "relationships (plural) _are_ complex"hoek2000-12-281-1/+1
|
* Prepare for mdoc(7)NG.ru2000-12-151-2/+2
|
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-201-2/+2
|
* Un-deprecate the -G flag at obrien's request. Colour sequences are stilljoe2000-08-132-11/+20
| | | | | dependent upon the output being directed to a terminal however. (Use the CLICOLOR_FORCE variable to force output).
* Correct spelling: depricated -> deprecated.joe2000-08-122-2/+2
|
* A change to the way that colours are switched on in ls. The -Gjoe2000-08-122-44/+54
| | | | | | | | | | | | | | flag has been depricated, although it still works with a warning message, and replaced with an environment variable CLICOLOR (command line interface colour). This could be used by other tools that want to be able to control colour output. In addition if the environment variable CLICOLOR_FORCE is defined colour sequences are output irrespective of whether the output is directed to a terminal (as long as TERM references a colour capable terminal of course ;) PR: bin/20291 and bin/20483
* ".It" -> ".It Ev" in a couple of places.joe2000-08-121-2/+2
|
* Add the missing flags to ls(1)'s usage: -Bb.green2000-07-221-2/+2
|
* Explain the dependence of colour support on the capabilities of thesheldonh2000-07-071-0/+20
| | | | | | | | | | terminal emulator. As pointed out by jhb, a more scalable solution would be preferable when multiple applications in the base system begin linking against libh. Submitted by: Doug Barton <DougB@gorean.org>
* make sure we do not write out non-printable characters in file namesassar2000-07-045-25/+36
| | | | | | | and symbolic links (by default) PR: bin/19354 Reviewed by: silence on -current
* Fix changes from 1.34 through 1.37:sheldonh2000-06-221-6/+14
| | | | | | Remove newly added hard sentence breaks. Mark ANSI up as a type name (Tn). Avoid parenthesized sentences and paragraphs.
* Order the ENVIRONMENT section alphabetically.joe2000-06-211-5/+5
|
* I broke locale sensitive ordering of date and month injoe2000-06-212-6/+16
| | | | | | | | | | the long -l output format with the last commit. Fix it by replacing the "%b %e" strftime format with "%Ef". Make a note in the manual page that the LANG environment variable affects the running of ls. Reviewed by: ache
* Don't assume that the output of strftime for "%c" ("nationaljoe2000-06-181-15/+10
| | | | | | | | | representation of time and date") won't change in time. Instead of hard coding the locations of the time elements and hoping that they don't move use strftime to generate the desired formats in the first place. PR: bin/7826
* Switch over to using the new fflagstostr and strtofflags library calls.joe2000-06-173-6/+9
|
* Fix one conditionalization in my prev. commitache2000-06-061-2/+3
|
* Greately simplify oxtabs fix by simple setting f_notabs for f_colorache2000-06-062-14/+10
|
* Honor f_notabs flag even in COLORLSache2000-06-061-1/+1
|
* Back out spaces to TABs replace removing for COLORLSache2000-06-061-0/+13
| | | | | Rewrite corresponding comment to say what happens in reality with oxtabs and current terminal column.
* Don't replace TABs with spaces for COLORLS because "some terminals get confused"ache2000-06-061-12/+0
| | | | | as comment says. I know no terminal confused by this. If even such terminal exists, it must be termcap flag for this, not hardcoded in ls.
* Add -G to usage: if COLORLSache2000-06-061-1/+6
|
* Staticize more functionsache2000-06-061-4/+7
|
* Move colorquit() prototype to extern.hache2000-06-062-4/+4
| | | | | Add "extern" to variables declarations in extern.h to not make them commons into each compiled file.
* Make signal handler safe - don't use stdio (pointed by bde)ache2000-06-062-14/+26
| | | | | | Staticize some color functions Add yet one tolower() call which is forgotten after check Don't check for OOPS - not really needed
* Reflect reality:ache2000-06-061-2/+2
| | | | | yellow -> brown white -> light grey
* Get rid of curses completely - use tgoto instead of tparmache2000-06-051-5/+4
|
* Do SIGINT cleanup for SIGQUIT as well.cracauer2000-06-051-0/+1
|
* Kill yourself in ^C handler, not exit(1) to allow script to sense signalache2000-06-051-7/+10
|
* Cosmetique of prev. optimization - don't use global variableache2000-06-051-1/+6
|
* Don't use curses includes, include termcap.h insteadache2000-06-051-13/+26
| | | | | | | Don't use curses functions, use tputs instead Add ^C reaction - reset colors Optimization - don't turn off colors after EACH file printed. Fix wrong ctype macro arg type in LSCOLORS parsing
* Don't use curses includes, include termcap.h insteadache2000-06-051-6/+7
| | | | Add ^C reaction set
* Don't use ncurses, use termcapache2000-06-051-1/+2
| | | | Add DPADD
* Don't look up the ANSI sequences each time a colour is changed,joe2000-06-053-11/+31
| | | | | | | | | | | this is extremely inefficient, instead write them all down at the beginning. The correct sequence to switch colours off is to first use 'op' if it exists, otherwise use 'oc'. If neither of these exist then we shouldn't be doing colour with this terminal. Reviewed by: ache
* Disable colour support in ls when building the fixit floppy, and makejoe2000-06-051-0/+2
| | | | a note of it in the release Makefile.
* * Re-implement colour support using termcap's AF and AB capabilitiesjoe2000-06-055-12/+74
| | | | | | | | | | | | | to manage the ANSI colour sequences. Colour support is disabled unless the TERM environment variable references a valid termcap. * Allow optional compilation of the colour support in the Makefile, defaulting to yes. This allows us to switch it off for fixit floppies and other mediums where space is an issue and the extra bloat of statically linking with ncurses isn't acceptable. * Display a warning if colour is requested with '-G' but support for it isn't compiled in.
* Add colour support to /bin/ls (at a cost of 1056 bytes on my system).joe2000-06-025-4/+220
| | | | | | | | | | | | | | It is not switched on by default and must be enabled with the -G flag. When using ls -G the output behaviour is modified with ANSI colour sequences wrapped around filenames to help distinguish file types. (Colours can be redefined in the LSCOLORS environment variable as described in the manual page.) Colour support is silently disabled (if switched on) if stdout isn't a tty. Based on: asami's colorls port. PR: bin/18900 && ports/18616.
* Remove more single-space hard sentence breaks.sheldonh2000-03-021-3/+6
|
* Remove single-space hard sentence breaks. These degrade the qualitysheldonh2000-03-011-2/+4
| | | | | of the typeset output, tend to make diffs harder to read and provide bad examples for new-comers to mdoc.
* Revert part of the last commit, remove {g|s}etflags from the libcjoe2000-02-052-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | interface, and statically link them to the programs using them. These functions, upon reflection and discussion, are too generically named for a library interface with such specific functionality. Also the api that they use, whilst ok for private use, isn't good enough for a libc function. Additionally there were complications with the build/install-world process. It depends heavily upon xinstall, which got broken by the change in api, and caused bootstrap problems and general mayhem. There is work in progress to address future problems that may be caused by changes in install-chain tools, and better names for {g|s}etflags can be derived when some future program requires them. For now the code has been left in src/lib/libc/gen (it started off in src/bin/ls). It's important to provide library functions for manipulating file flag strings if we ever want this interface to be adopted outside of the source tree, but now isn't necessarily the right moment with 4.0-release just around the corner. Approved: jkh
* Historically file flags (schg, uschg, etc) have been converted fromjoe2000-01-272-4/+1
| | | | | | | | | | | | | | | | | string to u_long and back using two functions, flags_to_string and string_to_flags, which co-existed with 'ls'. As time has progressed more and more other tools have used these private functions to manipulate the file flags. Recently I moved these functions from /usr/src/bin/ls to libutil, but after some discussion with bde it's been decided that they really ought to go in libc. There are two already existing libc functions for manipulating file modes: setmode and getmode. In keeping with these flags_to_string has been renamed getflags and string_to_flags to setflags. The manual page could probably be improved upon ;)
* Print negative minor numbers in hex. Negative minor numbers arebde2000-01-061-2/+3
| | | | | essentially large unsigned ones, and we already print minor numbers > 255 in hex.
* Added missing DPADD's. Removed unrequired SRCS's.joe2000-01-011-0/+1
| | | | Obtained from: bde
* Retire stat_flags.c; it's now in libutil.joe1999-12-301-149/+0
|
* Moved flags_to_string and string_to_flags into libutil. It's used injoe1999-12-301-1/+3
| | | | many places nowadays.
* Fix a bug where a pointer would be one character too far after puttingroberto1999-12-211-1/+1
| | | | | | a '\0' at the end of a string. Submitted by: Martin Birgmeier <Martin.Birgmeier@aon.at>
OpenPOWER on IntegriCloud