From: Karl M <karlm30@hotmail.com>
To: <towo@towo.net>, <cygwin@cygwin.com>
Subject: RE: Please upload: mined-2000.16-0
Date: Mon, 14 Feb 2011 20:39:00 -0000 [thread overview]
Message-ID: <COL102-W147744EA35E8C37AE1C8B5B5D00@phx.gbl> (raw)
In-Reply-To: <4D598E78.5000002@towo.net>
> Date: Mon, 14 Feb 2011 21:20:08 +0100
> From: Thomas
> Subject: Re: Please upload: mined-2000.16-0
>
> Am 13.02.2011 23:25, schrieb Karl M:
> >
> >
> >
> >> Date: Sun, 13 Feb 2011 23:18:18 +0100
> >> From: Thomas
> >> Subject: Re: Please upload: mined-2000.16-0
> >>> The reason is that, at least on Windows 7, there is no key called
> >>> HKEY_CURRENT_USER\Software\Classes\SystemFileAssociations.
> >>>
> >>> The result is that a user of Windows 7 gets a postinstall warning from
> >>> setup.exe because the mined postinstall script returns a non-zero exit
> >>> code.
> >>>
> >>>
> >>> Corinna
> >> Hi, thanks for the notice.
> >> Actually I'm aware that there is this postinstall return problem also in
> >> Windows XP and I've fixed it but the code base isn't quite ready yet for
> >> the next release - can it still wait for a short while?
> >> On the other hand, if the key doesn't exist because the mechanism has
> >> changed in Windows 7, I'm not sure what to do because I don't have W7
> >> myself for testing - any advice by someone? Just some other key name
> >> perhaps?
> > Why is mined by default messing with this? Isn't this something that the user should run if he/she wants to alter file associations/context menu stuff?
> I once discussed this with Andy and felt encouraged to do so - after
> all, non-expert users will not normally make such an entry because there
> is no tool to do it easily (I think).
> But I'll reconsider and maybe confine it to the stand-alone package.
>
Thanks for considering it. I think that a script that the used could run after installation would be fine. I don't use it, so it does not impact me directly. But I would not have expected that installing an editor in Cygwin would change windows file associations. I use vi in Cygwin, but would not want that to change my file associations.
Thanks,
...Karl
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2011-02-14 20:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0M3MGG-1NSYIM09lw-00rakK@mrelayeu.kundenserver.de>
[not found] ` <20110213163515.GB20855@calimero.vinschen.de>
[not found] ` <4D5858AA.8030502@towo.net>
2011-02-13 22:25 ` Karl M
2011-02-14 20:20 ` Thomas Wolff
2011-02-14 20:39 ` Karl M [this message]
2011-02-14 21:07 ` Khan, Waseem A
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=COL102-W147744EA35E8C37AE1C8B5B5D00@phx.gbl \
--to=karlm30@hotmail.com \
--cc=cygwin@cygwin.com \
--cc=towo@towo.net \
/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).