From: Drew Adams <drew.adams@oracle.com>
To: dont.spam.earl@gmail.com, help-gnu-emacs@gnu.org
Subject: RE: Looking for universal completion with simple UI
Date: Mon, 20 Oct 2014 14:48:47 -0700 (PDT) [thread overview]
Message-ID: <921ac557-18b4-423e-bad3-e67bf1c74788@default> (raw)
In-Reply-To: <8550d216-7396-40ac-b690-997bb334a0a4@default>
I said:
> Second, as to whether you can create your own "customizations
> to the interface" and share them with others:
>
> Of course you can, respecting the GNU Public License that the
> code is distributed under. That's the whole point of GNU and
> the GPL: freely sharing source code in a reasonable and
> freedom-respecting manner.
>
> There are by design "a variety of ways to get started with"
> Icicles. Setting different combinations of option values
> gives you different such ways ("starter kits"). Different
> combinations "reflect different people's perspectives on
> how" to use (or to get started with) Icicles. If you want
> to share your preferred combination with others and call
> that the "Earl Icicles Starter Kit", go for it. No problem.
>
> Likewise, if you want to customize or enhance the Icicles
> code in some way that appeals to you, and then share your
> customization code, go for it (respecting the GPL). You
> are also welcome to submit enhancement requests for this
> or that feature or change to be made to the Icicles code.
...
> And no, there is nothing wrong with sharing your own
> preferred default values, or values that you think might
> be helpful as defaults for some particular set of Icicles
> users, whether starters or others.
>
> In sum, I am open wrt concrete suggestions about Icicles
> default values. Alternatively, you are welcome to publish
> your own recommended set of default values. HTH.
I should be clear too that the Icicles code is copyrighted,
in addition to being published under the GPL. I think you
are essentially asking about sharing your personal settings
of Icicles options as a sort of suggested Icicles "starter
kit" for others, which is certainly OK.
You have posted here only anonymously, Earl. If you have
concerns or questions about customizing or sharing Icicles
code, please mail me directly. Thx.
next prev parent reply other threads:[~2014-10-20 21:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-05 20:26 Looking for universal completion with simple UI dont.spam.earl
2014-10-06 3:28 ` Drew Adams
[not found] ` <mailman.10545.1412566158.1147.help-gnu-emacs@gnu.org>
2014-10-06 4:40 ` dont.spam.earl
2014-10-06 5:02 ` Eric Abrahamsen
2014-10-06 5:53 ` Drew Adams
[not found] ` <mailman.10546.1412571788.1147.help-gnu-emacs@gnu.org>
2014-10-07 15:38 ` dont.spam.earl
2014-10-07 16:51 ` Eric Abrahamsen
[not found] ` <mailman.10548.1412574805.1147.help-gnu-emacs@gnu.org>
2014-10-07 15:39 ` dont.spam.earl
2014-10-08 16:49 ` Drew Adams
[not found] ` <mailman.10751.1412786977.1147.help-gnu-emacs@gnu.org>
2014-10-17 15:19 ` dont.spam.earl
2014-10-17 16:31 ` Drew Adams
2014-10-20 21:48 ` Drew Adams [this message]
[not found] ` <mailman.11604.1413841750.1147.help-gnu-emacs@gnu.org>
2014-10-30 21:09 ` dont.spam.earl
2014-10-08 5:42 ` Tu, Do
2014-10-17 15:18 ` dont.spam.earl
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=921ac557-18b4-423e-bad3-e67bf1c74788@default \
--to=drew.adams@oracle.com \
--cc=dont.spam.earl@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).