Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: ding@gnus.org
Subject: Re: interactive-p
Date: Wed, 10 Nov 2004 22:14:51 -0500	[thread overview]
Message-ID: <E1CS5QB-00083T-Ee@fencepost.gnu.org> (raw)
In-Reply-To: <m3oei67gwv.fsf@quimbies.gnus.org> (message from Lars Magne Ingebrigtsen on Wed, 10 Nov 2004 00:15:44 +0100)

    I'm not quite sure what counts as bad uses.  Functions that change
    their behavior surprisingly based on whether they're called
    interactively or not?

Please look at the latest commands.texi; it explains what is good
and bad usage of interactive-p.  I updated it a week ago.



  parent reply	other threads:[~2004-11-11  3:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1COWYP-0001lW-Tc@fencepost.gnu.org>
2004-11-09 23:15 ` interactive-p Lars Magne Ingebrigtsen
2004-11-09 23:33   ` interactive-p Simon Josefsson
2004-11-11  3:14   ` Richard Stallman [this message]
2004-11-11  4:00     ` interactive-p Katsumi Yamaoka

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1CS5QB-00083T-Ee@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=ding@gnus.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 NNTP newsgroup(s).