From: Jean Louis <bugs@gnu.support>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: emacs-devel@gnu.org
Subject: Re: adding to emacs coding standard / formatting
Date: Tue, 20 Oct 2020 12:30:44 +0300 [thread overview]
Message-ID: <X46uRAydhuZyNg3g@protected.rcdrun.com> (raw)
In-Reply-To: <20201020055548.nzw3zoucbsdx2unv@E15-2016.optimum.net>
* Boruch Baum <boruch_baum@gmx.com> [2020-10-20 09:18]:
> On 2020-10-20 01:11, Richard Stallman wrote:
> > [[[ To any NSA and FBI agents reading my email: please consider ]]]
> > [[[ whether defending the US Constitution against all enemies, ]]]
> > [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> >
> > > Also, this is an opportunity to address a pet peeve: I occasionally see
> > > code either defining keybindings to lambda functions, or setting lambda
> > > functions as elements of function lists (eg. lists of hook functions).
> > > I'd like to propose that those uses be banned because of their
> > > difficulty to modify.
> >
> > I think we recommend not doing that. Maybe we should say this also in
> > tips.texi. Want to propose a patch?
>
> For all the many years I've been using emacs and coding in elisp, I have
> no idea what tips.texi is or how to access it! I guess that speaks to
> another subject discussed on this list: the fragmentation and abundance
> of emacs help resources?
I guess texinfo file forms this section of Emacs Lisp manual, it is
then in that manual.
Tips and Conventions
* Coding Conventions:: Conventions for clean and robust programs.
* Key Binding Conventions:: Which keys should be bound by which programs.
* Programming Tips:: Making Emacs code fit smoothly in Emacs.
* Compilation Tips:: Making compiled code run fast.
* Warning Tips:: Turning off compiler warnings.
* Documentation Tips:: Writing readable documentation strings.
* Comment Tips:: Conventions for writing comments.
* Library Headers:: Standard headers for library packages.
prev parent reply other threads:[~2020-10-20 9:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 3:10 adding to emacs coding standard / formatting Boruch Baum
2020-10-19 9:28 ` Stefan Kangas
2020-10-19 15:37 ` Drew Adams
2020-10-19 14:24 ` Stefan Monnier
2020-10-19 14:32 ` Eli Zaretskii
2020-10-19 19:59 ` Boruch Baum
2020-10-19 20:07 ` Drew Adams
2020-10-21 4:37 ` Richard Stallman
2020-10-21 14:46 ` Drew Adams
2020-10-20 5:11 ` Richard Stallman
2020-10-20 5:11 ` Richard Stallman
2020-10-20 5:55 ` Boruch Baum
2020-10-20 8:32 ` Eli Zaretskii
2020-10-20 9:30 ` Jean Louis [this message]
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=X46uRAydhuZyNg3g@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=boruch_baum@gmx.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.