Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: A P documentation could be enhanced
Date: Sun, 04 Jan 2004 19:12:37 +0100	[thread overview]
Message-ID: <87brpjd1m2.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <87k747d24h.fsf@emptyhost.emptydomain.de>

Here is a suggestion for a docstring.  What do you think?  Does it
describe the behavior better?

--- gnus-sum.el.~6.373.~	Fri Jan  2 17:49:04 2004
+++ gnus-sum.el	Sun Jan  4 19:09:33 2004
@@ -8534,10 +8534,16 @@
 			  "[()]" "\\\\\\&"))
 
 (defun gnus-summary-print-article (&optional filename n)
-  "Generate and print a PostScript image of the N next (mail) articles.
+  "Generate and print a PostScript image of the process-marked (mail) articles.
 
-If N is negative, print the N previous articles.  If N is nil and articles
-have been marked with the process mark, print these instead.
+If used interactively, print the current article if none are
+process-marked.  With prefix arg, prompt the user for the name of the
+file to save in.
+
+When used from Lisp, accept two optional args FILENAME and N.  N means
+to print the next N articles.  If N is negative, print the N previous
+articles.  If N is nil and articles have been marked with the process
+mark, print these instead.
 
 If the optional first argument FILENAME is nil, send the image to the
 printer.  If FILENAME is a string, save the PostScript image in a file with



  parent reply	other threads:[~2004-01-04 18:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-03 17:23 Kai Grossjohann
2004-01-03 18:57 ` Lars Magne Ingebrigtsen
2004-01-03 22:31   ` Kai Grossjohann
2004-01-04  0:21     ` Lars Magne Ingebrigtsen
2004-01-04 18:01       ` Kai Grossjohann
2004-01-04 18:04         ` Kai Grossjohann
2004-01-04 18:12         ` Kai Grossjohann [this message]
2004-01-04 20:48           ` Lars Magne Ingebrigtsen

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=87brpjd1m2.fsf@emptyhost.emptydomain.de \
    --to=kai@emptydomain.de \
    /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).