all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: "Clément Pit--Claudel" <clement.pit@gmail.com>, 24579@debbugs.gnu.org
Subject: bug#24579: [PATCH] borderless windows on OS X
Date: Sun, 02 Oct 2016 20:09:48 +0200	[thread overview]
Message-ID: <57F14D6C.4070104@gmx.at> (raw)
In-Reply-To: <24c73665-5159-02db-4307-be9cde163726@gmail.com>

 > Doesn't that depend on the window manager? For example, I can press
 > Meta while dragging a frame to move it on my distro.

Whatever we do has to work with most window managers.  If most window
managers allow Meta dragging, we can drop this issue.

 > By arbitrary
 > frame, I meant the kind of frame that you can create with make-frame
 > (as opposed to a tooltip frame).  IIUC, the main difference is whether
 > you can create multiple of them at the same time.

Agreed.  However, such frames will never be as functional as a standard
graphical frame which is controlled by the window manager.  We have to
make a checklist for what we expect such frames to accomplish and what
Emacs has to do to manage them.

But remember that the topic of the present thread is to implement frames
without titlebars and external borders on OS X.  We can, in principle,
do that on GNU/Linux and Windows.  We cannot do that, so far, on OS X.

 >> Add a (border-width . 0) entry to `tooltip-frame-parameters' and show a
 >> native Emacs tooltip.
 >
 > Can we show multiple of these at once? I thought we were limited to having a single one shown at any time, unlike regular frames.

Yes, there can be only one tooltip frame.  I posted a feature to show
multiple such frames in the "Latest master broken on Cocoa/NS" thread
but IIRC never got a response from you.

martin





  reply	other threads:[~2016-10-02 18:09 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01  1:31 bug#24579: [PATCH] borderless windows on OS X Jay McCarthy
2016-10-01  8:44 ` martin rudalics
2016-10-01 11:53   ` Jay McCarthy
2016-10-01 13:41     ` martin rudalics
2016-10-01 20:18       ` Jay McCarthy
2016-10-02  8:29         ` martin rudalics
2016-10-13 17:56           ` Jay McCarthy
2016-10-13 18:36             ` martin rudalics
2016-10-13 22:27               ` Jay McCarthy
2016-10-01 21:26 ` Alan Third
2016-10-01 22:18   ` Jay McCarthy
2016-10-01 23:04     ` Alan Third
2016-10-02  0:49       ` Clément Pit--Claudel
2016-10-02  8:30         ` martin rudalics
2016-10-02 15:07           ` Alan Third
2016-10-02 16:39             ` martin rudalics
2016-10-02 16:49               ` Alan Third
2016-10-02 18:10                 ` martin rudalics
2016-10-02 18:31                   ` Clément Pit--Claudel
2016-10-02 15:18           ` Clément Pit--Claudel
2016-10-02 16:39             ` martin rudalics
2016-10-02 16:50               ` Clément Pit--Claudel
2016-10-02 18:09                 ` martin rudalics [this message]
2017-04-21 19:49 ` Alan Third

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=57F14D6C.4070104@gmx.at \
    --to=rudalics@gmx.at \
    --cc=24579@debbugs.gnu.org \
    --cc=clement.pit@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.