Gnus development mailing list
 help / color / mirror / Atom feed
From: Laura Conrad <lconrad@world.std.com>
Subject: Re: message-newline-and-reformat and supercite
Date: 06 Oct 1999 09:25:48 -0400	[thread overview]
Message-ID: <m3k8p0fwo3.fsf@serpent.local> (raw)
In-Reply-To: Vladimir Volovich's message of "06 Oct 1999 08:38:34 +0400"

>>>>> "Vladimir" == Vladimir Volovich <vvv@vvv.vsu.ru> writes:

       CC> Do you have a workaround ?

    Vladimir> the current message-newline-and-reformat in gnus 0.97
    Vladimir> behaves like you said. i already posted the corrected
    Vladimir> function. here is it again:
...
    Vladimir> does it work for you, or is *the above* function behaving buggy?

It seems to work some of the time, for instance, on the above,
correctly filled text, I can do:

<begin test 1>
    Vladimir> the current message-newline-and-reformat in gnus 0.97
    Vladimir> behaves like you said. 

Here I have inserted a break, and the next paragraph displays correctly.

    Vladimir> i already posted the corrected function. here is it
    Vladimir> again:
<end test 1>

However, if there are spaces at the ends of lines, the attributions
don't get removed:

<begin test 2>


    Vladimir> (defun message-newline-and-reformat ()
    Vladimir>   "Insert four newlines, and then reformat if inside quoted text."
    Vladimir>   (interactive)
    Vladimir>   (let ((point (point))

Here's where I inserted the break.

    Vladimir>   
    Vladimir> 	quoted) Vladimir> (save-excursion Vladimir>
    Vladimir> 	(beginning-of-line) Vladimir> (if (looking-at
    Vladimir> 	(sc-cite-regexp)) (setq quoted (buffer-substring
    Vladimir> 	(match-beginning 0) (match-end 0))))) Vladimir>
    Vladimir> 	(insert "\n\n\n\n") Vladimir> (delete-region (point)
    Vladimir> 	(re-search-forward "[ \t]*")) Vladimir> (when quoted
    Vladimir> 	Vladimir> (insert quoted)) Vladimir> (fill-paragraph
    Vladimir> 	nil) Vladimir> (goto-char point) Vladimir>
    Vladimir> 	(forward-line 2)))


<end test 2>

This is a bad example, since you wouldn't really want the lisp code
reformatted, but I frequently reply to correspondents who haven't
filled their lines any better than the lisp code did.

-- 
Laura (mailto:lconrad@world.std.com , http://www.world.std.com/~lconrad/ )
(617) 661-8097	fax: (801) 365-6574 
233 Broadway, Cambridge, MA 02139


  parent reply	other threads:[~1999-10-06 13:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-26 19:51 Vladimir Volovich
1999-10-04 22:41 ` François Pinard
1999-10-05  6:45   ` Vladimir Volovich
1999-10-05 18:50     ` Christophe Cuq
1999-10-05 20:25       ` David S. Goldberg
1999-10-05 21:22         ` Christophe Cuq
1999-10-06  4:38       ` Vladimir Volovich
1999-10-06  8:29         ` Kai Großjohann
1999-10-07  0:22           ` Francisco Solsona
1999-11-06  3:13             ` Lars Magne Ingebrigtsen
1999-10-06 13:25         ` Laura Conrad [this message]
1999-10-06 17:52           ` Vladimir Volovich
  -- strict thread matches above, loose matches on Subject: below --
1997-12-20 21:10 Michael R Cook
1998-01-04  9:29 ` Lars Magne Ingebrigtsen
1998-01-04 16:08   ` Wes Hardaker
1998-01-05  4:05     ` Lars Magne Ingebrigtsen
1998-01-05 10:21       ` Kai Grossjohann
1998-01-12 22:11         ` Lars Magne Ingebrigtsen

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=m3k8p0fwo3.fsf@serpent.local \
    --to=lconrad@world.std.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).