Re: [PATCH] message-elide-region.

[Matthieu Moy <Matthieu.Moy@imag.fr>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Matthieu Moy <Matthieu.Moy@imag.fr> writes:
>
>> it works when the region is a set of full lines, but if I call it with
>> regions [...] in the middle of a line, everything goes wrong:
>
> As you can see, it works for me.  (I also elided "beginning".)  But I
> have (setq message-elide-ellipsis "[...]").  Does that make a
> difference? 

Yes, and unfortunately, your example break my code :-(

The   old   message-elide-region    kills   the   region,   and   puts
message-elide-ellipsis instead. It doesn't  take any care of citation,
which   is   very   enoying   when   message-elide-ellipsis   contains
"\n"'s. (which is the default)

My  modification  was  to  add  (message-newline-and-reformat),  which
breaks a cited line properly. 

OK, lets try an improved version :

(defun message-elide-region (b e)
  "Elide the text in the region.
An ellipsis (from `message-elide-ellipsis') will be inserted where the
text was killed."
  (interactive "r")
  (kill-region b e)
  (if (string-match "\n.*\n" message-elide-ellipsis)
      (progn
	(message-newline-and-reformat)
	(delete-region
	 (progn (previous-line 1) (point))
	 (progn (next-line 3) (point))))
    )
  (insert message-elide-ellipsis))

This tests wether message-elide-ellipsis  begins and ends by "\n", and
do what it has to do then.

-- 
Matthieu