From: Phillip Lord <p.lord@russet.org.uk>
Subject: Re: Using custom as a type checker:- ramble
Date: 26 Mar 2003 16:59:41 +0000 [thread overview]
Message-ID: <vfwuim6p36.fsf@rpc71.cs.man.ac.uk> (raw)
In-Reply-To: 5ld6ke9k6c.fsf@rum.cs.yale.edu
>>>>> "Stefan" == Stefan Monnier <monnier+gnu.emacs.help/news/@flint.cs.yale.edu> writes:
>>>>> "Phillip" == Phillip Lord <p.lord@russet.org.uk> writes:
>> Now what I would want to do is combine the two. So have something
>> like (custom-setq compilation-window-height) Where custom-setq
>> would use the custom mechanism to set a variable. If it was of
>> the wrong type (so would display "mismatch" in the dialog), then
>> at this point an error would be signalled. This way I would have
>> most of the advantages of both systems. I could do conditional
>> logic, I could comment, I could grep, and so on. But I would also
>> get good "type safety."
Stefan> What I would much rather have is a way to load a normal
Stefan> .emacs and automatically have all the `setq's checked as
Stefan> above. The checking could also include obsolescence and
Stefan> things like that.
Stefan> I.e. I don't want to change the .emacs code at all, but I'd
Stefan> like to have a more-or-less generic way to add helpful
Stefan> analysis of the code so as to give useful information to the
Stefan> user about suspicious customizations.
Well I would agree that this would be preferable.
What worries me, though, is the complexity of this task. I don't know
about you, but my .emacs (and other files that I call from .emacs) is
huge, and often complex, so interpreting this would be complex. Adding
a "custom-setq" function would potentially be very simple.
Although I guess you would also need "custom-add-to-list". And then
"custom-add-hook". And so on. By which time I gets a lot less simple,
and would also require a lot of recoding of existing .emacs'.
Hmmm.
Phil
next prev parent reply other threads:[~2003-03-26 16:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 18:22 Using custom as a type checker:- ramble Phillip Lord
2003-03-26 16:17 ` Stefan Monnier
2003-03-26 16:59 ` Phillip Lord [this message]
2003-03-26 19:14 ` Stefan Monnier
2003-03-27 10:25 ` Phillip Lord
2003-03-27 16:32 ` Stefan Monnier
2003-03-27 17:11 ` Phillip Lord
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=vfwuim6p36.fsf@rpc71.cs.man.ac.uk \
--to=p.lord@russet.org.uk \
/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).