This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: weft 0.4


Frank Fesevur wrote:
> At 25-10-2006 23:00, Christopher Faylor wrote:
>> On Mon, Oct 23, 2006 at 07:08:51PM +0200, Frank Fesevur wrote:
>>> Two weeks ago I sent a message to this list, but there wasn't any
>>> reply.  http://cygwin.com/ml/cygwin-apps/2006-10/msg00029.html
> 
> But I find it a kind of strange that no one would be interested in it.
> chere does similar things. It helps to integrate Cygwin and Windows. And
> AFAICT, chere is received quite well. But no hard feelings. I wrote the
> package, it fits my own needs. I thought that others could benefit from
> it as well.

As chere maintainer I've had this on my TODO list for review, apologies
for the delay.

Comments on the package itself:

1. You've created a C++ program that essentially is just writing to the
registry. Have you considered scripting it instead? Then you can leave
the registry handling to regtool.

2. You have hardcoded the bash invocation line. It took a while to get
it right with chere. Issues that you'll find with the invocation you're
using:
  a) won't work on scripts in network paths
  b) won't play with ash or tcsh. Not a problem now since you're only
supporting bash.
  c) I don't think this plays well with spaces or '$' in a path (but I
could be wrong). Note '$' is commonly found in MS hidden network shares.

3. You're starting a login shell for every script you want to run.
Probably fine on a modern machine, but there's always someone trying to
eke out a performance gain.


More general:

weft will manage invoking scripts (or programs) which do not require
additional arguments directly from a particular shell. To add the
ability to handle a type of extension that does not want to be executed
by a shell (say for .pdf), the source of weft will need to be patched
and recompiled (and run to add the handler).

My feeling is that we need to have a single package which manages all
the explorer extensions anybody may want to add. I don't think the
package as proposed can easily be made to do this.

Together with the fact that I've never felt the need to execute a script
directly from Explorer, weft doesn't get my vote as it stands.

I have a work in progress which could do the generic management of
explorer extensions (see link below). As is typical, I haven't had time
to perfect it - but by all means, have a look at what I've done and
between us we might get this functionality into cygwin.



Regards,

Dave.

Sentry/XPIntegrate proposal:
http://www.cygwin.com/ml/cygwin-apps/2006-05/msg00103.html


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]