unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Deniz Dogan <deniz.a.m.dogan@gmail.com>
Cc: 5135@debbugs.gnu.org, Ryan Yeske <rcyeske@gmail.com>
Subject: bug#5135: [gnu.org #565169] Deniz Dogan EMACS Assignment
Date: Thu, 03 Jun 2010 10:56:32 -0400	[thread overview]
Message-ID: <87mxvcdv1b.fsf@stupidchicken.com> (raw)
In-Reply-To: <AANLkTinnPDYAAvlxpFw1eCcMHnyvx6WOqyMRk8JBoES5@mail.gmail.com> (Deniz Dogan's message of "Thu, 3 Jun 2010 10:41:18 +0200")

Deniz Dogan <deniz.a.m.dogan@gmail.com> writes:

> This patch adds the user option to sort nickname listings in the way
> that many other IRC clients sort them.
>
> Details:
> * Added rcirc-nickname<, a function which acts like string< but for
> IRC nicknames, making  <at>  less than + and comparing case-insensitively.
> * Added rcirc-sort-nicknames-join, a function which takes a string of
> IRC nicknames and a separator, sorts the nicknames and returns the
> result.
> * Added rcirc-sort-nicknames, a customizable variable which when
> non-nil will make rcirc sort any NAMES responses. nil by default.
> * Changed rcirc-handler-366 (RPL_ENDOFNAMES) to respect rcirc-sort-nicknames.

If most IRC clients sort nicknames this way, it may not be necessary to
create a new option `rcirc-sort-nicknames'.  We should just perform the
sorting automatically.  What do you think?  (I don't know enough about
"typical" IRC behavior to say).

Also, your docstrings need work.  Please read the Documentation node in
the Elisp manual:

     When you write a documentation string, make the first line a
     complete sentence (or two complete sentences) since some
     commands, such as `apropos', show only the first line of a
     multi-line documentation string.





       reply	other threads:[~2010-06-03 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <RT-Ticket-565169@rt.gnu.org>
     [not found] ` <h2k7b501d5c1004120658i8c3d2826vdc3ba01c5b8ae38e@mail.gmail.com>
     [not found]   ` <rt-3.4.5-26123-1274891873-1506.565169-5-0@rt.gnu.org>
     [not found]     ` <AANLkTilJo3lprNWKQ8RbBZt1mjXmEOPK5odV56D2cOyP@mail.gmail.com>
     [not found]       ` <AANLkTikiaZm0f3VobCrsWnv_GDx9OmCMHMrBO_ivIGfR@mail.gmail.com>
     [not found]         ` <876321udur.fsf@stupidchicken.com>
     [not found]           ` <AANLkTinnPDYAAvlxpFw1eCcMHnyvx6WOqyMRk8JBoES5@mail.gmail.com>
2010-06-03 14:56             ` Chong Yidong [this message]
2010-06-03 15:53               ` bug#5135: [gnu.org #565169] Deniz Dogan EMACS Assignment Deniz Dogan
2010-06-03 16:01                 ` Ryan Yeske
2010-06-03 17:23                   ` Chong Yidong
2010-06-03 15:28             ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mxvcdv1b.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=5135@debbugs.gnu.org \
    --cc=deniz.a.m.dogan@gmail.com \
    --cc=rcyeske@gmail.com \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).