unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Richard M. Stallman" <rms@gnu.org>
Cc: monnier@iro.umontreal.ca, bug-cc-mode@gnu.org,
	nickrob@snap.net.nz, emacs-devel@gnu.org
Subject: Re: c-submode-indicators at wrong place in minor-mode-alist
Date: Fri, 16 Dec 2005 20:05:20 -0500	[thread overview]
Message-ID: <E1EnQVk-00058c-8L@fencepost.gnu.org> (raw)
In-Reply-To: <Pine.LNX.3.96.1051216102114.548C-100000@acm.acm> (message from Alan Mackenzie on Fri, 16 Dec 2005 10:57:42 +0000 (GMT))

    >> CC Mode has a convention that defuns/variables with doc strings are
    >> part of the API (i.e. things like line-up functions and derived modes
    >> are "permitted" to use them), but those without doc strings are
    >> "internal", i.e.  subject to arbitrary change/disappearance between CC
    >> Mode versions.

This is how I used to do things, back when doc strings took
up space in Emacs.  But now they don't, so I suggest that you
aim in the future to give all functions and variables
real doc strings.


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click


      reply	other threads:[~2005-12-17  1:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-14 21:41 c-submode-indicators at wrong place in minor-mode-alist Stefan Monnier
2005-12-15  0:25 ` Nick Roberts
2005-12-15 14:25   ` Alan Mackenzie
2005-12-15 20:08     ` Nick Roberts
2005-12-16 10:18       ` Alan Mackenzie
2005-12-16 20:03         ` Nick Roberts
2005-12-17  8:22         ` Eli Zaretskii
2005-12-18  9:26           ` Alan Mackenzie
2005-12-15 20:40     ` Stefan Monnier
2005-12-16 10:57       ` Alan Mackenzie
2005-12-17  1:05         ` Richard M. Stallman [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

  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=E1EnQVk-00058c-8L@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=bug-cc-mode@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=nickrob@snap.net.nz \
    /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).