From: "Drew Adams" <drew.adams@oracle.com>
To: 7555@debbugs.gnu.org
Subject: bug#7555: 24.0.50; (elisp) bad organization - Frames submenus
Date: Sat, 4 Dec 2010 10:24:47 -0800 [thread overview]
Message-ID: <F7EE8A976557457FB5DA3CD40103AFD4@us.oracle.com> (raw)
All kinds of stuff has been stuffed under the `Frames' node - stuff that
has nothing particular to do with frames. This stuff should be placed
elsewhere.
Examples:
Mouse Tracking - maybe put it with other mouse stuff
Mouse Position - " "
Pop-Up Menus - put it with other menu stuff
It has nothing to do with frames, apart from the fact
that the implementation might involve frames.
Dialog Boxes - maybe put it with menu or `interactive' stuff
Again, it has nothing to do with frames apart from
implementation.
Pointer Shape - put it with other mouse stuff
Window System Selections - put it with selection/region stuff
Drag and Drop - put it with copy/paste stuff
Color Names - again, has nothing to do with frames
Text Terminal Colors - ditto
Resources - resources can be anything, not just frame parameters
Display Feature Testing - similar to resources - this is about
display/system properties, not about Emacs frames
This is a terrible mess. It confuses users wrt what Emacs frames are
all about. You might just as well stuff all this stuff in the section
about Emacs faces or the region - that makes about as much sense (none).
In GNU Emacs 24.0.50.1 (i386-mingw-nt5.1.2600)
of 2010-11-30 on 3249CTO
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.4) --no-opt --cflags
-Ic:/imagesupport/include'
next reply other threads:[~2010-12-04 18:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 18:24 Drew Adams [this message]
2016-04-28 9:47 ` bug#7555: 24.0.50; (elisp) bad organization - Frames submenus Lars Ingebrigtsen
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=F7EE8A976557457FB5DA3CD40103AFD4@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=7555@debbugs.gnu.org \
/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.