From: Drew Adams <drew.adams@oracle.com>
To: Anders Lindgren <andlind@gmail.com>,
"Charles A. Roelli" <charles@aurox.ch>
Cc: 25818@debbugs.gnu.org
Subject: bug#25818: 25.2; frame moved off display does not return (OS X)
Date: Tue, 28 Feb 2017 14:05:26 -0800 (PST) [thread overview]
Message-ID: <a056da96-b184-48ef-bd6e-d720ba818fe4@default> (raw)
In-Reply-To: <CABr8ebbyGjZT5Om=DAspbvSnfPdzLbOFELsPoQLtD+PUR+-YFA@mail.gmail.com>
Excuse me for chiming in without really following this
thread. I don't use OS X, for one thing, and I'm not
following this particular bug.
But if one of the questions is whether an Emacs user
(or code) should _be able_ to position a frame off
screen then I emphatically say yes, s?he should.
I have code that lets you incrementally move a frame
up/down/left/right, including wraparound or including
the possibility of not wrapping but continuing till
the frame is entirely off screen.
I don't see anything wrong with _allowing_ someone
to position a frame off screen. Why they might want
to do that is up to them.
If that question is not in fact being raised in this
bug discussion, then please ignore this intrusion,
and sorry for the noise.
next prev parent reply other threads:[~2017-02-28 22:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 20:04 bug#25818: 25.2; frame moved off display does not return (OS X) Charles A. Roelli
2017-02-23 8:49 ` martin rudalics
2017-02-26 11:26 ` Charles A. Roelli
2017-02-26 15:40 ` Charles A. Roelli
2017-02-26 16:45 ` martin rudalics
2017-02-26 19:42 ` Charles A. Roelli
2017-02-27 8:05 ` martin rudalics
2017-02-27 10:34 ` Charles A. Roelli
2017-02-27 20:47 ` Charles A. Roelli
2017-02-28 10:12 ` Charles A. Roelli
2017-02-28 13:20 ` Anders Lindgren
2017-02-28 15:05 ` Charles A. Roelli
2017-02-28 20:35 ` Anders Lindgren
2017-02-28 22:05 ` Drew Adams [this message]
2017-03-01 10:48 ` Anders Lindgren
2017-03-01 16:10 ` Drew Adams
2017-03-19 19:38 ` Charles A. Roelli
2017-03-27 18:22 ` Anders Lindgren
2017-04-02 14:14 ` Charles A. Roelli
2017-04-03 8:33 ` Anders Lindgren
2017-04-08 20:40 ` Charles A. Roelli
2017-04-09 19:13 ` Anders Lindgren
2017-04-10 19:54 ` Charles A. Roelli
2017-04-11 18:35 ` Anders Lindgren
2017-04-27 19:14 ` Charles A. Roelli
2017-04-27 20:05 ` Alan Third
2017-04-28 17:33 ` Charles A. Roelli
2017-05-02 20:33 ` Alan Third
2017-05-05 18:30 ` Charles A. Roelli
2017-04-29 10:30 ` martin rudalics
2017-04-29 11:15 ` Charles A. Roelli
2017-04-29 14:51 ` Alan Third
2017-04-29 17:23 ` Anders Lindgren
2017-04-30 8:32 ` 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
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=a056da96-b184-48ef-bd6e-d720ba818fe4@default \
--to=drew.adams@oracle.com \
--cc=25818@debbugs.gnu.org \
--cc=andlind@gmail.com \
--cc=charles@aurox.ch \
/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).