From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Consolidation of image support (was Re: Emacs on MAC OS X 10.3)
Date: 18 Dec 2003 17:42:24 +0100 [thread overview]
Message-ID: <m3r7z2jcwf.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <wlsmjii5zn.wl@church.math.s.chiba-u.ac.jp>
YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> writes:
> >>>>> On 18 Dec 2003 01:53:20 +0100, Kim F. Storm said:
>
> > Be aware that I plan (in the near future) to take out the image
> > support code from xfns.c, w32fns.c and macfns.c and consolidate it in
> > a new image.c file.
> >
> > That should reduce 15000 lines of code to approx 5500 lines.
> >
> > It seems that most of the image code in macfns.c isn't actually
> > used/ported yet, so it would be a good thing to consolidate the code
> > before finishing the image support for MAC.
>
> Actually, I've been porting the image support code to Carbon Emacs,
That will make MAC users happy I suppose :-)
> and I think it's almost ready now although some features are not
> implemented yet. I was planning to send the patch as soon as my
> assignment paper is accepted, and currently I'm waiting for the form
> to be delivered to me. Should I send the patch now?
No need to do so.
I don't expect to actually work on the consolidation until CVS is back
up again. I want to be sure to get any fixes to that people -- like
yourself -- may have laying around waiting to be committed before I
start.
> Many parts in
> macfns.c is almost identical with those in xfns.c.
I would have expected that (otherwise there would be no reason to
consolidate the code :-)
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2003-12-18 16:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 13:57 Consolidation of image support (was Re: Emacs on MAC OS X 10.3) YAMAMOTO Mitsuharu
2003-12-18 16:42 ` Kim F. Storm [this message]
2004-01-13 12:10 ` Image support for Carbon Emacs (Re: Consolidation of image support) YAMAMOTO Mitsuharu
2004-01-13 15:55 ` Stefan Monnier
2004-01-19 11:53 ` YAMAMOTO Mitsuharu
2004-01-28 12:48 ` Sébastien Kirche
2004-01-28 18:07 ` Steven Tamm
2004-01-14 0:20 ` Kim F. Storm
2004-01-15 21:22 ` Richard Stallman
2004-01-16 4:22 ` Steven Tamm
2004-01-16 19:54 ` Richard Stallman
2004-01-16 0:54 ` Image support for Carbon Emacs Hans-Peter Binder
2004-01-16 5:05 ` YAMAMOTO Mitsuharu
2004-01-16 10:44 ` Hans-Peter Binder
2004-04-20 8:43 ` Image support for Carbon Emacs (Re: Consolidation of image support) YAMAMOTO Mitsuharu
2004-04-20 9:03 ` Miles Bader
2004-04-20 9:31 ` YAMAMOTO Mitsuharu
2004-04-20 9:16 ` David Kastrup
2004-04-20 14:28 ` Stefan Monnier
2004-04-21 1:10 ` YAMAMOTO Mitsuharu
2004-04-21 15:58 ` Stefan Monnier
2004-04-22 1:08 ` YAMAMOTO Mitsuharu
-- strict thread matches above, loose matches on Subject: below --
2003-12-17 9:28 Emacs on MAC OS X 10.3 Dusan Turk
2003-12-17 10:56 ` Benjamin Riefenstahl
2003-12-17 18:05 ` Ted Lemon
2003-12-18 0:53 ` Consolidation of image support (was Re: Emacs on MAC OS X 10.3) Kim F. Storm
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=m3r7z2jcwf.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--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).