public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Charles Wilson <cygwin@cwilson.fastmail.fm>
To: Mailing List: CygWin-Apps <cygwin-apps@cygwin.com>
Subject: Re: weft 0.4
Date: Thu, 26 Oct 2006 02:51:00 -0000	[thread overview]
Message-ID: <4540227B.9020601@cwilson.fastmail.fm> (raw)
In-Reply-To: <453FD916.6030709@users.sourceforge.net>

Frank Fesevur wrote:
> 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.

I think the problem is "sample bias". Most of the cygwin maintainers 
seem (to me) to be mostly focused on "getting unix stuff that I like to 
work on the bass-ackward platform called Windows".

I spend most of my "cygwin" time in a bash shell.  I've got oodles of 
scripts to automate things.  And I use either vi or xemacs to edit.

The only time I double-click something is (a) when I'm not "cygwinning" 
-- e.g. I'm using "regular windows" apps, or (b) cygwin setup.exe (c) my 
shortcuts to rxvt and the xserver.  I don't use chere.

So IMO *this audience* isn't very interested in 
[chere|weft|other-windows-integration].  That doesn't mean that the 
universe of cygwin users who are NOT maintainers have similar biases.

I'll try to review your package this weekend, and will report back here.

--
Chuck

  reply	other threads:[~2006-10-26  2:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25 20:46 Frank Fesevur
2006-10-25 21:00 ` Christopher Faylor
2006-10-25 21:37   ` Frank Fesevur
2006-10-26  2:51     ` Charles Wilson [this message]
2006-10-26  8:20     ` Oliver Wienand
2006-10-30 17:12     ` Dave
2006-10-30 21:56       ` Frank Fesevur
2006-11-02 17:51         ` Dave

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=4540227B.9020601@cwilson.fastmail.fm \
    --to=cygwin@cwilson.fastmail.fm \
    --cc=cygwin-apps@cygwin.com \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).