unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Kelvin White <kelvin.white77@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Lawrence Mitchell <wence@gmx.li>, Michael Olson <mwolson@gnu.org>,
	17755@debbugs.gnu.org, Mario Lang <mlang@delysid.org>,
	Diane Murray <disumu@x3y2z1.net>, Alex Schroeder <alex@gnu.org>,
	Kelvin White <kelvin.white77@gmail.com>,
	Julien Danjou <julien@danjou.info>,
	Francis Litterio <franl@users.sourceforge.net>,
	Jorgen Schaefer <forcer@users.sourceforge.net>
Subject: bug#17755: 24.3; ERC user mode support
Date: Wed, 18 Jun 2014 14:51:22 -0400	[thread overview]
Message-ID: <87wqcef3v9.wl%kelvin.white77@gmail.com> (raw)
In-Reply-To: <jwv7g4e5bfe.fsf-monnier+emacsbugs@gnu.org>

At Wed, 18 Jun 2014 14:32:09 -0400,
Stefan Monnier wrote:
> 
> >> > + (defsubst erc-channel-user-owner-p (nick)
> >> > +   "Return t if NICK is an owner of the current channel."
> >> Usually we say "non-nil" rather than "t", unless the callers need to
> >> rely on the return value being t rather than some other non-nil value.
> > Indeed, the callers do rely on the value being t in this case. rather than
> > just non-nil
> 
> Hmm?  I see only one call to erc-channel-user-owner-p and the result is
> passed to `cond' so any non-nil value will work as well (which is the
> way it should be for functions named `<foo>-p').
> 
You are right, this could be non-nil. I was looking at
`erc-channel-user-owner' not the predicate form
`erc-channel-user-owner-p'.
> > + 2014-06-11  Kelvin White  <kelvin.white77@gmail.com>
> > + 
> > + 	* erc-backend.el: Handle user modes in relevent server responses
> > + 	* erc.el: Better user mode support.
> > + 	(erc-channel-user): Add members for new modes.
> > + 	(erc-channel-member-halfop-p, erc-channel-user-admin-p, erc-channel-user-owner-p): Use new struct members.
> > + 	(erc-format-nick, erc-format-@nick): Display user modes as nick prefix.
> > + 	(erc-nick-prefix-face, erc-my-nick-prefix-face): Add new faces to separate colors if desired.
> > + 	(erc-get-user-mode-prefix): Return symbol for mode prefix.
> > + 	(erc-update-channel-member, erc-update-current-channel-member, erc-channel-receive-names): Update channel users.
> > + 	(erc-nick-at-point): Return correct user info.
> > + 
> 
Ah yes, I did change the rest of the code to under 80 columns, but it
looks like I missed the changelog. Sorry, it's been one of those days.
> Please try a bit harder to stay within 80 columns.  M-q is your friend.
> 
> > ! ;; Hacker: l3thal@smashthestack.org
> > ! ;; Created: 2004-05-07
> > ! ;; Hacked: 2014-06-08
> 
This and the next comment slipped my me on mistake. 
This was for my own use to track revisions as It wasn't in version control.
It should not have been included in the patch 
> If you want to add your name, add it to the "Author:" part (one per
> line, see in erc.el for an example).  And don't add entries like
> timestamps of when it was last changed.  This just causes spurious
> conflicts when merging branches.  This info is readily available via
> "bzr log".  I tolerate things like "Created" (tho find it a waste of
> perfectly good bits and screen real estate) because, by nature these
> should never change and hence don't cause such spurious conflicts.
> 
> > ! ;;; hacked
> >   (define-erc-response-handler (JOIN)
> > !   "HACKED: Handle join messages."
> 
> What does this "hacked" mean here?  Looks like left-over annotations you
> used temporarily to keep track of what you changed.
This was a mistake, please see above.
> 
> Anyway, the patch looks OK to me.  As soon as your copyright paperwork
> comes through I can give you write access and you can install it.
> 
> 
>         Stefan





  reply	other threads:[~2014-06-18 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 10:34 bug#17755: 24.3; ERC user mode support kelvin.white77
2014-06-11 11:45 ` Kelvin White
2014-06-17 16:03   ` Stefan Monnier
2014-06-18 14:40     ` Kelvin White
2014-06-18 16:08       ` Kelvin White
2014-06-18 18:32       ` Stefan Monnier
2014-06-18 18:51         ` Kelvin White [this message]
2014-10-02 19:31 ` Paul Eggert

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=87wqcef3v9.wl%kelvin.white77@gmail.com \
    --to=kelvin.white77@gmail.com \
    --cc=17755@debbugs.gnu.org \
    --cc=alex@gnu.org \
    --cc=disumu@x3y2z1.net \
    --cc=forcer@users.sourceforge.net \
    --cc=franl@users.sourceforge.net \
    --cc=julien@danjou.info \
    --cc=mlang@delysid.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=mwolson@gnu.org \
    --cc=wence@gmx.li \
    /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).