This fixes a few issues with macros in ksh emacs input mode. I'm sure
it's not widely used but I'd be glad if someone could have a look at
it so I can get the diff out of my tree.
Ok, so what does it do? Here goes:
1. Expanding a macro containing characters that themselves are macros
$ bind -
I guess you're right. It seems like what df does currently is also
consistent with what posix says for a command like ls.
"Specifying more than one of the options in the following
mutually-exclusive pairs shall not be considered an error...
-t and -S. The last option specified in each pair shall d
I don't agree as this is the normal behaviour of most commands;
ls -St
ls -tS
ls -l1
ls -1l
ntpd -sS
ntpd -Ss
etc, etc.
/Alexander
Daniel Dickman wrote:
> I found it a little confusing that the order of the options for df
> can make a difference in the output. For example:
>
> [/usr/src/bin
I found it a little confusing that the order of the options for df
can make a difference in the output. For example:
[/usr/src/bin/df] df -hk .
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/sd0a 472403466 316700726 13208256871%/
[/usr/src/bin/df] df -kh .
Filesys
Here is another attempt at the drive bay eject code.. this one will detect
if the bay is already installed and do a better job of of identifying bay
devices.
Index: acpi.c
===
RCS file: /cvs/src/sys/dev/acpi/acpi.c,v
retrieving revisi
