Gnus development mailing list
 help / color / mirror / Atom feed
From: steve@miranova.com (Steven L. Baur)
Subject: Re: New features + feature freeze?
Date: 14 Dec 1995 20:02:28 -0800	[thread overview]
Message-ID: <m2enu7gejv.fsf@diana.miranova.com> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 13 Dec 1995 10:22:07 -0800

>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

    Lars> I've been whittling away on the todo list, and it's now down
    Lars> to only 75 remaining items.  :-) At this rate, they may all
    Lars> be done by New Year.

    Lars> So perhaps there should be a new feature freeze in January
    Lars> so that we can get September working reliably.  Two months
    Lars> beta, and then we should have Gnus 5.2 ready for general
    Lars> usage Marchish?

Sounds good.  At this point I'd rather see all the ``old'' features
work reliably (NOCEM, a port of customize to XEmacs, and Gnus Daemon
come to mind) before adding more stuff.

Speaking of testing and old features, I've noticed a fair number of
questions regarding usage and problems with Gnus and foreign servers.
Is there anyone who can donate NNTP access to allow Gnus testing on
this?  I'd like to test with another NNTP server, but won't have
access to another one until at least mid '96.

    Lars> (I probably shouldn't say this, but...)  If you have ideas
    Lars> for anything neat that you think definitely should be in
    Lars> Gnus, you should probably speak up soon(ish), or it'll have
    Lars> to wait until April.

Since XEmacs has builtin sound support, it would be kind of nice to
have sound effects.  A toilet flushing when deleting articles, the
sound of a flyswatter striking when gnus-summary-mail-nastygram is
sending a message, the sound of letters being dropped into a mail box
when incoming mail arrives, etc.  :-)

    Lars> To take a look at the current (sort of; I've now shaved off
    Lars> 20 items) todo list, point your Web Thing to
    Lars> <URL:http://www.ifi.uio.no/~larsi/sgnus/todo>.

Not on your list:
* Gnus should be able to grok XHDR (I should have code to give you
  for this ready by this weekend)

* If we can't have any native Gnus support for color in the *Group*
  buffer, how about adding hooks to gnus-group-insert-group-line and
  gnus-group-update-group-line so that it can be added without hacking
  Gnus source?

* Tm MIME integration is incomplete at this time.
+ tm-edit doesn't have a buffer menu in mail mode by default
+ News Header hiding looks broken in tm-view
+ The last time I checked, C-c C-x C-z in a *news* post buffer was an
  unwise thing to do

* Customize has to be ported to XEmacs, or some better method of
  customizing colors needs to be added.

(Documentation)
* All hook functions need some documentation.  At the minimum, there
  should be a list of variables that can be safely used in that hook.

* All user callable gnus internal functions need to be at least
  enumerated, and the calling interface needs to be frozen at some
  point too.  It's difficult to customize and extend Gnus when it's a
  rapidly moving target.

-- 
steve@miranova.com baur


  parent reply	other threads:[~1995-12-15  4:02 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-12-13 18:22 Lars Magne Ingebrigtsen
1995-12-13 19:36 ` Wes Hardaker
1995-12-13 20:05   ` William Perry
1995-12-14 17:52     ` Wes Hardaker
1995-12-15  3:55       ` picons support (was Re: New features + feature freeze?) Ben Gross
1995-12-14  8:29   ` New features + feature freeze? Lars Magne Ingebrigtsen
1995-12-14 17:15     ` Wes Hardaker
1995-12-14 17:27       ` William Perry
1995-12-14 17:36         ` Wes Hardaker
1995-12-14 19:38       ` Lars Magne Ingebrigtsen
1995-12-14 20:49         ` Wes Hardaker
1995-12-15 19:14           ` Lars Magne Ingebrigtsen
1995-12-14 22:39         ` Steven L. Baur
1995-12-15 19:07       ` Lars Magne Ingebrigtsen
1995-12-14 18:25     ` Jens Lautenbacher
1995-12-15 19:14       ` Lars Magne Ingebrigtsen
1995-12-14 19:17     ` Jens Lautenbacher
1995-12-14 20:58       ` Wes Hardaker
1995-12-14 21:50         ` Wes Hardaker
1995-12-15 19:14           ` Lars Magne Ingebrigtsen
1995-12-15 22:54             ` Wes Hardaker
1995-12-16 16:28               ` Lars Magne Ingebrigtsen
1995-12-14 22:22         ` William Perry
1995-12-14 22:23           ` Wes Hardaker
1995-12-14  9:49 ` Kai Grossjohann
1995-12-14 19:38   ` Lars Magne Ingebrigtsen
1995-12-15  3:07     ` Steven L. Baur
1995-12-15 19:07   ` Lars Magne Ingebrigtsen
1995-12-15  4:02 ` Steven L. Baur [this message]
1995-12-15 15:19   ` 守岡 知彦 / MORIOKA Tomohiko
1995-12-15 16:32   ` Wes Hardaker
1995-12-20  2:53     ` Lars Magne Ingebrigtsen
1995-12-15 19:14   ` Lars Magne Ingebrigtsen
1995-12-15 23:51     ` Steven L. Baur
1995-12-16 14:43       ` Lars Magne Ingebrigtsen
1995-12-18 15:55 ` Sten Drescher
1995-12-20  2:53   ` Lars Magne Ingebrigtsen
1995-12-20 14:57     ` Sten Drescher
1995-12-21  3:21       ` Lars Magne Ingebrigtsen
1995-12-21 15:44         ` Sten Drescher
1995-12-22  3:56     ` Christopher Davis
1995-12-22 16:55       ` Sten Drescher
1996-01-03  8:54         ` Lars Magne Ingebrigtsen
1996-01-07  0:16           ` Christopher Davis
1996-01-10 18:37             ` Lars Magne Ingebrigtsen
1996-01-07  1:33           ` Sten Drescher
1996-01-07  7:44             ` Yair Friedman
1996-01-10 18:34               ` Lars Magne Ingebrigtsen
1996-01-12 15:00                 ` Per Abrahamsen
1996-01-14  6:08                   ` Greg Stark
1996-01-15 23:17                   ` Lars Magne Ingebrigtsen
1996-01-10 18:33             ` Lars Magne Ingebrigtsen
1996-01-12 11:31               ` Sten Drescher
1996-01-15 23:17                 ` Lars Magne Ingebrigtsen
1996-01-16  7:33                   ` Yair Friedman
1996-01-16 18:45                     ` Lars Magne Ingebrigtsen
1996-01-16 19:29                       ` Yair Friedman

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=m2enu7gejv.fsf@diana.miranova.com \
    --to=steve@miranova.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).