From: Eric Fraga <firstname.lastname@example.org>
To: Bastien <email@example.com>
Subject: Re: orgstuct++ does not lurk silently in the shadow
Date: Sun, 29 Apr 2012 16:10:33 +0930 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Bastien's message of "Thu, 26 Apr 2012 12:42:57 +0200")
Bastien <firstname.lastname@example.org> writes:
> Hi Eric,
> Eric Fraga <email@example.com> writes:
>> Thanks for this. This behaviour has annoyed me for years now.
> Me too...
>> never gotten around to figuring out why I got this behaviour because I
>> get caught up with writing the email and forget by the time I finish...
>> I hope somebody can indeed fix this as it sounds quite straightforward
>> (for better elisp programmers than I...).
> This should be fixed now in master.
> Can you confirm?
> There is one remaining use-case I didn't fix: the case where you use M-q
> on the first line of the message (things are messed up then.) I don't
> know how to fix this, but this is a rather border-line case, as simply
> typing and using auto-fill does the right thing.
> Thanks for insisting on this!
Filling seems to work much better now but I don't know whether any of
this is org or gnus. However, I am not sure what is happening
here. With the following line in my configuration:
(add-hook 'message-setup-hook 'turn-on-orgstruct++)
all my emails end up indented strangely. Specifically, if this email
had been composed with that hook entry, all my lines would have been
indented 2 spaces. See my previous message to this list if you can find
I commented out that line in my configuration and restarted Emacs to
compose this reply. No indenting is happening (which is a good thing).
Very strange. I do not understand why turning on orgstuct++ would cause
a default indentation of all text.
I am happy to explore this further if you give me some hint as to what
I am using gnus and org up to date as of yesterday (Australia time). I
haven't updated today yet.
: Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D) in Emacs 22.214.171.124
: using Org release_7.8.09-414-gb3e8a8
next prev parent reply other threads:[~2012-04-29 6:40 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 7:08 orgstuct++ does not lurk silently in the shadow Christopher Schmidt
2012-03-08 13:38 ` orgstruct++ does not lurk silently in the shadow (was: orgstuct++ does not lurk silently in the shadow) Christopher Schmidt
2012-04-25 7:44 ` orgstuct++ does not lurk silently in the shadow Eric Fraga
2012-04-26 10:42 ` Bastien
2012-04-29 6:40 ` Eric Fraga [this message]
2012-04-29 6:48 ` Eric Fraga
2012-04-29 8:38 ` Bastien
2012-04-29 11:05 ` Christopher Schmidt
2012-04-29 12:27 ` Christopher Schmidt
2012-05-01 17:43 ` Bastien
2012-05-03 9:56 ` Eric Fraga
2012-05-03 12:28 ` Bastien
2012-05-03 12:58 ` Nicolas Goaziou
2012-05-03 13:12 ` Bastien
2012-05-03 13:17 ` Nicolas Goaziou
2012-05-03 13:45 ` Bastien
2012-05-03 15:53 ` Nicolas Goaziou
2012-05-05 13:46 ` Bastien
2012-05-05 15:51 ` Nicolas Goaziou
2012-05-05 16:18 ` Bastien
2012-05-05 16:19 ` Nicolas Goaziou
2012-05-05 16:22 ` Bastien
2012-05-05 16:30 ` Nicolas Goaziou
2012-05-06 8:07 ` Bastien
2012-05-06 14:09 ` Eric Fraga
2012-05-06 14:27 ` Thorsten Jolitz
2012-05-06 15:47 ` Bastien
2012-05-07 4:23 ` Eric S Fraga
2012-05-08 12:31 ` Bastien
2012-05-08 23:54 ` Eric S Fraga
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).