all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kevin Vigouroux via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 41532@debbugs.gnu.org
Subject: bug#41532: Why use the mouse in Emacs?
Date: Tue, 26 May 2020 16:58:19 +0200	[thread overview]
Message-ID: <87sgfmoi9g.fsf@laposte.net> (raw)
In-Reply-To: <304f1cd0-045c-4f34-924c-2ae2ca072cc0@default> (Drew Adams's message of "Mon, 25 May 2020 11:22:10 -0700 (PDT)")

The user experience is quite different when browsing the Emacs and
LibreOffice menus although they seem similar. The Emacs interface is
mainly text-based partly because there are few graphical widgets.

Nonetheless, this difference is not always clearly perceived. It can be
seen in the following two cases:

1. Menu bar> Tools, Merge, Files... opens a window manager window.
2. Menu bar> Tools, Search Files(Grep)... opens the minibuffer.

Moreover, I think people may also confuse a text-based interface having
a good appearance with a graphical user interface.

The issue may be:

- Better describe or explain how to use the mouse in the interface,

- Fix the menu so as not to mislead the user,

- Rebuild at least partially the Emacs graphical user interface.





  reply	other threads:[~2020-05-26 14:58 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
2020-05-26 14:58   ` Kevin Vigouroux via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgfmoi9g.fsf@laposte.net \
    --to=bug-gnu-emacs@gnu.org \
    --cc=41532@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    --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 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.