From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: org-element-at-point fails in programming-modes
Date: Thu, 21 Aug 2014 22:03:31 +0200 [thread overview]
Message-ID: <878umhvcdo.fsf@gmx.us> (raw)
In-Reply-To: 87vbpn9x6u.fsf@gmail.com
Hi Thorsten,
Thorsten Jolitz <tjolitz@gmail.com> writes:
> As a side-remark, I did send these blocks with emptly lines between them,
> and when I look at my post in gmane the format looks alright, however
> when I open it in gnus the empty lines are gone and it looks like this:
Do you by any chance have `gnus-article-strip-all-blank-lines' (W E A
from summary) in your `gnus-article-mode-hook' or, more dangerously,
in your `nnmail-prepare-incoming-hook'?
I have had terrible things happen when I applied "washing"
automatically.
(info "(gnus) article washing")
—Rasmus
--
This space is left intentionally blank
next prev parent reply other threads:[~2014-08-21 20:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-20 12:00 org-element-at-point fails in programming-modes Thorsten Jolitz
2014-08-20 12:12 ` Thorsten Jolitz
2014-08-20 12:17 ` Nick Dokos
2014-08-20 12:39 ` Sebastien Vauban
2014-08-20 14:28 ` Nick Dokos
2014-08-22 4:02 ` Nick Dokos
2014-08-22 5:22 ` Nicolas Richard
2014-08-22 13:23 ` Nick Dokos
2014-08-22 10:28 ` Thorsten Jolitz
2014-08-22 13:46 ` Nick Dokos
2014-08-22 13:53 ` Nicolas Richard
2014-08-22 14:20 ` Nicolas Richard
2014-08-22 14:26 ` Article Mode eats newlines between src-blocks (was Re: org-element-at-point fails in programming-modes) Thorsten Jolitz
2014-08-22 14:46 ` org-element-at-point fails in programming-modes Nick Dokos
2014-08-22 17:07 ` Rasmus
2014-08-20 12:41 ` Nicolas Richard
2014-08-21 20:03 ` Rasmus [this message]
2014-08-21 20:13 ` Rasmus
2014-08-21 20:35 ` Thorsten Jolitz
2014-08-21 20:49 ` Rasmus
2014-08-20 12:40 ` Nicolas Richard
2014-08-20 13:52 ` Thorsten Jolitz
2014-08-21 8:58 ` Nicolas Goaziou
2014-08-21 11:22 ` Thorsten Jolitz
2014-08-22 13:47 ` Bastien
2014-09-23 10:29 ` Thorsten Jolitz
2014-09-23 21:27 ` Nicolas Goaziou
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878umhvcdo.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@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/org-mode.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).