From: "Arne Babenhauserheide (IMK)" <arne.babenhauserheide@kit.edu>
To: Noah Lavine <noah.b.lavine@gmail.com>
Cc: "15221@debbugs.gnu.org" <15221@debbugs.gnu.org>
Subject: bug#15221: provide a mechanism to activate readline systemwide
Date: Tue, 3 Sep 2013 10:52:42 +0200 [thread overview]
Message-ID: <5225A35A.3070004@kit.edu> (raw)
In-Reply-To: <CA+U71=NEwMXY_j5io_MNiMKUXL2Ff_Mo6GyVnbWTnPjb6DSdPw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2624 bytes --]
I am not a lawyer either, but I know that the license of the executable
does not place restrictions on the license of the guile-specific code
(as long as that code is GPL-compatible).
Best wishes,
Arne
Am 30.08.2013 17:49, schrieb Noah Lavine:
> I am not a lawyer, but it seems to me that libguile could be under LGPL,
> but guile the executable could be under GPL, and therefore use readline
> by default.
>
> As you say, there would have to be an option to turn it off. Maybe
> --no-readline?
>
> Noah
>
>
> On Fri, Aug 30, 2013 at 10:01 AM, <dsmich@roadrunner.com
> <mailto:dsmich@roadrunner.com>> wrote:
>
>
> ---- "Arne Babenhauserheide (IMK)" <arne.babenhauserheide@kit.edu
> <mailto:arne.babenhauserheide@kit.edu>> wrote:
> > Hi,
> >
> > Not having readline at the guile interpreter from the get-go in a GNU
> > environment was a quite scarring experience for me, so it would be
> great
> > to have a way to enable readline by default.
> >
> > init.scm could provide that, but:
> >
> > <wingo> it seems to search the load path for init.scm
> > <wingo> before loading anything else
> > <wingo> tricky though, apparently that happens even before loading
> boot-9
> >
> > Ideally there should be either a compileflag or a systemwide
> config file
> > to enable readline support in the whole system. If it is a
> compile-flag
> > it might be useful to not make it default, because developers why
> > develop proprietary applications could then by accident compile a
> > program with activated readline support.
> >
> > If such a flag existed, most GNU/Linux distributions could simply
> > activate it for guile itself (as long as they do not ship unfree
> scripts
> > using guile which depend on readline support — those scripts would
> > violate the GPL, but they would not work at all without readline
> > support, so this dependency should be pretty clear).
>
> Sometimes readline gets in the way, for example, when using guile
> with emacs.
>
> If it was enabled by default, then there also must be an option to
> disable it when not needed.
>
> The main reason readline is not enabled by default (IIRC), is the
> license differences between readline and guile. (GPL and LGPL)
>
> -Dale
>
>
>
>
>
--
Doktorand
Gruppe: GHG
Raum: 435/410
Tel.: +49 721 608-22885
arne.babenhauserheide@kit.edu
Karlsruher Institut für Technologie
IMK-ASF
Postfach 36 40
76021 Karlsruhe
[-- Attachment #1.2: 0xA70DA09E.asc --]
[-- Type: application/pgp-keys, Size: 1893 bytes --]
[-- Attachment #1.3: arne_babenhauserheide.vcf --]
[-- Type: text/x-vcard, Size: 366 bytes --]
begin:vcard
fn:Arne Babenhauserheide
n:Babenhauserheide;Arne
org:KIT;GHG, IMK-ASF
adr;quoted-printable:;;Geb=C3=A4ude 435, Raum 410, Campus Nord;Karlsruhe;BW;76021;Deutschland
email;internet:arne.babenhauserheide@kit.edu
title:Doktorand
tel;work:+49 721 608-22885
x-mozilla-html:FALSE
url:http://www.imk-asf.kit.edu/874_1194.php
version:2.1
end:vcard
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]
next prev parent reply other threads:[~2013-09-03 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 13:04 bug#15221: provide a mechanism to activate readline systemwide Arne Babenhauserheide (IMK)
2013-08-30 14:01 ` dsmich
2013-08-30 15:49 ` Noah Lavine
2013-09-03 8:52 ` Arne Babenhauserheide (IMK) [this message]
2018-09-07 18:22 ` bug#15221: reiterating the request Tom Tromey
2018-09-07 20:32 ` Mark H Weaver
2018-09-07 23:10 ` Tom Tromey
2018-09-08 3:35 ` David Pirotte
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5225A35A.3070004@kit.edu \
--to=arne.babenhauserheide@kit.edu \
--cc=15221@debbugs.gnu.org \
--cc=noah.b.lavine@gmail.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).