From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Malformed MIME quoted-printable message
Date: 19 Nov 1996 16:45:16 +0100 [thread overview]
Message-ID: <rjsp66m6lv.fsf@babbage.dina.kvl.dk> (raw)
In-Reply-To: Wesley.Hardaker@sphys.unil.ch's message of 19 Nov 1996 10:37:19 +0100
Wesley.Hardaker@sphys.unil.ch writes:
> I was actually going to suggest (and then laugh at the changing API
> causing people problems) that customize should store a list of
> add/remove calls instead of a list of functions...
Yes, I want to do something like this, but a bit more general. For
example, you would probably doesn't want customize `auto-mode-alist'
using the current method, i.e. saving a copy of the list.
Something similar is true for customizing keymaps. I'd like to come
up with a way to specify modifications to complex structures, instead
of just saving the entire structure. It is not simple to come up with
a good API though, and the UI problems are even worse. Suggestions
are welcome.
I don't think it will cause any compatibility problems though.
next prev parent reply other threads:[~1996-11-19 15:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-17 3:05 Steven L Baur
1996-11-17 10:59 ` Lars Magne Ingebrigtsen
1996-11-17 19:44 ` Steven L Baur
1996-11-17 20:04 ` Lars Magne Ingebrigtsen
1996-11-17 20:16 ` Per Abrahamsen
1996-11-17 21:33 ` Steven L Baur
1996-11-19 9:37 ` Wesley.Hardaker
1996-11-19 15:45 ` Per Abrahamsen [this message]
1996-11-17 19:48 ` Hrvoje Niksic
1996-11-18 7:20 ` Steinar Bang
1996-11-18 17:02 ` 守岡 知彦 / MORIOKA Tomohiko
1996-11-18 7:16 ` 守岡 知彦 / MORIOKA Tomohiko
1996-11-18 17:48 ` Lars Magne Ingebrigtsen
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=rjsp66m6lv.fsf@babbage.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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 NNTP newsgroup(s).