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: Tue, 24 Nov 2020 15:37:49 +0100 [thread overview]
Message-ID: <trinity-97c71ffb-e9b2-4917-aec9-be256c3725c0-1606228669092@3c-app-mailcom-bs16> (raw)
In-Reply-To: <874klhdsj7.fsf@web.de>
> Sent: Sunday, November 22, 2020 at 9:51 PM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Make fullscreen with margins
>
> Jean Louis <bugs@gnu.support> writes:
>
> > > A package normally uses one prefix. For coding conventions and tips you
> > > definitely want to have a look in the manual: (info "(elisp) Tips").
> >
> > And is it fine if I have several packages using same prefix?
>
> If they belong together, I think so, it is lived practice. Occupying
> someone else's prefix is not good of course, maybe unless your package
> is an extension.
Would the prefix be done for all of defun, defvar, defgroup, defcustom?
> For several packages sharing one prefix, one can use "sub prefixes" (I
> call them so here, there is no official name for that I think), like
> "foo-" for the whole ecosystem of related packages, and then
> e.g. "foo-evil-" "foo-firefox" or "foo-x" for the packages implementing
> certain special features.
>
> Michael.
>
>
>
next prev parent reply other threads:[~2020-11-24 14:37 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
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 [this message]
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-97c71ffb-e9b2-4917-aec9-be256c3725c0-1606228669092@3c-app-mailcom-bs16 \
--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).