> So, what operations is it that people need frequently that require the emacs
> menubar? I can see that maybe a menubar user may want the edit and possibly
> the buffer menus, but the rest?
Oh, anything really. The whole point of using a mail client inside
Emacs is to have the power of Emacs for doing all the other things.
Some of the frequent things I needed do were to browse files or
directories, run shells etc. (I don't use the menubar much now, but I
used it a lot when I had RSI and did things by speech.)
> If VM users need to switch to the emacs menu
> frequently, I'd argue that what should happen is VM should not disable those
> menu items and have them in the menubar - this would be much more convenient
> that having to frequently toggle the whole menu-bar.
I agree, but that is too large a project to contemplate right now.
The whole menubar has to be rethought. But, our first task is to
restore VM to its original form. As I said, GTK users can have the
work-around, but there is no reason for all the other users to put up
with this overhead.
Tim Cross writes:
> So, what operations is it that people need frequently that require the emacs
> menubar? I can see that maybe a menubar user may want the edit and possibly
> the buffer menus, but the rest?
Oh, anything really. The whole point of using a mail client inside
Emacs is to have the power of Emacs for doing all the other things.
Some of the frequent things I needed do were to browse files or
directories, run shells etc. (I don't use the menubar much now, but I
used it a lot when I had RSI and did things by speech.)
> If VM users need to switch to the emacs menu
> frequently, I'd argue that what should happen is VM should not disable those
> menu items and have them in the menubar - this would be much more convenient
> that having to frequently toggle the whole menu-bar.
I agree, but that is too large a project to contemplate right now.
The whole menubar has to be rethought. But, our first task is to
restore VM to its original form. As I said, GTK users can have the
work-around, but there is no reason for all the other users to put up
with this overhead.
Cheers,
Uday