unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark Lillibridge <mark.lillibridge@hp.com>
To: <7743@debbugs.gnu.org>
Subject: bug#7743: closed (Re: bug#7743: unrmail loses extra blank line at end of message)
Date: Fri, 25 Nov 2011 22:06:05 -0800	[thread overview]
Message-ID: <qmh62i7ct9u.fsf@hp.com> (raw)
In-Reply-To: <handler.7743.D7743.132203471715779.notifdone@debbugs.gnu.org> (message from GNU bug Tracking System on Wed, 23 Nov 2011 07:52:02 +0000)


Glenn Morris writes:
>  Mark Lillibridge wrote:
>  
>  >>  So I cannot see that blank lines are going missing (unless going from
>  >>  Babyl to mbox adds one, and going the other way subtracts one?).
>  >
>  >     You got it!  Examine the BABYL file and you will see that Rmail 22.3
>  > has added an extra blank line after each of your messages.  That was a
>  > recent (pre transformation to 23) RMAIL bug, I believe.  My older email
>  > does not have these extra blank lines. 
>  
>  It sort of makes me wonder if it is worth changing this now, because if
>  most BABYL files started life as mbox files but were converted by Emacs,
>  then they have an extra blank line.

        The adding an extra line on incorporation is a recent bug; my
older BABYL files don't have the extra blank lines.

- Mark





      parent reply	other threads:[~2011-11-26  6:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27 19:54 bug#7743: unrmail loses extra blank line at end of message Mark Lillibridge
2011-11-13 19:59 ` bug#7743: bug #7743: unrmail loses extra blank line at end of message [PATCH] Mark Lillibridge
2011-11-16  7:52 ` bug#7743: unrmail loses extra blank line at end of message Glenn Morris
2011-11-19 20:28   ` Mark Lillibridge
2011-11-23  7:50     ` Glenn Morris
     [not found] ` <handler.7743.D7743.132203471715779.notifdone@debbugs.gnu.org>
2011-11-26  6:06   ` Mark Lillibridge [this message]

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=qmh62i7ct9u.fsf@hp.com \
    --to=mark.lillibridge@hp.com \
    --cc=7743@debbugs.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 public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).