From: Tassilo Horn <tassilo@member.fsf.org>
To: info-gnus-english@gnu.org
Subject: Re: Gnus and new mail notification
Date: Sat, 25 Dec 2010 22:52:56 +0100 [thread overview]
Message-ID: <87oc89a5af.fsf@member.fsf.org> (raw)
In-Reply-To: <87tyi1dgb0.fsf@savara.sat.thregr.org>
Yuri D'Elia <wavexx@users.sf.net> writes:
Hi Yuri,
>> and you do something different (*desktop notification* instead of
>> *mode line* stuff)!
>
> gnus-desktop-notify? gnus-ext-notify?
I like the former, cause desktop notifications is the common term for
that kind of notifications.
>> How about making it a global minor mode?
>
> Any pointer in how to do that?
> I don't do elisp very often.
,----[ C-h f define-global-minor-mode RET ]
| define-global-minor-mode is an alias for `define-globalized-minor-mode' in
| `easy-mmode.el'.
|
| (define-global-minor-mode GLOBAL-MODE MODE TURN-ON &rest KEYS)
|
| Make a global mode GLOBAL-MODE corresponding to buffer-local minor MODE.
| TURN-ON is a function that will be called with no args in every buffer
| and that should try to turn MODE on if applicable for that buffer.
| KEYS is a list of CL-style keyword arguments. As the minor mode
| defined by this function is always global, any :global keyword is
| ignored. Other keywords have the same meaning as in `define-minor-mode',
| which see. In particular, :group specifies the custom group.
| The most useful keywords are those that are passed on to the
| `defcustom'. It normally makes no sense to pass the :lighter
| or :keymap keywords to `define-globalized-minor-mode', since these
| are usually passed to the buffer-local version of the minor mode.
|
| If MODE's set-up depends on the major mode in effect when it was
| enabled, then disabling and reenabling MODE should make MODE work
| correctly with the current major mode. This is important to
| prevent problems with derived modes, that is, major modes that
| call another major mode in their body.
`----
There's also an example in
,----[ (info "(elisp)Defining Minor Modes") ]
| The macro `define-minor-mode' offers a convenient way of implementing a
| mode in one self-contained definition.
`----
Bye,
Tassilo
next prev parent reply other threads:[~2010-12-25 21:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-24 23:33 Yuri D'Elia
2010-12-25 13:10 ` Philipp Haselwarter
2010-12-25 15:26 ` Yuri D'Elia
2010-12-25 21:52 ` Tassilo Horn [this message]
2010-12-26 20:11 ` Yuri D'Elia
2011-01-02 12:02 ` Philipp Haselwarter
[not found] <mailman.26.1293233609.7272.info-gnus-english@gnu.org>
2010-12-25 13:25 ` e20100633
2010-12-26 18:26 ` Philipp Haselwarter
2010-12-26 18:59 ` Philipp Haselwarter
2010-12-25 20:31 ` Richard Riley
2010-12-25 21:55 ` Tassilo Horn
2010-12-25 22:56 ` Yuri D'Elia
[not found] ` <mailman.13.1293317806.24913.info-gnus-english@gnu.org>
2010-12-25 23:19 ` Richard Riley
2010-12-26 16:22 ` Yuri D'Elia
[not found] ` <mailman.1.1293380566.6185.info-gnus-english@gnu.org>
2010-12-27 8:11 ` Richard Riley
2010-12-27 9:25 ` Thierry Volpiatto
[not found] ` <mailman.2.1293441979.18751.info-gnus-english@gnu.org>
2010-12-27 13:30 ` Richard Riley
2010-12-27 15:39 ` Philipp Haselwarter
2010-12-27 16:04 ` Thierry Volpiatto
[not found] ` <mailman.8.1293465927.24495.info-gnus-english@gnu.org>
2010-12-27 16:42 ` Richard Riley
2010-12-27 17:47 ` Thierry Volpiatto
[not found] ` <mailman.19.1293472126.24495.info-gnus-english@gnu.org>
2010-12-27 18:11 ` Richard Riley
2010-12-27 19:09 ` Thierry Volpiatto
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=87oc89a5af.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--cc=info-gnus-english@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.
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).