Gnus development mailing list
 help / color / mirror / Atom feed
From: Thorsten Jolitz <tjolitz@gmail.com>
To: ding@gnus.org
Subject: Re: Org src-blocks not shown correctly
Date: Thu, 21 Aug 2014 20:20:40 +0200	[thread overview]
Message-ID: <8738cpwvpj.fsf@gmail.com> (raw)
In-Reply-To: <87sikq0zhc.fsf@ucl.ac.uk>

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Thursday, 21 Aug 2014 at 13:31, Thorsten Jolitz wrote:
>> Hi list, 
>>
>> since a few weeks I noticed that when I send Org src-blocks in a post
>> via gnus, the empty lines between them are lost when I open up my own
>> post in gnus later (while C-u g shows that the raw message does have
>> them).
>
> What does the following look like when you receive it from somebody
> else?
>
> #+BEGIN_SRC emacs-lisp
>   (+ 3 3)
> #+END_SRC
> #+BEGIN_SRC emacs-lisp
>   (- 2 2)
> #+END_SRC
>
> This is a much a question as a test so that I can see what happens in my
> case.

I see it like this, without the empty lines, and following up keeps that
state. But C-u g shows the empty lines between the blocks, and following
up from that raw message does quote it correctly too (with empty lines). 

-- 
cheers,
Thorsten




  parent reply	other threads:[~2014-08-21 18:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r40a9j0k.fsf@gmail.com>
2014-08-21 13:00 ` Eric S Fraga
2014-08-21 13:59   ` Jorge A. Alfaro-Murillo
2014-08-21 18:20   ` Thorsten Jolitz [this message]
2014-08-21 18:51     ` Eric S Fraga
2014-08-21 19:09       ` Thorsten Jolitz
2014-08-22  8:01         ` Eric S Fraga
2014-08-22  8:24           ` Eric Abrahamsen
2014-08-22  8:49             ` Thorsten Jolitz
2014-08-22 10:45             ` Eric S Fraga
2014-08-22  9:20           ` Thorsten Jolitz
2014-08-22 10:01           ` Katsumi Yamaoka

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=8738cpwvpj.fsf@gmail.com \
    --to=tjolitz@gmail.com \
    --cc=ding@gnus.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).