Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: "B. T. Raven" <ecinmn@alcisp.com>
To: info-gnus-english@gnu.org
Subject: Re: quoted text prefix(es)
Date: Sat, 24 Feb 2007 12:58:26 -0600	[thread overview]
Message-ID: <ce906$45e08ae4$49f20a9$21430@DIALUPUSA.NET> (raw)
In-Reply-To: <y687iu88zx7.fsf@contents-vnder-pressvre.mit.edu>

Thanks David. Supercite does too much for me. Since the very format of
your response (below) demonstrates the impracticality of my idea, what I
want now is what you suggest, but implemented automatically, something
like (strip-deep-cites n) where n is, say, the maximum number of
allowable > characters prefixed to a line. Then all groups of lines with a
greater number of > characters  would be collapsed to the sequence C-j
[...] C-j C-j. Do you know of something similar to that already
implemented in elisp. Unfortunately, however, most of supercite.el is over
my head.


"David Z Maze" <dmaze@mit.edu> wrote in message
news:y687iu88zx7.fsf@contents-vnder-pressvre.mit.edu...
> "B. T. Raven" <ecinmn@alcisp.com> writes:
>
> > Is there a way to replace the stacks of right pointing arrows prefixed
to
> > quoted text in gnus or rmail with an abbreviation?
> > E.g.:
> >>
> >>>
> > 3>
> > 4>
> > ...
>
> Honestly, best practice if you've got quoting that deep is to remove
> some of the really old stuff and just keep the past couple of replies'
> worth of context.  My experience from using Supercite long ago is that
> using non-standard quote characters makes it harder for other people
> to read and reply correctly, the ">>>>" format is sufficiently
> widespread that almost everyone can understand it and generate it
> (assuming their mailer is functional).
>
> > This would prevent text with many levels of nested quotations from
pushing
> > text so far rightward that it is forced to wrap prematurely.
>
> The usual M-q Emacs line-wrapping works fine for quoted text.
>
> > It seems that
> > it should be possible to convert to this format even email sent by a
> > non-conforming program:
> >
> > E.g.
> >
> >>4> is converted to 5>
> >>>6> .....  8>
>
> In principle this should be pretty straightforward with some Lisp and
> some regexp matching, but see e.g. `gnus-supercite-regexp' to see just
> how hairy the regular-expression matching can get.
>
>   --dzm

  reply	other threads:[~2007-02-24 18:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 17:19 B. T. Raven
2007-02-23 18:57 ` David Z Maze
2007-02-24 18:58   ` B. T. Raven [this message]
2007-02-23 21:47 ` Phil Jackson
2007-02-24  4:45   ` Daniel Brockman

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='ce906$45e08ae4$49f20a9$21430@DIALUPUSA.NET' \
    --to=ecinmn@alcisp.com \
    --cc=info-gnus-english@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.
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).