Gnus development mailing list
 help / color / mirror / Atom feed
From: <jari.aalto@poboxes.com>
Subject: [patch] 0.37 gnus-article-edit-article (added new hook)
Date: 20 Mar 1998 18:05:17 +0200	[thread overview]
Message-ID: <tbu38tl54y.fsf@blue.sea.net> (raw)

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


    I was seeking for a hook that would run after everything was set
    after article Edit command was called, but I only found

	gnus-article-edit-mode-hook
	  Variable: Hook run in article edit mode buffers.
	  Plist: 4 properties

    Which is run before the actual article is inserted to the buffer.
    If I have missed something, please ignore this patch.

    jari


[-- Attachment #2: gnus-art.el.diff --]
[-- Type: application/octet-stream, Size: 968 bytes --]

Prereq: 1.37

===================================================================
RCS file: RCS/gnus-art.el,v
retrieving revision 1.37
retrieving revision 1.37.1.1
diff -ubw -r1.37 -r1.37.1.1
--- 1.37	1998/03/19 08:21:51
+++ 1.37.1.1	1998/03/20 15:57:41
@@ -2567,6 +2567,11 @@
   :group 'gnus-article-various
   :type 'hook)
 
+(defcustom gnus-article-edit-article-hook  nil
+  "Hook run when everything has been set for article editing."
+  :group 'gnus-article-various
+  :type 'hook)
+
 (defvar gnus-article-edit-done-function nil)
 
 (defvar gnus-article-edit-mode-map nil)
@@ -2624,7 +2629,8 @@
     (gnus-configure-windows 'edit-article)
     (setq gnus-article-edit-done-function exit-func)
     (setq gnus-prev-winconf winconf)
-    (gnus-message 6 "C-c C-c to end edits")))
+    (gnus-message 6 "C-c C-c to end edits")
+    (run-hooks 'gnus-article-edit-article-hook)))
 
 (defun gnus-article-edit-done (&optional arg)
   "Update the article edits and exit."

             reply	other threads:[~1998-03-20 16:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-03-20 16:05 jari.aalto [this message]
1998-03-23 13:12 ` 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=tbu38tl54y.fsf@blue.sea.net \
    --to=jari.aalto@poboxes.com \
    --cc=jari.aalto@ntc.nokia.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).