From: Jean Louis <bugs@gnu.support>
To: Christopher Dimech <dimech@gmx.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: Re: Make fullscreen with margins
Date: Sun, 22 Nov 2020 19:02:35 +0300 [thread overview]
Message-ID: <X7qLm2XwYzxHYHHb@protected.rcdrun.com> (raw)
In-Reply-To: <trinity-44ddef94-5460-4b89-bb62-3419ce5ababb-1606058917158@3c-app-mailcom-bs08>
* Christopher Dimech <dimech@gmx.com> [2020-11-22 18:30]:
> I figured that users can use "C-h f" which would give the required
> information of the file and package for that call.
>
> Do people not like that?
That is why Emacs is self-documenting. I use it every day.
Related to prefix for functions:
• You should choose a short word to distinguish your program from
other Lisp programs. The names of all global symbols in your
program, that is the names of variables, constants, and functions,
should begin with that chosen prefix. Separate the prefix from the
rest of the name with a hyphen, ‘-’. This practice helps avoid
name conflicts, since all global variables in Emacs Lisp share the
same name space, and all functions share another name space(1).
Use two hyphens to separate prefix and name if the symbol is not
meant to be used by other packages.
You could simply prefix each function with cd-
I have first defined my own functions like string-empty-p but then
when I make program into package it starts using built-in function of
same name that does not give me same result and all program
breaks. There are 26856 functions in my Emacs and many are similar so
the prefix helps in having distinct function names.
My prefixes are
cf-
rcd-
hyperscope-
wrs-
For example: wrs-publish-pages
--
Thanks,
Jean Louis
⎔ λ 🄯 𝍄 𝌡 𝌚
next prev parent reply other threads:[~2020-11-22 16:02 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
2020-11-24 15:23 ` Michael Heerdegen
2020-11-22 15:28 ` Christopher Dimech
2020-11-22 16:02 ` Jean Louis [this message]
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=X7qLm2XwYzxHYHHb@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=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).