From: "Greg J. Badros" <gjb@moa.cs.duke.edu>
To: Bruce Stephens <stephens@math.ruu.nl>
Cc: zsh-workers@math.gatech.edu
Subject: Re: patches to give colorized file listings
Date: Thu, 22 Aug 1996 10:07:34 -0400 (EDT) [thread overview]
Message-ID: <Pine.SOL.3.93.960822095931.26987C-100000@moa.cs.duke.edu> (raw)
In-Reply-To: <199608220951.LAA18845@cantecler.math.ruu.nl>
On Thu, 22 Aug 1996, Bruce Stephens wrote:
> I like it, but there are a couple of things I don't like.
>
> The technical one is that it seems to depend on the listtypes option,
> so I can either have colours and characters indicating the types, or
> characters indicating the types, or nothing. I'd like to be able to
> have just colours.
This is pretty doable, but since I use file types I attacked that side
first to see what other snags came up... few did, so I went forward. I
can easily add the code to both parts, or better, factor it out and make
it a little bit cleaner, too.
> The other one is an IPR problem: it uses the patch that gives the GNU
> fileutils package colourized ls (included in the latest fileutils), so
> what's the copyright position on this? Personally, I don't care, but I
> thought some people wanted to keep zsh from being infected with the
> GPL?
I looked through the color-ls patch, and have no idea what their copy
policy is. My distribution of the patch is a single gz file, so it's hard
to say. I've not been following the group long enough to know about a
history of GPL infection fright. :-) It's actually not that complicated
an ordeal, but I don't believe in reinventing the wheel, plus it'd be
confusing if zsh colorized listing worked differently that ls's. Anybody
know more about color-ls?
>
> --
> Bruce Stephens | email: B.Stephens@math.ruu.nl
Greg J. Badros
gjb@cs.duke.edu
next prev parent reply other threads:[~1996-08-22 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-22 9:51 Bruce Stephens
1996-08-22 14:07 ` Greg J. Badros [this message]
1996-08-22 14:17 ` Bruce Stephens
1996-08-22 14:27 ` Zefram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SOL.3.93.960822095931.26987C-100000@moa.cs.duke.edu \
--to=gjb@moa.cs.duke.edu \
--cc=stephens@math.ruu.nl \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).