unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: cua: quiet warning messages
Date: Tue, 01 Jul 2003 11:17:22 -0400	[thread overview]
Message-ID: <E19XMsk-0003c7-4G@fencepost.gnu.org> (raw)
In-Reply-To: <200306231700.h5NH0NXr019258@rum.cs.yale.edu> (monnier+gnu/emacs@cs-www.cs.yale.edu)

    As far as I know, minor modes are only ever called with the
    following arguments:

	    - integers
	    - nil
	    - t
	    - a one-element list containing an integer
	    - toggle

I think there are others, such as the symbol `-'.

    This last one is new and only happens when the minor mode is
    called interactively.

One problem with specifying this behavior for `toggle' is that many
minor modes don't currently implement it.  They would need to be
changed.

    It could even not specify the behavior in the `toggle' case since
    it's only used internally between the interactive spec and
    the minor mode's body.

That makes it feasible.

How about text for modes.texi?



The command should accept one optional argument.  If the argument is
@code{nil}, it should toggle the mode (turn it on if it is off, and
off if it is on).  It should turn the mode on if the argument is a
positive integer, the symbol @code{t}, or a list whose @sc{car} is one
of those.  It should turn the mode off if the argument is a negative
integer or zero, the symbol @code{-}, or a list whose @sc{car} is one
of those.  The meaning of other arguments is not specified.

  reply	other threads:[~2003-07-01 15:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-16 17:04 cua: quiet warning messages Michael Mauger
2003-06-16 18:47 ` Luc Teirlinck
2003-06-16 19:12   ` Stefan Monnier
2003-06-16 19:41     ` Luc Teirlinck
2003-06-22  3:01     ` Richard Stallman
2003-06-23 17:00       ` Stefan Monnier
2003-07-01 15:17         ` Richard Stallman [this message]
2003-07-04  0:47           ` 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=E19XMsk-0003c7-4G@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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).