Open GoogleCodeExporter opened 9 years ago
Currently, M-x Customize is pretty much useless because it won't save
customizations
anymore. The next start-up, they are all gone.
I dont see the interface getting less complex and unintuitive just with these
changes, on the contrary, I believe the more visual and explicit the better,
taking
away buttons but keeping their functionality alive by "prompt at close" is the
wrong
way to go. Just closing should mean discarding any settings, only prompting the
user
if he is aware of unsaved changes in the buffer. Deliberate visual (not to say
haptic) differentiation between 'try out once' and 'save forever' is a good
thing and
allows newbeginners to experiment.
Original comment by milan.santosi@gmail.com
on 24 Sep 2009 at 3:48
[deleted comment]
Milan (milan.santosi@gmail.com) has further comment on this:
http://groups.google.com/group/ergoemacs/browse_frm/thread/c415f26b9b3ffb50
Original comment by xah...@gmail.com
on 24 Sep 2009 at 10:26
btw, for some reason, when i do M-x customize with GNU emacs on Windows, i
don't see
Save For Future Session anymore. I recall it was there. I am puzzled. David,
did we do
something that changed this? I wanted to ask about this before but just didn't
do yet.
Original comment by xah...@gmail.com
on 24 Sep 2009 at 10:35
about this issue... i think Milan's comment has merit... however, i think that
the
current way of customize has a lot usability problem. For example, try to
customize-
group the whitespace-mode. See: http://xahlee.org/emacs/whitespace-mode.html
Original comment by xah...@gmail.com
on 24 Sep 2009 at 10:37
Original issue reported on code.google.com by
xah...@gmail.com
on 15 Sep 2009 at 7:56