From: martin rudalics <rudalics@gmx.at>
To: Drew Adams <drew.adams@oracle.com>,
"N. Jackson" <nljlistbox2@gmail.com>,
Eli Zaretskii <eliz@gnu.org>
Cc: 20183@debbugs.gnu.org
Subject: bug#20183: 24.4.91; No resize handle to adjust width of Emacs windows
Date: Thu, 02 Jul 2015 18:14:58 +0200 [thread overview]
Message-ID: <55956382.1020903@gmx.at> (raw)
In-Reply-To: <c9f09908-2c0b-4683-aebd-b77d65490b31@default>
> They can always customize Emacs, to get back those pixels. The problem
> of not being aware of such possibilities is a bigger problem, IMHO.
>
> And I agree with N. Jackson that this particular affordance
> is something that is quite common and thus often expected.
That's why I wrote it. But it was never on our TODO list. Maybe it is
quite common for Windows users only. And so far nobody was interested
in porting it to the ns build.
> [FWIW, I've long been in favor of giving :help-echo or other pop-up
> help for UI elements a menu item that takes users to either the doc
> about customizing that element or directly to an appropriate Customize
> buffer. In this case, it would mean (a) we show the handle by default
> and (b) we provide mouseover help with a link that gives you access to
> the doc you added about this - doc that describes the UI element and
> tells you how to customize it.]
There seems to be a technical problem with this. Pop-up help disappears
here as soon as I move the mouse over it.
martin
next prev parent reply other threads:[~2015-07-02 16:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 19:15 bug#20183: 24.4.91; No resize handle to adjust width of Emacs windows N. Jackson
2015-03-23 19:36 ` Eli Zaretskii
2015-03-23 20:57 ` N. Jackson
2015-07-02 13:22 ` martin rudalics
2015-07-02 15:32 ` Drew Adams
2015-07-02 16:14 ` martin rudalics [this message]
2015-07-02 16:49 ` Drew Adams
2015-03-23 19:48 ` Drew Adams
2015-07-02 13:22 ` martin rudalics
2015-07-06 11:08 ` martin rudalics
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=55956382.1020903@gmx.at \
--to=rudalics@gmx.at \
--cc=20183@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=nljlistbox2@gmail.com \
/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.