From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: d.love@dl.ac.uk, emacs-devel@gnu.org
Subject: Re: TODO additions
Date: Tue, 29 Oct 2002 14:02:09 -0500 [thread overview]
Message-ID: <200210291902.g9TJ2AY18220@rum.cs.yale.edu> (raw)
In-Reply-To: E185wzJ-0000zO-00@fencepost.gnu.org
> * Convert the XPM bitmaps to PPM, replace the PBMs with them and scrap
> the XPMs so that the colour versions work generally. (Requires care
> with the colour used for the transparent regions.)
>
> Could someone explain what good this would do? I don't know much
> about these image formats.
The PPM format is supported by all Emacsen, whereas the XPM format
is only supported if you have the libXpm library.
> * Use automake and use autoconf fully, preferably avoiding src/{m,s}
> entirely. [Maintaining the build process _is_ a major problem.]
>
> I don't think this would make it easier. It might be harder,
> because it would require solving every problem in a general way.
We have already installed changes that make the configuration process
rely more on autoconf and less on src/{s,m}. We should keep going in
this direction because it makes things easier to handle. Whether we'll
ever be able to remove src/{s,m} is not relevant I think (it would be
good but is not a prerequisite to using autoconf/automake).
> * Do something to make rms happy with fx's dynamic loading, and use it
> to implement things like auto-loaded buffer parsers and database
> access in cases which need more than Lisp.
> The problem here is too fundamental to suppose it can necessarily be
> solved.
I find it distressing that GPL programs should not be able to dynamically
load a GPL library just because of some legal issues. I understand the
legal issues, but I still think that there has to be some way (either
technical or legal) to allow dynamic loading without endangering the
overarching goal of the FSF. I (and I guess Dave as well) can't try to
solve the problem on the legal side, but we can try to address it
technically.
Stefan
next prev parent reply other threads:[~2002-10-29 19:02 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-18 12:41 TODO additions Dave Love
2002-10-19 3:24 ` Miles Bader
2002-10-21 13:11 ` Stefan Monnier
2002-10-22 16:47 ` Dave Love
2002-10-21 13:07 ` Stefan Monnier
2002-10-21 13:21 ` Oliver Scholz
2002-10-22 14:14 ` Stefan Monnier
2002-10-22 17:03 ` Dave Love
2002-10-27 23:38 ` Richard Stallman
2002-10-29 18:04 ` Dave Love
2002-10-29 22:09 ` Miles Bader
2002-10-31 17:25 ` Richard Stallman
2002-11-05 10:59 ` Dave Love
2002-10-30 17:18 ` Richard Stallman
2002-10-31 7:21 ` Kai Großjohann
2002-10-31 9:12 ` Miles Bader
2002-11-01 9:40 ` Richard Stallman
2002-11-01 13:06 ` Kai Großjohann
2002-11-03 13:57 ` Richard Stallman
2002-10-31 18:19 ` Dave Love
2002-11-02 3:32 ` Richard Stallman
2002-11-11 20:15 ` Dave Love
2002-11-12 13:18 ` Miles Bader
2002-11-14 4:10 ` Richard Stallman
2002-11-17 22:47 ` Dave Love
2002-10-30 17:18 ` Richard Stallman
2002-10-31 18:42 ` Dave Love
2002-11-02 3:31 ` Richard Stallman
2002-11-05 11:37 ` Dave Love
2002-10-29 19:02 ` Stefan Monnier [this message]
2002-10-31 17:27 ` Richard Stallman
2002-10-31 18:10 ` Dave Love
2002-11-02 3:31 ` Richard Stallman
2002-11-05 11:33 ` Dave Love
2002-11-07 4:48 ` Richard Stallman
2002-11-07 10:33 ` Andreas Schwab
2002-11-08 12:06 ` Richard Stallman
2002-11-11 11:58 ` Andreas Schwab
2002-11-13 11:31 ` Richard Stallman
2002-11-17 22:49 ` Dave Love
2002-11-11 20:25 ` Dave Love
2002-11-13 11:32 ` Richard Stallman
2002-11-17 22:56 ` Dave Love
2002-11-18 19:09 ` Richard Stallman
2002-11-20 17:10 ` Dave Love
2002-11-21 17:12 ` Richard Stallman
2002-11-24 18:57 ` Dave Love
2002-11-25 12:36 ` Richard Stallman
2002-11-27 23:38 ` Dave Love
2002-11-29 15:04 ` Richard Stallman
2002-11-29 19:57 ` Dave Love
2002-12-01 9:16 ` Richard Stallman
2002-12-02 14:02 ` Dave Love
2002-12-05 15:10 ` Richard Stallman
2002-12-09 19:03 ` Dave Love
2002-12-12 17:09 ` Richard Stallman
2002-12-15 17:23 ` Dave Love
2002-12-01 9:16 ` Richard Stallman
2002-12-02 14:05 ` Dave Love
2002-12-02 15:47 ` Richard Stallman
2002-12-06 16:41 ` movemail re-write [was Re: TODO additions] Dave Love
[not found] ` <E18LD0N-0004Rc-00@fencepost.gnu.org>
2002-12-10 23:42 ` Dave Love
2002-12-16 10:49 ` Michael Sperber [Mr. Preprocessor]
2002-12-17 18:44 ` Richard Stallman
2002-12-18 9:35 ` Michael Sperber [Mr. Preprocessor]
2002-12-19 18:32 ` Richard Stallman
2002-12-02 15:47 ` TODO additions Richard Stallman
2002-12-03 10:58 ` Dave Love
2002-12-05 15:10 ` Richard Stallman
2002-11-29 15:04 ` Richard Stallman
2002-11-27 15:13 ` Francesco Potorti`
2002-11-28 1:43 ` Miles Bader
2002-11-28 5:45 ` Eli Zaretskii
2002-11-29 15:03 ` Richard Stallman
2002-11-29 15:59 ` Francesco Potorti`
2002-11-30 14:05 ` Richard Stallman
2002-11-07 4:48 ` Richard Stallman
2002-11-11 20:19 ` Dave Love
2002-11-13 11:32 ` Richard Stallman
2002-11-17 22:47 ` Dave Love
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=200210291902.g9TJ2AY18220@rum.cs.yale.edu \
--to=monnier+gnu/emacs@rum.cs.yale.edu \
--cc=d.love@dl.ac.uk \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).