[gnus git] branch master updated: n0-17-41-gc0a090e =1= shr: add support for del tag

Julien Danjou <[email protected]>
Newsgroups gmane.emacs.gnus.cvs
Message-ID <[email protected]>
       via  c0a090e1ab6cbddff4547fb6577d31972287d60e (commit)
      from  bd74ba3e89556c0194b3ab3051226d3d8cb16cf0 (commit)


- Log -----------------------------------------------------------------
commit c0a090e1ab6cbddff4547fb6577d31972287d60e
Author: Julien Danjou <[email protected]>
Date:   Mon May 16 10:44:14 2011 +0200

    shr: add support for del tag
    
    Signed-off-by: Julien Danjou <[email protected]>

diff --git a/lisp/ChangeLog b/lisp/ChangeLog
index fe9e083..0d8e984 100644
--- a/lisp/ChangeLog
+++ b/lisp/ChangeLog
@@ -1,3 +1,7 @@
+2011-05-16  Julien Danjou  <[email protected]>
+
+	* shr.el (shr-tag-del): Add support for del tag.
+
 2011-05-13  Katsumi Yamaoka  <[email protected]>
 
 	* gnus-html.el (gnus-html-put-image): Register a displayer.
diff --git a/lisp/shr.el b/lisp/shr.el
index edd1066..d23d9c7 100644
--- a/lisp/shr.el
+++ b/lisp/shr.el
@@ -780,6 +780,9 @@ ones, in case fg and bg are nil."
 (defun shr-tag-s (cont)
   (shr-fontize-cont cont 'shr-strike-through))
 
+(defun shr-tag-del (cont)
+  (shr-fontize-cont cont 'shr-strike-through))
+
 (defun shr-tag-b (cont)
   (shr-fontize-cont cont 'bold))
 

-----------------------------------------------------------------------
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we listed those
revisions in full, above.

Summary of changes:
 lisp/ChangeLog |    4 ++++
 lisp/shr.el    |    3 +++
 2 files changed, 7 insertions(+), 0 deletions(-)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Gnus Project".

The branch, master has been updated


hooks/post-receive
-- 
Gnus Project
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.