From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Simplify code for tooltips in menus
Date: Tue, 06 Jan 2004 05:45:44 +0100 [thread overview]
Message-ID: <m3ad51znuv.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <v91xqejvco.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> I think we should do this. Could you suggest a name and kick-start it
> (add to CVS, write something about its purpose [1])?
>
> What about the name-space (package prefix)? Should the helper
> functions start with "gnus-"? If not, it would be easier to find real
> dependencies packages or libraries that are supposed to be independent
> from Gnus, like `message.el', `mm-*.el', `mml-*.el', what-else? But
> OTOH, a different name-space would need a lot of renaming in the Gnus
> code.
Let's see... there's already a mm-util.el file, and a mail-utils.el
file... How about nnutil.el? Or how about just stuffing more of
these functions/macros into mm-util? It looks like it only has
general utility functions and stuff, but quite a few compatibility
functions, too. Which might or might not be a plus.
> Is there a reason why there are no ";;;###autoload" statements in
> `gnus-util.el'? Wouldn't it be useful for the new proposed file?
Well, everything requires gnus-util.el, so there's really not much
point. autoloads are mostly useful for functions from files that you
don't require.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2004-01-06 4:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-01 13:54 Reiner Steib
2004-01-02 19:45 ` Lars Magne Ingebrigtsen
2004-01-02 21:04 ` Steve Youngs
2004-01-05 14:58 ` Reiner Steib
2004-01-06 4:45 ` Lars Magne Ingebrigtsen [this message]
2006-01-16 17:44 ` Small self-contained helper library for Gnus (was: Simplify code for tooltips in menus) Reiner Steib
2006-01-20 21:51 ` Small self-contained helper library for Gnus Reiner Steib
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=m3ad51znuv.fsf@quimbies.gnus.org \
--to=larsi@gnus.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.
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).