Gnus development mailing list
 help / color / mirror / Atom feed
From: Rui Zhu <sprache@iname.com>
Subject: Re: [patch] `M-Return' on quoted text failed when not using prefix `>'.
Date: 22 Apr 2000 02:07:30 +0200	[thread overview]
Message-ID: <23057.20621157$1042200931@news.gmane.org> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "20 Apr 2000 20:40:46 +0200"

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Rui Zhu <sprache@iname.com> writes:
> 
> > The problem is I'd like to use `> ' as quote prefix when composing
> > replies,

Sorry for the rant I've made.  In fact the patch is not well thought
out, think if I encounter such a prefix `> Super> ', sigh, not super any
more. ;-(

The point is that the code in `message-newline-and-reformat' seems to
presume the cited text *must* have prefix include char `>', because
`supercite-thing' must get matched.  But the situation is, I think,
supercite prefix can only occure one or zero time, and at the end of
prefix.  Or you mean `supercite-thing' can degenerate to normal prefix.

> Well, I think that's a problem, too, and the solution is to stop doing
> that. :-)

I've just thought `| ' looks good and tried to work out the troubles
it makes to me.  But now I thought a little more about it: It makes
troubles to others too, just like to myself.  The existence of the
convention is not without its reason.

#\Rui

-- 
Happy Gnusing!
Happy Easter!



  reply	other threads:[~2000-04-22  0:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87snxodv5o.fsf@.i-did-set--mail-host-address--so-not-shoot-me>
2000-04-20 18:40 ` Lars Magne Ingebrigtsen
2000-04-22  0:07   ` Rui Zhu [this message]
     [not found]   ` <87aein577h.fsf@.i-did-set--mail-host-address--so-not-shoot-me>
2000-04-22 12:15     ` Lars Magne Ingebrigtsen
2000-04-22 15:09       ` Kai Großjohann
2000-03-18 17:50 Rui Zhu

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='23057.20621157$1042200931@news.gmane.org' \
    --to=sprache@iname.com \
    /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.
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 NNTP newsgroup(s).