unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Make fullscreen with margins
Date: Sun, 22 Nov 2020 15:25:47 +0100	[thread overview]
Message-ID: <trinity-71252705-99dd-41a5-bc3c-6c50e914f71d-1606055147852@3c-app-mailcom-bs11> (raw)
In-Reply-To: <87sg91h3si.fsf@web.de>

I actually used

(if (one-window-p)

Here is the code.  Would you be so kind to comment if this can be improved?


(defun fullscreen-toggle ()
   "Toggles to fullscreen"
   (interactive)
   (if (eq (frame-parameter nil 'fullscreen) 'fullboth)
      (if (one-window-p)
         (progn (margined-buffer 0)
                (disable-fullscreen))
         (disable-fullscreen))
      (if (one-window-p)
         (progn (margined-buffer)
                (enable-fullscreen))
         (enable-fullscreen)) ))



> Sent: Sunday, November 22, 2020 at 3:19 PM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Make fullscreen with margins
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > I have the following code for getting to full screen Have made buffer-margins
> > that sets a margin on either side of buffer.  Bet I would like that the
> > margins are only set when there is only one buffer in the frame.
>
> AFAIU you want a test like (cdr (window-list)).
>
>
>
>



  reply	other threads:[~2020-11-22 14:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-21 20:13 Make fullscreen with margins Christopher Dimech
2020-11-22 14:19 ` Michael Heerdegen
2020-11-22 14:25   ` Christopher Dimech [this message]
2020-11-22 14:34     ` Michael Heerdegen
2020-11-22 14:45       ` Christopher Dimech
2020-11-22 14:58         ` Michael Heerdegen
2020-11-22 15:20           ` Christopher Dimech
2020-11-22 15:27             ` Michael Heerdegen
2020-11-22 15:57               ` Jean Louis
2020-11-22 20:51                 ` Michael Heerdegen
2020-11-24 14:37                   ` Christopher Dimech
2020-11-24 15:23                     ` Michael Heerdegen
2020-11-22 15:28           ` Christopher Dimech
2020-11-22 16:02             ` Jean Louis
2020-11-22 20:54             ` Michael Heerdegen

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=trinity-71252705-99dd-41a5-bc3c-6c50e914f71d-1606055147852@3c-app-mailcom-bs11 \
    --to=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).