unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: doctor.el
Date: Sun, 03 Jul 2005 16:43:01 -0400	[thread overview]
Message-ID: <E1DpBIr-00026o-CA@fencepost.gnu.org> (raw)
In-Reply-To: <92a5eb47050702155627ac4ec7@mail.gmail.com> (message from Joshua Varner on Sat, 2 Jul 2005 17:56:59 -0500)

    There are a number a variables that are made buffer local, that are
    unique to doctor.el should those be prefixed as well?

On general principles it would be cleaner to do so.  Another
alternative is to defvar them without initial value, since that
doesn't affect other files.  On general principles, that is less
clean, but it might be adequate, and it might be more convenient in
other ways.

    When you mention the 'doctor specs' are you referring to the below:
    (defun doctor-meaning (x) (get x 'doctor-meaning))

    (defmacro doctor-put-meaning (symb val)
	"Store the base meaning of a word on the property list."
	(list 'put (list 'quote symb) ''doctor-meaning val))

    doctor-put is called on a bunch of global symbols, but the property is
    prefixed by 'doctor-',

Yes.

     if these are the ones you want converted would
    it be better to not use properties at all,

I looked at that, and it looks like the names defined with
doctor-put-meaning have nothing to do with the issue.  I was talking
about the names that seem to be set up as local variables.  That is
what makes the warnings.

  reply	other threads:[~2005-07-03 20:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-02 12:33 doctor.el Richard M. Stallman
2005-07-02 22:56 ` doctor.el Joshua Varner
2005-07-03 20:43   ` Richard M. Stallman [this message]
2005-08-02  9:42     ` doctor.el Juanma Barranquero
2005-08-03 13:33       ` doctor.el Richard M. Stallman

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=E1DpBIr-00026o-CA@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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 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).