From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ryan Yeske Newsgroups: gmane.emacs.devel Subject: Re: rcirc changes Date: Thu, 16 Feb 2006 08:30:57 -0800 Message-ID: <87k6bv2rlq.fsf@cut.bc.hsia.telus.net> References: <87oe192men.fsf@cut.bc.hsia.telus.net> NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1140125854 8029 80.91.229.2 (16 Feb 2006 21:37:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 16 Feb 2006 21:37:34 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 16 22:37:31 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F9qoB-0004Hg-T7 for ged-emacs-devel@m.gmane.org; Thu, 16 Feb 2006 22:37:04 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F9qke-0007RQ-LA for ged-emacs-devel@m.gmane.org; Thu, 16 Feb 2006 16:33:24 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F9m5p-0006DZ-It for emacs-devel@gnu.org; Thu, 16 Feb 2006 11:34:58 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F9m55-0005n6-Tn for emacs-devel@gnu.org; Thu, 16 Feb 2006 11:34:13 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F9m2F-0002mN-1R for emacs-devel@gnu.org; Thu, 16 Feb 2006 11:31:15 -0500 Original-Received: from [199.185.220.224] (helo=priv-edtnes40.telusplanet.net) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F9m7D-0003Fl-Sh; Thu, 16 Feb 2006 11:36:24 -0500 Original-Received: from cut.bc.hsia.telus.net ([207.6.239.189]) by priv-edtnes40.telusplanet.net (InterMail vM.6.01.05.04 201-2131-123-105-20051025) with ESMTP id <20060216163100.FVRJ8515.priv-edtnes40.telusplanet.net@cut.bc.hsia.telus.net>; Thu, 16 Feb 2006 09:31:00 -0700 Original-To: Miles Bader In-reply-to: (message from Miles Bader on Thu, 16 Feb 2006 14:07:00 +0900) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:50630 Archived-At: Date: Thu, 16 Feb 2006 14:07:00 +0900 From: Miles Bader Sender: snogglethorpe@gmail.com Cc: emacs-devel@gnu.org Content-Disposition: inline On 2/15/06, Ryan Yeske wrote: > After running with your installed changes, I realize I don't really > like this particular feature (earlier I said "I like it" after only > reading the patch, not running it, sorry). It breaks nick-completion > (you still complete the underlying nicks, not abbrev) and it doesn't > deal with nick changes which are abbreviated. It seems like this is > adding a feature to solve a local problem... if your own nick is too > long, then you can just change it, can't you? That's the whole point, it changes the _presentation_ in a particular context, not the nick itself. In one particular context -- the nicks inserted into the log with each message -- they are used so incredibly often, that otherwise acceptable nicks can become very annoying. In that sense, it doesn't break completion or whatever, because what are inserted into the log when this feature is used are _not nicks_, they are abbreviations for nicks. [I've actually used this to map different nicks (the same person on different IM servers) to the same name when inserted into the log.] I'm not sure I totally understand. But what I mean by breaking completion is that I may see something like: hello when really your nick is snogglethorpe; I have just aliased it to miles. If I then cycle through nicks to reply to you, I find that miles isn't in the list. Maybe I should know this, since I know that miles is an abbrev, but now the tab completion of nicks is pretty much broken. If I reply to you on a busy channel as miles, it won't make any sense to anyone but me. As for whether I can "just change my nick", no I don't seem to be able to without actually changing my global IM name, and that is not something to be done lightly (i.e., I won't). Most IM clients seem to have this sort of "local name" feature (which changes the printed form of the name, but not the name used in more formal contexts) for exactly the same reason. Ihe IM translator I use with rcirc, Bitlbee, has a local rename feature, but (1) it doesn't seem to work on _my_ name, and (2) it apparently can't handle ambiguous names. That's true, you cant mess with your own nick on bitlbee once you have registered it. What about not showing your own nick at all? Just a copy of the prompt and the text you submitted as it is? hello > hi there Anyway, if you take it out, I'm going to have to add it back in my local copy, and patches like that are a pain to maintain, so I'd really rather you didn't; if you can think of some better method that will accomplish what I want, that would be great, of course... One possibility would be to make the "abbreviated" form have it's own format letter in rcirc-format-response-string; for instance, %n would print the real nick, and %a would print the abbreviated nick; this would at least allow a bit more control. I don't see how that really helps. For the nick abbrev stuff to actually do what you want, you would always want to see the abbreviated form, wouldn't you?