* "Package options is obsolete" but beats "customization"
@ 2006-06-07 17:38 Dan Jacobson
0 siblings, 0 replies; only message in thread
From: Dan Jacobson @ 2006-06-07 17:38 UTC (permalink / raw)
Only now on day 2 and in a different emacs 22 session, after writing
all those bug reports on day 1, do I now see "Package options is
obsolete" in the minibuffer, upon just happening to start
edit-options.
So fine, only now after replying to all my day 1 bug reports, to
inform me that Package options is obsolete, do you now see that I
finally got the message already. So were even.
Messages in the minibuffer have a 50/50 chance of not being seen by
the user. How do you know that they weren't even also covered up by a
different message?
So you should put the message in more places, like at the top of the
*List Options* buffer, etc.
;; The customization buffer feature is intended to make this obsolete.
Not so fast. I run screaming when ever sent to the customization
buffer. "There is a sense that I am not in control."
Indeed I wish there was a script that would translate all the
;; custom-set-faces was added by Custom.
;; If you edit it by hand, you could mess it up, so be careful.
junk that was written to my .emacs just like I was a little kid in
Microsoft land, back to good old setq's that I can deal with by hand.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2006-06-07 17:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-07 17:38 "Package options is obsolete" but beats "customization" Dan Jacobson
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.