From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-devel@gnu.org
Subject: Re: Documentation of nnoo.el
Date: Sun, 12 Jul 2015 20:15:26 +0800 [thread overview]
Message-ID: <87a8v16081.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87vbdphbg5.fsf@gmx.us
Rasmus <rasmus@gmx.us> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> 3. Easier hackage/extensibility. Contributors currently have very hard
>> time figuring out how everything works; this would help. Subclassing
>> would also make it much easier for people to write new backends, or
>> modify existing ones.
>
> It's extremely hard to write patches for Gnus 'cause it's so hard to
> figure out what is going on.
>
> And dev. documentation is/docstrings are not the best, though user
> documentation is pretty awesome.
Which isn't to say that an EIEIO rewrite would magically result in
better documentation, but if the code were simplified at the same time
that a general overhaul were undertaken... it would make things more
comprehensible.
next prev parent reply other threads:[~2015-07-12 12:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 15:01 Documentation of nnoo.el Stefan Monnier
2015-07-12 1:32 ` Eric Abrahamsen
2015-07-12 2:25 ` Stefan Monnier
2015-07-12 3:44 ` Eric Abrahamsen
2015-07-12 11:17 ` Rasmus
2015-07-12 12:15 ` Eric Abrahamsen [this message]
2015-07-12 18:05 ` Lars Magne Ingebrigtsen
2015-07-13 2:56 ` Eric Abrahamsen
2015-12-24 16:59 ` Lars Ingebrigtsen
2015-12-25 3:44 ` Eric Abrahamsen
2015-12-26 22:11 ` Lars Ingebrigtsen
2015-12-27 1:03 ` Eric Abrahamsen
2015-12-27 6:03 ` Lars Ingebrigtsen
2015-07-12 17:55 ` Lars Magne Ingebrigtsen
2015-07-12 18:22 ` Nikolaus Rath
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=87a8v16081.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.