unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: dieter@duenenhof-wilhelm.de,
	Alexis Roda <alexis.roda.villalonga@gmail.com>
Cc: aprekates <aprekates@posteo.net>, help-gnu-emacs@gnu.org
Subject: RE: How can i enable webmode?
Date: Sun, 10 May 2020 09:42:14 -0700 (PDT)	[thread overview]
Message-ID: <d7ac5ab8-dc94-4676-b262-a546ef8c41d4@default> (raw)
In-Reply-To: <86d07b6a4w.fsf@duenenhof-wilhelm.de>

> For example the Melpa package `inform' is activating itsel during
> installation (and maybe by restarting Emacs in some situations).  The
> motivation is: If you are interested you'll have it without much ado
> and
> if you don't like it any more just uninstall the small package.
> 
> Does it make sense or do you regard this behaviour as impolite?

It's generally considered impolite, and is
contrary to convention.

Loading a library should in general not change
most user-observable behavior.  It shouldn't
change faces, key bindings, actions of existing
commands, etc.

"Installing a package" does a little bit more
than loading a typical library (Lisp file).
The main thing package-installing does, which
might or might not be done by just loading a
library (e.g. `require'), is to establish
autoloading for some commands etc.
___

This is, in fact, the very first rule of the
Emacs Lisp Coding Conventions:

  D.1 Emacs Lisp Coding Conventions
  =================================

  Here are conventions that you should follow when
  writing Emacs Lisp code intended for widespread use:

   • Simply loading a package should not change Emacs’s
     editing behavior.  Include a command or commands
     to enable and disable the feature, or to invoke it.

     This convention is mandatory for any file that
     includes custom definitions.  If fixing such a file
     to follow this convention requires an incompatible
     change, go ahead and make the incompatible change;
     don’t postpone it.

https://www.gnu.org/software/emacs/manual/html_node/elisp/Coding-Conventions.html

These conventions apply pretty strictly to code
to be included in Emacs.  And they are offered
as guidance for 3rd-party (i.e., user) code.



  reply	other threads:[~2020-05-10 16:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-10 10:02 How can i enable webmode? aprekates
2020-05-10 11:05 ` Jakub Jankiewicz
2020-05-10 14:40   ` aprekates
2020-05-10 15:35     ` 조성빈
     [not found] ` <CAMDYoXZKD6krOQXpX_4js16bn+MtS_imPBHHmLJ2qNEh0Z_toQ@mail.gmail.com>
     [not found]   ` <008d9cd4-8d24-f19b-82ad-d5c1bf7a435f@posteo.net>
2020-05-10 15:43     ` Alexis Roda
2020-05-10 16:13       ` H. Dieter Wilhelm
2020-05-10 16:42         ` Drew Adams [this message]
2020-05-11 11:55           ` H. Dieter Wilhelm
2020-05-11 12:03             ` tomas
2020-05-11 12:47               ` H. Dieter Wilhelm
2020-05-11 15:02             ` Drew Adams
2020-05-11 16:05             ` Stefan Monnier
2020-05-11 17:22               ` H. Dieter Wilhelm
2020-05-10 16:55         ` Dan Sommers
2020-05-11 12:03           ` H. Dieter Wilhelm
2020-05-11 14:01             ` Dan Sommers
2020-05-11 16:09             ` Stefan Monnier

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=d7ac5ab8-dc94-4676-b262-a546ef8c41d4@default \
    --to=drew.adams@oracle.com \
    --cc=alexis.roda.villalonga@gmail.com \
    --cc=aprekates@posteo.net \
    --cc=dieter@duenenhof-wilhelm.de \
    --cc=help-gnu-emacs@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.
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).