Gnus development mailing list
 help / color / mirror / Atom feed
From: Colin Rafferty <craffert@ms.com>
Subject: [patch] mode checking against picons
Date: 12 Jan 1999 10:36:42 -0500	[thread overview]
Message-ID: <vgvu2xwsdth.fsf@ms.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 542 bytes --]

Similar to yesterday's patch, I have noticed that in a check for
gnus-article-mode, we should be checking for gnus-picons-mode.

On the other hand, I'm not sure why there is a gnus-picons-mode.  Does 
it actually give us anything?

Maybe it should be a minor mode, and then the major-mode can still be
gnus-article-mode, and gnus-art.el doesn't need to know about picons,
and we may even be able to put picons in non-gnus-article-mode
buffers.

Anyway, here is my patch.  The line numbers may be off slightly
because of my previous patches.


[-- Attachment #2: patch for gnus-article-check-buffer --]
[-- Type: text/plain, Size: 578 bytes --]

1999-01-12  Colin Rafferty  <colin@xemacs.org>

	* gnus-art.el (gnus-article-check-buffer): Also check for
 	picons-mode.

--- lisp/gnus-art.el~	Sun Jan  3 08:36:04 1999
+++ lisp/gnus-art.el	Tue Jan 12 10:26:49 1999
@@ -2994,7 +2997,7 @@
 
 (defun gnus-article-check-buffer ()
   "Beep if not in an article buffer."
-  (unless (equal major-mode 'gnus-article-mode)
+  (unless (memq major-mode '(gnus-article-mode gnus-picons-mode))
     (error "Command invoked outside of a Gnus article buffer")))
 
 (defun gnus-article-read-summary-keys (&optional arg key not-restore-window)

[-- Attachment #3: Type: text/plain, Size: 10 bytes --]


;; Colin

             reply	other threads:[~1999-01-12 15:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-12 15:36 Colin Rafferty [this message]
1999-01-12 15:57 ` Lars Magne Ingebrigtsen
1999-01-12 20:20   ` Colin Rafferty
1999-01-12 16:42 ` Wes Hardaker

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=vgvu2xwsdth.fsf@ms.com \
    --to=craffert@ms.com \
    /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).