Mercurial > emacs
comparison lisp/mail/rnewspost.el @ 10804:abd9ad4309b0
Various doc fixes.
(news-post-news): Add autoload cookie.
author | Richard M. Stallman <rms@gnu.org> |
---|---|
date | Thu, 23 Feb 1995 04:59:43 +0000 |
parents | 99b9f20b6921 |
children | 8535e6d5f8bb |
comparison
equal
deleted
inserted
replaced
10803:b8c4a1b7d484 | 10804:abd9ad4309b0 |
---|---|
108 (setq paragraph-separate (concat "^" mail-header-separator "$\\|" | 108 (setq paragraph-separate (concat "^" mail-header-separator "$\\|" |
109 paragraph-separate)) | 109 paragraph-separate)) |
110 (run-hooks 'text-mode-hook 'news-reply-mode-hook)) | 110 (run-hooks 'text-mode-hook 'news-reply-mode-hook)) |
111 | 111 |
112 (defvar news-reply-yank-from | 112 (defvar news-reply-yank-from |
113 "Save From: field for news-reply-yank-original." | 113 "Save `From:' field for `news-reply-yank-original'." |
114 "") | 114 "") |
115 | 115 |
116 (defvar news-reply-yank-message-id | 116 (defvar news-reply-yank-message-id |
117 "Save Message-Id: field for news-reply-yank-original." | 117 "Save `Message-Id:' field for `news-reply-yank-original'." |
118 "") | 118 "") |
119 | 119 |
120 (defun news-reply-yank-original (arg) | 120 (defun news-reply-yank-original (arg) |
121 "Insert the message being replied to, if any (in rmail). | 121 "Insert the message being replied to, if any (in Mail mode). |
122 Puts point before the text and mark after. | 122 Puts point before the text and mark after. |
123 Indents each nonblank line ARG spaces (default 3). | 123 Indents each nonblank line ARG spaces (default 3). |
124 Just \\[universal-argument] as argument means don't indent | 124 Just \\[universal-argument] as argument means don't indent |
125 and don't delete any header fields." | 125 and don't delete any header fields." |
126 (interactive "P") | 126 (interactive "P") |
133 (insert "In article " news-reply-yank-message-id | 133 (insert "In article " news-reply-yank-message-id |
134 " " news-reply-yank-from " writes:\n\n")) | 134 " " news-reply-yank-from " writes:\n\n")) |
135 "Hook for inserting a header at the top of a yanked message.") | 135 "Hook for inserting a header at the top of a yanked message.") |
136 | 136 |
137 (defun news-reply-newsgroups () | 137 (defun news-reply-newsgroups () |
138 "Move point to end of Newsgroups: field. | 138 "Move point to end of `Newsgroups:' field. |
139 RFC 850 constrains the Newsgroups: field to be a comma separated list of valid | 139 RFC 850 constrains the `Newsgroups:' field to be a comma-separated list |
140 newsgroups names at your site: | 140 of valid newsgroup names at your site. For example, |
141 Newsgroups: news.misc,comp.misc,rec.misc" | 141 Newsgroups: news.misc,comp.misc,rec.misc" |
142 (interactive) | 142 (interactive) |
143 (expand-abbrev) | 143 (expand-abbrev) |
144 (goto-char (point-min)) | 144 (goto-char (point-min)) |
145 (mail-position-on-field "Newsgroups")) | 145 (mail-position-on-field "Newsgroups")) |
146 | 146 |
147 (defun news-reply-followup-to () | 147 (defun news-reply-followup-to () |
148 "Move point to end of Followup-To: field. Create the field if none. | 148 "Move point to end of `Followup-To:' field. Create the field if none. |
149 One usually requests followups to only one newsgroup. | 149 One usually requests followups to only one newsgroup. |
150 RFC 850 constrains the Followup-To: field to be a comma separated list of valid | 150 RFC 850 constrains the `Followup-To:' field to be a comma-separated list |
151 newsgroups names at your site, that are also in the Newsgroups: field: | 151 of valid newsgroups names at your site, and it must be a subset of the |
152 Newsgroups: news.misc,comp.misc,rec.misc,misc.misc,soc.misc | 152 `Newsgroups:' field. For example: |
153 Followup-To: news.misc,comp.misc,rec.misc" | 153 Newsgroups: news.misc,comp.misc,rec.misc,misc.misc,soc.misc |
154 Followup-To: news.misc,comp.misc,rec.misc" | |
154 (interactive) | 155 (interactive) |
155 (expand-abbrev) | 156 (expand-abbrev) |
156 (or (mail-position-on-field "Followup-To" t) | 157 (or (mail-position-on-field "Followup-To" t) |
157 (progn (mail-position-on-field "newsgroups") | 158 (progn (mail-position-on-field "newsgroups") |
158 (insert "\nFollowup-To: "))) | 159 (insert "\nFollowup-To: "))) |
159 ;; @@ could do a completing read based on the Newsgroups: field to | 160 ;; @@ could do a completing read based on the Newsgroups: field to |
160 ;; @@ fill in the Followup-To: field | 161 ;; @@ fill in the Followup-To: field |
161 ) | 162 ) |
162 | 163 |
163 (defun news-reply-distribution () | 164 (defun news-reply-distribution () |
164 "Move point to end of Distribution: optional field. | 165 "Move point to end of `Distribution:' optional field. |
165 Create the field if none. Without this field the posting goes to all of | 166 Create the field if none. Without this field the posting goes to all of |
166 USENET. The field is used to restrict the posting to parts of USENET." | 167 USENET. The field is used to restrict the posting to parts of USENET." |
167 (interactive) | 168 (interactive) |
168 (expand-abbrev) | 169 (expand-abbrev) |
169 (mail-position-on-field "Distribution") | 170 (mail-position-on-field "Distribution") |
170 ;; @@could do a completing read based on the news library file: | 171 ;; @@could do a completing read based on the news library file: |
171 ;; @@ ../distributions to fill in the field. | 172 ;; @@ ../distributions to fill in the field. |
172 ) | 173 ) |
173 | 174 |
174 (defun news-reply-keywords () | 175 (defun news-reply-keywords () |
175 "Move point to end of Keywords: optional field. Create the field if none. | 176 "Move point to end of `Keywords:' optional field. Create the field if none. |
176 Used as an aid to the news reader, it can contain a few, well selected keywords | 177 Used as an aid to the news reader, it can contain a few, well selected keywords |
177 identifying the message." | 178 identifying the message." |
178 (interactive) | 179 (interactive) |
179 (expand-abbrev) | 180 (expand-abbrev) |
180 (mail-position-on-field "Keywords")) | 181 (mail-position-on-field "Keywords")) |
181 | 182 |
182 (defun news-reply-summary () | 183 (defun news-reply-summary () |
183 "Move point to end of Summary: optional field. Create the field if none. | 184 "Move point to end of `Summary:' optional field. Create the field if none. |
184 Used as an aid to the news reader, it can contain a succinct | 185 Used as an aid to the news reader, it can contain a succinct |
185 summary (abstract) of the message." | 186 summary (abstract) of the message." |
186 (interactive) | 187 (interactive) |
187 (expand-abbrev) | 188 (expand-abbrev) |
188 (mail-position-on-field "Summary")) | 189 (mail-position-on-field "Summary")) |
191 "The inews program appends ~/.signature automatically." | 192 "The inews program appends ~/.signature automatically." |
192 (interactive) | 193 (interactive) |
193 (message "~/.signature will be appended automatically.")) | 194 (message "~/.signature will be appended automatically.")) |
194 | 195 |
195 (defun news-setup (to subject in-reply-to newsgroups replybuffer) | 196 (defun news-setup (to subject in-reply-to newsgroups replybuffer) |
196 "Setup the news reply or posting buffer with the proper headers and in | 197 "Set up the news reply or posting buffer with the proper headers and mode." |
197 news-reply-mode." | |
198 (setq mail-reply-buffer replybuffer) | 198 (setq mail-reply-buffer replybuffer) |
199 (let ((mail-setup-hook nil)) | 199 (let ((mail-setup-hook nil)) |
200 (if (null to) | 200 (if (null to) |
201 ;; this hack is needed so that inews wont be confused by | 201 ;; this hack is needed so that inews wont be confused by |
202 ;; the fcc: and bcc: fields | 202 ;; the fcc: and bcc: fields |
361 (insert message-id)) | 361 (insert message-id)) |
362 (goto-char (point-max)))))) | 362 (goto-char (point-max)))))) |
363 (message ""))) | 363 (message ""))) |
364 | 364 |
365 ;@@ the guts of news-reply and news-post-news should be combined. -tower | 365 ;@@ the guts of news-reply and news-post-news should be combined. -tower |
366 ;;;###autoload | |
366 (defun news-post-news () | 367 (defun news-post-news () |
367 "Begin editing a new USENET news article to be posted. | 368 "Begin editing a new USENET news article to be posted. |
368 Type \\[describe-mode] once editing the article to get a list of commands." | 369 Type \\[describe-mode] once editing the article to get a list of commands." |
369 (interactive) | 370 (interactive) |
370 (if (y-or-n-p "Are you sure you want to post to all of USENET? ") | 371 (if (y-or-n-p "Are you sure you want to post to all of USENET? ") |