all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: bkhl@elektrubadur.se (Björn Lindström)
To: emacs-devel@gnu.org
Subject: Re: rcirc multiline nick adding
Date: Thu, 19 Apr 2007 02:56:16 +0200	[thread overview]
Message-ID: <87bqhlgp1r.fsf@bast.dreaming> (raw)
In-Reply-To: 87647try7q.fsf@kanga.tapsellferrier.co.uk

Nic James Ferrier <nferrier@tapsellferrier.co.uk>:

> Miles Bader <miles@gnu.org> writes:
>
>> Nic James Ferrier <nferrier@tapsellferrier.co.uk> writes:
>>> +  ;; Is there a nick at the start of the multiline buffer? if so add it to all the lines
>>> +  (goto-char (point-min))
>>> +  (if (looking-at "^[^ :]+: ")
>>> +      (let ((nick (match-string 0)))
>>> +        (while (re-search-forward "\n" nil t)
>>> +          (replace-match (concat "\n" nick)))))
>>
>> This seems dangerous; what if it's not a nick?  It seems quite likely to
>> have annoying results...
>
> Well... with me it always is a nick. And it's vital that it be put
> in.
>
> Sending multilines through bitlebee without it is tricky.
>
> Not sure there's another way to tell it if is a nick or not which is
> partly why I pasted it here; maybe someone will have an idea.

How about instead of doing this automagically, make this a text
editing command for multiline mode?

I.e. pressing C-c something inserts a nick followed by colon on each line.

  reply	other threads:[~2007-04-19  0:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-18 12:55 rcirc multiline nick adding Nic James Ferrier
2007-04-19  0:31 ` Miles Bader
2007-04-19  0:42   ` Nic James Ferrier
2007-04-19  0:56     ` Björn Lindström [this message]
2007-04-19  1:16       ` Nic James Ferrier
2007-04-19  5:19     ` Miles Bader
2007-04-19  2:38 ` Richard Stallman
2007-04-19  8:06   ` Nic James Ferrier
2007-04-19 23:17     ` Richard Stallman
2007-04-19 23:35       ` Nic James Ferrier
  -- strict thread matches above, loose matches on Subject: below --
2007-04-21  3:07 Ryan Yeske
2007-04-21 18:25 ` Richard Stallman
2007-04-22  5:23   ` Ryan Yeske
2007-04-22  9:10     ` Nic James Ferrier
2007-04-23  3:47     ` Richard Stallman

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

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

  git send-email \
    --in-reply-to=87bqhlgp1r.fsf@bast.dreaming \
    --to=bkhl@elektrubadur.se \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.