Gnus development mailing list
 help / color / mirror / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: ding@gnus.org
Subject: Maximised second frame when first one is maximised on OS X
Date: Tue, 25 Jun 2013 13:59:06 +0200	[thread overview]
Message-ID: <m21u7q8kqd.fsf@krugs.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]

Hi

I asked already in the emacs.mac mailing list, but it was sugested to
ask here - so this is what I do. 

I installed gnu-emacs
,----
| GNU Emacs 24.3.1 (x86_64-apple-darwin12.4.0, NS apple-appkit-1187.39)
`----
via homebrew as well as well ws emacs (carbon)

,----
| GNU Emacs 24.3.1 (x86_64-apple-darwin, NS apple-appkit-1038.36)
|  of 2013-03-13 on bob.porkrind.org
`----


and I have a questions concerning maximising and second
frame on both, started with -q.

I have a Macbook Pro Retina plus a second monitor.

I can maximise emacs without problems, and then one monitor is, as
expected, blank. Now I would like to open a second frame on the second
monitor. I managed once, but now, the second frame is automatically
maximised, resulting it being moved away. How can I create a new frame,
without it becoming automatically maximised?

I tried setting default-frame-alist and it works, but as soon as all the
specified settings are applied, the frame is maximised.

The reason why I would like to have this option is that I could then
move the second frame to the (now blank) monitor.

Thanks,

Rainer

-- 
Rainer M. Krug

email: RMKrug<at>gmail<dot>com

[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]

                 reply	other threads:[~2013-06-25 11:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=m21u7q8kqd.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=ding@gnus.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.
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 NNTP newsgroup(s).