Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes:
> I don't think that would be a good idea. All over XEmacs,
button1 is
> used to position the point, while button2 is used for selecting.
> Making list-mode an exception without changing anything else would
> only add to the confusion.
That's not quite true; button1 on a glyph widget selects it (eg in
customize buffers).
...which only proves my point that changing these things is a
long-term mistake because it confuses the hell out of everyone. It
does make sense for button1 to select glyphs (Customize merely copied
the way annotations.el has behaved for ages), because positioning the
point to a glyph doesn't.
I'd like to see button1 select all "button-like"
things. I suggest
that non-glyph widgets are certainly buttons. I also suggest that
filenames in Completion List Mode are more button-like than
text-like, especially when presented in the mouse-read-file frame if
not in general. Do you think that changing button1 to select
filenames in the mouse-read-file frame only and to select non-glyph
widgets would be a good thing or at least harmless?
I don't know. In my humble opinion, Emacs users should get used to
clicking with button2 everywhere, *or* we should do something about
it. Kludging up individual modes in order to support the optional use
of button1 for that purpose is clearly not the right thing.
My opinions on all that are not very strong. If you really really
think it would help people to select files with button1, I won't
veto the change.