From: Jon Turney <jon.turney@dronecode.org.uk>
To: "© Fxzx mic" <fxzxmic@outlook.com>,
"The Cygwin Mailing List" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: setup (2.917)
Date: Mon, 31 Jan 2022 12:13:24 +0000 [thread overview]
Message-ID: <8012ebad-acb2-72e6-3dad-8b7273262a05@dronecode.org.uk> (raw)
In-Reply-To: <OS3P286MB18556235885AB71E12976510B4259@OS3P286MB1855.JPNP286.PROD.OUTLOOK.COM>
> On 31.01.2022 06:36, © Fxzx mic wrote:
>> Hello,
>> I want to know how to change the default value of the check boxes when creating a program shortcut after installation so that it is no longer checked by default.
>> Which part of the program needs to be changed?
>>
[...]>
> Can you please clarify with an example ?
> Which shortcut do you mean ?
>
> Maybe you should look on the Command Line options for already available
> options :
>
> $ ./setup-x86_64.exe --help
> Cygwin setup 2.917
>
> Command Line Options:
>
> ...
> -d --no-desktop Disable creation of desktop shortcut
> ...
On 31/01/2022 06:43, © Fxzx mic wrote:
>
> After installing (or updating) through the GUI, the program will
> finally have two check boxes to choose whether to create shortcuts,
> and the default status of these two check boxes is checked. I just
> want to know how to cancel this default behavior. I want to know
> where this behavior is written in the setup program source code.
If you search for that option text in the source code you'll end up
looking at:
https://cygwin.com/git/?p=cygwin-apps/setup.git;a=blob;f=desktop.cc
Note that a patch to simply reverse the default setting of that option
(i.e. make it unset by default, and require the user to click that
checkbox to create the shortcuts (meaning that most users will have to
do that) would not be acceptable.
Probably what's wanted is to remember the state of those checkboxes, if
this isn't the first time setup has been run?
next prev parent reply other threads:[~2022-01-31 12:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 20:02 Jon Turney
2022-01-27 7:28 ` Shaddy Baddah
2022-01-28 14:56 ` Jon Turney
2022-01-31 3:06 ` Shaddy Baddah
2022-01-31 5:36 ` © Fxzx mic
2022-01-31 6:25 ` Marco Atzeri
2022-01-31 6:43 ` © Fxzx mic
2022-01-31 8:20 ` Samuel Lelièvre
2022-01-31 12:13 ` Jon Turney [this message]
2022-01-31 15:46 ` Andrey Repin
2022-01-31 19:56 ` Brian Inglis
2022-01-24 22:49 Buchbinder, Barry (NIH/NIAID) [E]
2022-01-24 23:12 ` Bill Stewart
2022-01-25 22:33 Buchbinder, Barry (NIH/NIAID) [E]
2022-01-26 8:47 ` Adam Dinwoodie
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=8012ebad-acb2-72e6-3dad-8b7273262a05@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=fxzxmic@outlook.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).