Gnus development mailing list
 help / color / mirror / Atom feed
From: Raja R Harinath <harinath@cs.umn.edu>
Subject: Miscelleous notes/bugs
Date: 27 May 1996 22:22:19 +0000	[thread overview]
Message-ID: <d9ras5ah9g.fsf@cs.umn.edu> (raw)

Gnus v5.2.1; nntp 4.0; nnml 1.0; nnmh 1.0; nndir 1.0; nndoc 1.0; nndraft 1.0; nnfolder 1.0

* Local hooks not useful

SGnus uses `gnus-make-local-hook' in two places, but these hooks are
effectively useless.  This is because the `add-hook' immediately after
it does _not_ set the local hook.  `add-hook' has a fourth parameter
that has to be non-nil for it to add to the local hook.  Maybe,
`gnus-add-to-local-hook' has to be defined, which is either plain
`add-hook' for XEmacs, or adds the 'local parameter in case of Emacs.
This could also clean up the ugly tests in `gnus-gl.el', like the
following:

      (if (not (fboundp 'make-local-hook))
          (add-hook 'gnus-select-article-hook 'grouplens-do-time)
        (make-local-hook 'gnus-select-article-hook)
        (add-hook 'gnus-select-article-hook 'grouplens-do-time nil 'local))

This bug became apparent when I exited gnus, and tried to send a
message.  `message-sent-hook' still had `gnus-inews-do-gcc', and it
started complaining about selecting a deleted buffer.

(In fact, I sent a previous bug report on this, but due to this error
during send, I was not sure whether the message was actually sent or
not.  It hadn't appeared on the `gnus-bug' archive a half-hour after I
sent it...)

* Emacs 19.31 timers

Should `gnus-demon' be rewritten to use the new API of Emacs timers
(run-with-timer, run-with-idle-timer)?

* `derived.el'

I saw `derived.el' in the Emacs `lisp/' directory.  It appears to
support major-mode inheritance (keymaps, syntax-tables, etc., are
automatically copied on derivation.)  Should "grouplens" and other
variants of the "summary" mode use this mechanism?

* `nn*.el' independent of `gnus*.el'?

Can `message.el' use some of the features of `nn*.el' without loading
the rest of Gnus? (`message-post-method' uses one of the "nn*"
backends.)  If so, can message archiving be supported without loading
Gnus?

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu
"When all else fails, read the instructions."      -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing."   -- Roy L Ash


             reply	other threads:[~1996-05-27 22:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-05-27 22:22 Raja R Harinath [this message]
1996-05-28 19:44 ` Lars Magne Ingebrigtsen
1996-05-29  8:49   ` Steinar Bang
1996-05-29 21:07     ` 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=d9ras5ah9g.fsf@cs.umn.edu \
    --to=harinath@cs.umn.edu \
    /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).