Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Simplify code for tooltips in menus
Date: Mon, 05 Jan 2004 15:58:15 +0100	[thread overview]
Message-ID: <v91xqejvco.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3d6a2b0de.fsf@quimbies.gnus.org>

On Fri, Jan 02 2004, Lars Magne Ingebrigtsen wrote:

> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:

>> This would also be useful for `message.el'.  Can (should) we use stuff
>> from `gnus-util.el' there?
>
> Preferably not.
>
> But I've sometimes wished that there was a file in the Gnus
> distribution that just had self-contained little helper functions and
> macros (like this one).  misc.el or something.  h4x0r.el.

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.

> A collection of functions that could be included anywhere without
> worrying about requiring half the world...

I'd like to add the proposed `gnus-help' and some (self-contained)
functions/macro from `gnus-utils' to that new file.

Is there a reason why there are no ";;;###autoload" statements in
`gnus-util.el'?  Wouldn't it be useful for the new proposed file?

Bye, Reiner.

[1] Similar to this:

,----
| ;;; gnus-util.el --- utility functions for Gnus
| [...]
| ;;; Commentary:
| 
| ;; Nothing in this file depends on any other parts of Gnus -- all
| ;; functions and macros in this file are utility functions that are
| ;; used by Gnus and may be used by any other package without loading
| ;; Gnus first.
| 
| ;; [Unfortunately, it does depend on other parts of Gnus, e.g. the
| ;; autoloads below...]
`----
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  parent reply	other threads:[~2004-01-05 14:58 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 [this message]
2004-01-06  4:45     ` Lars Magne Ingebrigtsen
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=v91xqejvco.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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).