On Thu, Jun 28, 2012 at 08:35:18AM -0400, Kjell Wooding wrote:
> Thoughts, since we have been down this road before.
> 
> 1. You can remap keys, in your ~/.mg file
> 
> 2. I should point out that all of mg (other than theo.c) is currently
> PUBLIC DOMAIN, not merely BSD, so this change is significant, license-wise.
> Please be pedantic about including licenses.
> 
> 3. Why scheme? Yes, emacs uses Lisp. But seriously, so? Why not just add,
> say, perl bindings?
> 
> 4. Seriously, please be pedantic about licenses. Part of me dies when we
> see a new source file without one.
> 
> I'm all for adding support for scripting into mg, though I would be tempted
> to rip out all nonessential functionality first (ng? ;) and add it back via
> the scripting language. I would think the goal should be to make mg
> significantly *smaller* any such change
> 
> -kj
Regarding the licenses, Kettenis pointed out I forgot to add the original
copyright headers, which I have since added to my local repo.

It's reproduced here for reference:

Copyright (c) 2000, Dimitrios Souflis
All rights reserved.

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:

Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.

Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.

Neither the name of Dimitrios Souflis nor the names of the
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR 
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR 
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, 
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, 
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR 
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF 
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS 
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

I'm totally fine with putting mgscheme.c into the public domain, if tedu
agrees too of course.

> On Thursday, June 28, 2012, Loganaden Velvindron wrote:
> 
> > If Jasper is going to take care of it, why not :-) ?
> >
> > I'd like to get the ability to remap keys, without hacking src.
> >
> > (As an mg user)
> >
> > On Thu, Jun 28, 2012 at 2:06 PM, Mark Lumsden 
> > <m...@showcomplex.com<javascript:;>>
> > wrote:
> > >> Here is an updated diff for mg with tinyscheme integration. It's based
> > on
> > >> tedu's original diff with various tweaks and changes. For those worried
> > about
> > >> mg being too bloated, rest assured, it's still small and lean and a big
> > part
> > >> smaller than vi ;-)
> > >> It's not fully possible to turn mg into your mail client, but I'd like
> > to commit
> > >> this diff and work on it futher in tree (not the mail-client thing,
> > that would
> > >> bloat mg and that's far from desired).
> > >>
> > >> Includes some fixes by lum@ and Sunil Nimmagadda too.
> > >>
> > >> Diff is also at http://crappydiffs.org/tinyschemg.diff
> > >>
> > >
> > > I would appreciate some feedback on the inclusion of this diff in mg
> > > since I am unlikely to use tinyscheme myself but can see why others
> > > would like it added. Are there are strong feelings about it either
> > > way?
> > >
> > > -lum
> > >
> >
> >
> >
> > --
> > Brightest day,
> > Blackest night,
> > No bug shall escape my sight,
> > And those who worship evil's mind,
> > be wary of my powers,
> > puffy lantern's light !
> 

-- 
Cheers,
Jasper

"Stay Hungry. Stay Foolish"

Reply via email to