From: Joni Eskelinen <jonieske@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] cygregext (formerly cygscript)
Date: Fri, 28 Apr 2017 08:08:00 -0000 [thread overview]
Message-ID: <efb68507-9fc0-1d9b-107f-7b6f161805b6@gmail.com> (raw)
In-Reply-To: <8568023f-c95b-1809-44da-efe26d59c0e1@gmail.com>
Hi all,
I've renamed cygscript as proposed. Hopefully cygregext conveys its
purpose more clearly. A man page has also been added.
Repository has been moved to https://github.com/sop/cygregext.
Packages are available for inspection at http://eske.fi/cygregext/.
On 20.4.2017 8.24, Joni Eskelinen wrote:
> On 19.4.2017 20.00, Jon Turney wrote:
>> On 30/03/2017 06:54, Joni Eskelinen wrote:
>>> Dear maintainers,
>>>
>>> Cygscript is an utility program allowing to register file types to be
>>> executed in Cygwin when double clicked from File Explorer or when a file
>>> is dragged and dropped to a registered file type.
>>>
>>> Any file type can be registered. Scripts are executed with bash in
>>> MinTTY terminal. Windows paths passed as arguments (eg. when dragged and
>>> dropped) are automatically detected and translated to POSIX paths.
>>
>> Thank you for your patience and sorry about the delay.
>>
>> Nice work. I'm kind of surprised we don't have something like this
>> already.
>
> Thanks! I'm surprised too, since there's a lot of kinda hackish Windows
> batch file solutions that are not generic nor easy to install.
> TBH i'd rather see this feature implemented as a part of MinTTY.
>
>> How attached are you to the name? I know this is not a concept which
>> lends itself easily to a short name, but perhaps something which makes
>> the purpose a little more obvious is possible?
>
> I settled on cygscript after a few iterations, but it's trivial to
> change at this point. It's hard to come up with something that is not
> bulky. Although this not a command one has to type often, so it wouldn't
> matter if it had a longer name. I'd gladly hear suggestions.
>
>>> Please see the github page for further details.
>>
>> It would be nice if there was a manpage included in the package.
>
> I'll write and bundle a manpage in the near future.
>
>>> This application is not included in any other distro, so i reckon a vote
>>> must be first passed.
>>
>> +1
>>
>>>
>>> I am the sole developer and maintainer of the project at the moment.
>>>
>>> The source is released under MIT License.
>>>
>>> Homepage:
>>> https://github.com/sop/cygscript
>>>
>>> Packages:
>>> http://eske.fi/cygscript/
>>>
>>> # cygscript-1.0.2-1.hint
>>> category: Utils
>>> requires: cygwin libgcc1 libstdc++6 mintty bash
>>> sdesc: "Run shell scripts from Windows File Explorer"
>>> ldesc: "A helper program allowing to register an extension (eg. .sh)
>>> to be executed in Cygwin by double-clicking a file from Windows File
>>> Explorer
>>> or by dragging and dropping files to an icon of a registered extension."
next prev parent reply other threads:[~2017-04-28 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 5:54 [ITP] cygscript Joni Eskelinen
2017-04-19 17:00 ` Jon Turney
2017-04-20 5:24 ` Joni Eskelinen
2017-04-28 8:08 ` Joni Eskelinen [this message]
2017-04-28 20:30 ` [ITP] cygregext (formerly cygscript) Marco Atzeri
2017-04-28 20:46 ` Eric Blake
2017-04-29 11:54 ` Jon Turney
2017-05-03 6:13 ` Joni Eskelinen
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=efb68507-9fc0-1d9b-107f-7b6f161805b6@gmail.com \
--to=jonieske@gmail.com \
--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).