🚀 go-pugleaf

|> The fix is not indiscriminate bashing of trailing slashes, as
|> currently implemented.  The fix is to remove the generic truncation of
|> trailing slashes, then to fix whatever minor bugs prevent the use of
|> pathnames containing trailing slashes.
|
|Fix everyone's shells, or everyone's kernels?

I don't think there is anything to fix in either the shell or the
kernel. File completion in bash is just fine (I like getting trailing
slashes for directories), as is the behavior of the UNIX kernel of not
accepting trailing slashes in certain situations.

|I don't offhand see a
|better solution than what the GNU utilities currently do.  But
|specific suggestions are welcome.

I have come to rely on the fact that if I write "mv foo bar/" and "bar"
is a plain file, I get an error message, rather than have "mv" silently
remove "bar". What would you say if type checking were suddenly removed
from ANSI C?  

If you want this non-standard behavior in the GNU file utilities, maybe
you can make it optional via an environment variable.  I certainly
don't feel safe using the current GNU file utilities, and, furthermore,
I wonder what other dangerous "improvements" may have been made.

				Thomas.