unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Kevin Vigouroux <ke.vigouroux@laposte.net>, 41532@debbugs.gnu.org
Subject: bug#41532: Why use the mouse in Emacs?
Date: Mon, 25 May 2020 11:22:10 -0700 (PDT)	[thread overview]
Message-ID: <304f1cd0-045c-4f34-924c-2ae2ca072cc0@default> (raw)
In-Reply-To: <87zh9vgbkc.fsf@laposte.net>

Lots of us use both keyboard and mouse.

The difference from some other applications,
I think, is that some applications pretty
much _require_ you to use a mouse.  There's
often no keyboard shortcut for this or that
operation, and no way to create your own
shortcut in the application.

This seems to be the problem you're reporting:

> the Emacs graphical interface is half broken.
> ... it is difficult to navigate with the mouse
> or to organize its work because the interface
> is not designed this way.

How so?  Specifically, what's the problem?  In
what way can you not navigate with the mouse?

> The menu, for example, does not open graphical
> windows but usual Emacs windows (minibuffer,
> echo area, Customize...).

OK, good; something concrete.  Except ... what
do you mean by "graphical windows"?  The examples
you mention are graphical windows, AFAICT.

Do you perhaps mean window-manager windows, i.e.,
what Emacs calls "frames"?  If so, customize
`pop-up-frames' to `t', and see if Emacs then
does what you want.

> Finally, I think it is necessary to clarify
> that we use Emacs mainly with the keyboard
> because the interface is designed that way
> otherwise the user will have false expectations.

Is not designed what way?  False expectations
of what?





  reply	other threads:[~2020-05-25 18:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-25 17:37 bug#41532: Why use the mouse in Emacs? Kevin Vigouroux via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-25 18:22 ` Drew Adams [this message]
2020-05-26 14:58   ` Kevin Vigouroux via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-05-26 15:30     ` Drew Adams
2020-10-18  1:29     ` Stefan Kangas
2020-12-12 13:25       ` Lars Ingebrigtsen
2020-05-27  3:57   ` Dmitry Alexandrov
2020-05-27  4:57     ` Drew Adams
2020-05-26 15:52 ` Colin Baxter
2020-05-27  3:33 ` Dmitry Alexandrov

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=304f1cd0-045c-4f34-924c-2ae2ca072cc0@default \
    --to=drew.adams@oracle.com \
    --cc=41532@debbugs.gnu.org \
    --cc=ke.vigouroux@laposte.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).