unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Jenkins <brian@brianjenkins.org>
To: rms@gnu.org
Cc: Bozhidar Batsov <bozhidar@batsov.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: [PATCH] frame.c: focus hooks
Date: Tue, 19 Nov 2013 13:14:59 -0500	[thread overview]
Message-ID: <CADTx1Ow_qZYe=nOYd6FoZeqys0ctTd0k=0jHXx814ddf_10bWg@mail.gmail.com> (raw)
In-Reply-To: <E1VieNs-0001wg-Cr@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

>
>
> Are you assuming that these hooks won't be used by any Lisp packages?
>
>
Yes, I am expecting that they will be left for the user to specify in
his or her local Emacs configuration.

That is, I expect that they won't be assigned by *polite* Lisp packages.
It would be rude to set these hooks in a package published for
widespread use.

Package authors aren't perfect, but they care enough about Emacs culture
to learn Lisp and contribute work.  We should assume good faith.  When
people write impolite packages, we should teach them Emacs etiquette and
help them observe social norms.

Further, ill-mannered Lisp packages are not forced on the user.  They
are deliberately downloaded in source form and installed.  If a package
inappropriately assigns hooks, we are free to uninstall it, to clear the
hooks after load, to modify the package for local use, to contact the
authors and suggest that they not over-specify our environment, or even
to distribute a better-behaved fork of the package.

Inappropriate hook assignment is also easier to detect than many
possible package misbehaviors -- just evaluate the hook variables.

It's probably not a bad idea to document the intent of these hooks -- that
they are meant for the end user and that it is inappropriate to set them
in public packages, but I don't see that adding them opens a huge can of
worms.

Best,
Brian Jenkins

[-- Attachment #2: Type: text/html, Size: 2107 bytes --]

  reply	other threads:[~2013-11-19 18:14 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-17 17:50 [PATCH] frame.c: focus hooks Brian Jenkins
2013-11-17 18:29 ` Bozhidar Batsov
2013-11-17 22:25   ` Brian Jenkins
2013-11-17 22:33     ` Drew Adams
2013-11-18 13:24       ` Brian Jenkins
2013-11-18 14:53         ` Drew Adams
2013-11-19  0:19         ` Stefan Monnier
2013-11-19  8:26         ` Stephen J. Turnbull
2013-11-19 14:10           ` Bozhidar Batsov
2013-11-20  3:10             ` Brian Jenkins
2013-11-18  8:20     ` Bozhidar Batsov
2013-11-18 13:32   ` Stefan Monnier
     [not found]     ` <CAM9Zgm18uL7+PJ+60NjZqtjZJ6tUV77xUbFhXh7UPwqs==1=hg@mail.gmail.com>
2013-11-18 14:20       ` Fwd: " Bozhidar Batsov
2013-11-18 14:23     ` Brian Jenkins
2013-11-18 18:44   ` Richard Stallman
2013-11-18 19:49     ` Brian Jenkins
2013-11-19  6:02       ` Richard Stallman
2013-11-19 18:14         ` Brian Jenkins [this message]
2013-11-19 18:53           ` Drew Adams
2013-11-20  0:52             ` Brian Jenkins
2013-11-19 23:42           ` Richard Stallman
2013-11-20  0:52             ` Josh
2013-11-20  3:16               ` Stefan Monnier
2013-11-20  3:36                 ` Josh
2013-11-20  7:34                   ` martin rudalics
2014-01-09 17:01                     ` Josh
2014-01-11 10:25                       ` martin rudalics
2014-01-11 19:05                         ` Josh
2014-01-12  9:54                           ` martin rudalics
2014-01-14 17:30                             ` Josh
2014-01-14 18:10                               ` martin rudalics
2014-01-10 17:31                   ` Stefan Monnier
2014-01-11 19:06                     ` Josh
2013-11-20  0:53             ` Brian Jenkins
2013-11-20  7:46               ` Jarek Czekalski
2013-11-17 19:28 ` Glenn Morris
2013-11-17 21:19 ` Stefan Monnier
2013-11-18  4:11 ` Leo Liu
     [not found]   ` <CADTx1Oy5pUmb9sPU6jm0yt1hJtvgJmfDtZQpeFakmHknhEXE=A@mail.gmail.com>
2013-11-18 13:33     ` Fwd: " Brian Jenkins

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='CADTx1Ow_qZYe=nOYd6FoZeqys0ctTd0k=0jHXx814ddf_10bWg@mail.gmail.com' \
    --to=brian@brianjenkins.org \
    --cc=bozhidar@batsov.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).