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:45:29 +0100 [thread overview]
Message-ID: <trinity-5ba0d9ac-51fc-4106-9573-917727e9f060-1606056329006@3c-app-mailcom-bs11> (raw)
In-Reply-To: <87mtz9h34i.fsf@web.de>
> Sent: Sunday, November 22, 2020 at 3:34 PM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: Make fullscreen with margins
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> > I actually used
> >
> > (if (one-window-p)
>
> Should be ok, yes.
>
> > Here is the code. Would you be so kind to comment if this can be
> > improved?
>
> If you are happy with what it does, and `margined-buffer' is a function
> you defined, I think you can use that.
Yes, it is a function I defined.
> If you intend to distribute your code, your function names should get an
> according prefix. If not, it's still better to use a prefix like "my-"
> or so, for the sake that it will later be obvious that that is your own
> function. That will prevent later confusion, for yourself, or if you
> post your code etc.
Yes, the code will be good enough for public release. Can you suggest a
package I can check out on the things you mentioned so there won't be
confusion?
> Regards,
>
> Michael.
>
>
next prev parent reply other threads:[~2020-11-22 14:45 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
2020-11-22 14:34 ` Michael Heerdegen
2020-11-22 14:45 ` Christopher Dimech [this message]
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-5ba0d9ac-51fc-4106-9573-917727e9f060-1606056329006@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).