Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Concerning marks and the back end.
Date: Sat, 04 Jan 2003 15:52:05 +0100	[thread overview]
Message-ID: <84y961vuga.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <86el7uj5a9.fsf@asfast.com>

Lloyd Zusman <ljz@asfast.com> writes:

> But I don't want to type one set of keystrokes to enter a group with
> unread articles, and a different set of keystrokes to enter a group with
> no unread articles.

Now that you have all the pieces, you can just write a function to
call instead of gnus-topic-select-group that looks if the group is
empty and then does one thing if yes and another thing if no.  No?
-- 
Ambibibentists unite!



  reply	other threads:[~2003-01-04 14:52 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-01 22:23 Lloyd Zusman
2003-01-02 16:57 ` Kai Großjohann
2003-01-02 18:23   ` Lloyd Zusman
2003-01-02 18:46     ` Lars Magne Ingebrigtsen
2003-01-03  2:23       ` Lloyd Zusman
2003-01-03  2:45         ` Simon Josefsson
2003-01-03  2:56           ` Lloyd Zusman
2003-01-03  3:01             ` Lloyd Zusman
2003-01-03  4:11               ` Simon Josefsson
2003-01-03  4:59                 ` Lloyd Zusman
2003-01-03 14:57                   ` Simon Josefsson
2003-01-04 18:23                   ` Lloyd Zusman
2003-01-13 18:47                     ` A solution that's better than my ugly hack? Lloyd Zusman
2003-01-13 18:53                       ` Lars Magne Ingebrigtsen
2003-01-13 19:00                         ` Lloyd Zusman
2003-01-13 19:18                           ` Lars Magne Ingebrigtsen
2003-01-13 19:26                             ` Lloyd Zusman
2003-01-13 19:30                               ` Lars Magne Ingebrigtsen
2003-01-13 19:33                                 ` Lloyd Zusman
2003-01-13 21:04                                 ` Lloyd Zusman
2003-01-13 19:32                               ` Lloyd Zusman
2003-01-03 17:54         ` Concerning marks and the back end Kai Großjohann
2003-01-03 18:20           ` Lloyd Zusman
2003-01-03 17:53     ` Kai Großjohann
2003-01-03 18:15       ` Lloyd Zusman
2003-01-03 19:18         ` Kai Großjohann
2003-01-03 19:34           ` Lloyd Zusman
2003-01-03 19:43             ` Lloyd Zusman
2003-01-03 21:03               ` Kai Großjohann
2003-01-03 21:24                 ` Lloyd Zusman
2003-01-04 14:52                   ` Kai Großjohann [this message]
2003-01-04 16:19                     ` Lloyd Zusman
2003-01-03 20:17             ` Lars Magne Ingebrigtsen
2003-01-03 20:41               ` Lloyd Zusman
2003-01-03 20:45                 ` Lars Magne Ingebrigtsen
2003-01-03 20:52                   ` Lloyd Zusman
2003-01-03 21:05                     ` Kai Großjohann
2003-01-03 21:05                 ` Kai Großjohann
2003-01-04  4:50                   ` Lloyd Zusman
2003-01-03 20:53             ` Paul Jarc
2003-01-03 20:58               ` Lloyd Zusman
2003-01-03 21:02             ` Kai Großjohann
2003-01-02 19:14 ` Simon Josefsson
2003-01-03  2:25   ` Lloyd Zusman

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=84y961vuga.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@uni-duisburg.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).