unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ryan Yeske <rcyeske@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: rcirc changes
Date: Thu, 16 Feb 2006 08:30:57 -0800	[thread overview]
Message-ID: <87k6bv2rlq.fsf@cut.bc.hsia.telus.net> (raw)
In-Reply-To: <fc339e4a0602152107m4e17f443naf95738339268749@mail.gmail.com> (message from Miles Bader on Thu, 16 Feb 2006 14:07:00 +0900)

   Date: Thu, 16 Feb 2006 14:07:00 +0900
   From: Miles Bader <miles@gnu.org>
   Sender: snogglethorpe@gmail.com
   Cc: emacs-devel@gnu.org
   Content-Disposition: inline

   On 2/15/06, Ryan Yeske <rcyeske@gmail.com> 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:

<miles> 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?

<miles> 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?

  reply	other threads:[~2006-02-16 16:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-09 12:07 rcirc changes Miles Bader
2006-02-11 17:54 ` Ryan Yeske
2006-02-12  1:03   ` Miles Bader
2006-02-15  5:58 ` Ryan Yeske
2006-02-16  4:40   ` Richard M. Stallman
2006-02-16  5:07   ` Miles Bader
2006-02-16 16:30     ` Ryan Yeske [this message]
2006-02-16 20:56       ` Miles Bader
2006-02-17 12:56         ` Björn Lindström
2006-02-18  6:38           ` Miles Bader
2006-02-18 22:18             ` David Kastrup
2006-02-19  0:44               ` Miles Bader
2006-02-18 17:36         ` Alex Schroeder
  -- strict thread matches above, loose matches on Subject: below --
2006-02-15  6:28 Ryan Yeske
2006-09-12 15:27 Richard Stallman
2006-09-12 16:51 ` Chong Yidong
2006-09-12 21:50   ` Ryan Yeske
2006-09-12 22:08     ` Chong Yidong

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=87k6bv2rlq.fsf@cut.bc.hsia.telus.net \
    --to=rcyeske@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).