From b4c3267ac7793d9a18148b351b41d45f609e7df2 Mon Sep 17 00:00:00 2001 From: yamaoka Date: Tue, 8 Jan 2002 11:49:44 +0000 Subject: [PATCH] * gnus-art.el (article-toggle-headers): Expose headers even if there is a boundary line. --- ChangeLog | 3 +++ lisp/gnus-art.el | 11 ++++++++--- 2 files changed, 11 insertions(+), 3 deletions(-) diff --git a/ChangeLog b/ChangeLog index a8cedd9..3e39cee 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,5 +1,8 @@ 2002-01-08 Katsumi Yamaoka + * lisp/gnus-art.el (article-toggle-headers): Expose headers even + if there is a boundary line. + * lisp/nntp.el (nntp-send-buffer): Don't use `mm-with-unibyte-current-buffer'. Use expanded form instead. diff --git a/lisp/gnus-art.el b/lisp/gnus-art.el index ace8ad9..d4d0441 100644 --- a/lisp/gnus-art.el +++ b/lisp/gnus-art.el @@ -1665,13 +1665,18 @@ if given a positive prefix, always hide." 'invisible t))) ;; If the invisible text is not terminated with newline, we ;; won't expose it. Because it may be created by x-face-mule. - ;; BTW, XEmacs sometimes fail in putting a invisible text + ;; BTW, XEmacs sometimes fail in putting an invisible text ;; property with `gnus-article-hide-text' (really?). In that ;; case, the invisible text might be started from the middle of - ;; a line so we will expose the sort of thing. + ;; a line, so we will expose the sort of thing. (when (or (not (or (eq header-start field-start) (eq ?\n (char-before field-start)))) - (eq ?\n (char-before field-end))) + (eq ?\n (char-before field-end)) + ;; Expose a boundary line anyway. + (string-equal + "\nX-Boundary: " + (buffer-substring (max (- field-end 13) header-start) + field-end))) (remove-text-properties field-start field-end gnus-hidden-properties) (put-text-property field-start field-end -- 1.7.10.4