On Wed, Feb 17, 2016 at 08:48:25PM +, Dimitris Papastamos wrote:
>
> what about ls -R .///
>
That's normal behavior, the GNU ls doesn't trim more than one excessive
slash either. I guess it's also ok not to trim them at all, and expect
the user not to end directories with a slash.
Here's a better version of the patch.
When the R flag is used with a single directory, the given directory name is
omitted. With multiple directories each directory name is listed.
Directories that start with './' and '../' are now also printed.
---
ls.c | 2 +-
1 file changed, 1 insertion(+), 1
On Wed, Feb 17, 2016 at 04:57:12PM +, Dimitris Papastamos wrote:
> Actually, upon second thought I prefer the current behaviour
> because the output is actually parsable.
>
> This dir:\n stuff is just insane.
>
The current version is broken though, it outputs "./" where there would
be a
Here's the patch with updated manpage and usage().
---
sort.1 | 8 +++-
sort.c | 63 ++-
2 files changed, 69 insertions(+), 2 deletions(-)
diff --git a/sort.1 b/sort.1
index 8fd5ee9..52c73dc 100644
--- a/sort.1
+++ b/sort.1
@@