From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: rcirc changes Date: Thu, 16 Feb 2006 14:07:00 +0900 Message-ID: References: <87oe192men.fsf@cut.bc.hsia.telus.net> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1140066676 774 80.91.229.2 (16 Feb 2006 05:11:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 16 Feb 2006 05:11:16 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 16 06:11:15 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 1F9bQ4-00050C-ED for ged-emacs-devel@m.gmane.org; Thu, 16 Feb 2006 06:11:09 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F9bOA-0003Ua-PD for ged-emacs-devel@m.gmane.org; Thu, 16 Feb 2006 00:09:10 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F9bMg-0002dA-EI for emacs-devel@gnu.org; Thu, 16 Feb 2006 00:07:39 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F9bMd-0002Z3-Jd for emacs-devel@gnu.org; Thu, 16 Feb 2006 00:07:36 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F9bMb-0002XC-N6 for emacs-devel@gnu.org; Thu, 16 Feb 2006 00:07:34 -0500 Original-Received: from [64.233.182.202] (helo=nproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F9bRf-0000I4-5D for emacs-devel@gnu.org; Thu, 16 Feb 2006 00:12:47 -0500 Original-Received: by nproxy.gmail.com with SMTP id c29so49063nfb for ; Wed, 15 Feb 2006 21:07:32 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SjwYEmGx7B30BwJIm5hFm+gI8Szt7rkh4yuNmoYSys89e5HBcb+zdbIIx3BKALQRb9DWEosMwyCsOVva2ixQ2G1h5re5bi/jn72TqrC18F1ehkVX+QaYD2Kt+ONUeFpafy+dF3oBajcHHbaeK4JyfcOstwRmsZcKIMOinXr6CH4= Original-Received: by 10.49.21.16 with SMTP id y16mr90066nfi; Wed, 15 Feb 2006 21:07:00 -0800 (PST) Original-Received: by 10.48.237.13 with HTTP; Wed, 15 Feb 2006 21:07:00 -0800 (PST) Original-To: Ryan Yeske In-Reply-To: <87oe192men.fsf@cut.bc.hsia.telus.net> Content-Disposition: inline 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:50602 Archived-At: 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.] 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. 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. -Miles -- Do not taunt Happy Fun Ball.