From: Bastien <bzg@gnu.org>
To: Christopher Schmidt <christopher@ch.ristopher.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug in structmode++?
Date: Tue, 14 May 2013 10:59:37 +0200 [thread overview]
Message-ID: <87d2sulyp0.fsf@bzg.ath.cx> (raw)
In-Reply-To: <878v3qkghd@ch.ristopher.com> (Christopher Schmidt's message of "Tue, 7 May 2013 15:31:53 +0100 (BST)")
Hi Christopher,
Christopher Schmidt <christopher@ch.ristopher.com> writes:
> Most people use orgstruct{,++}-mode in message-mode, right? I think it
> makes sense to use vanilla org here. That is, make an indirect buffer
> of the message-mode buffer, narrow the buffer to the message body and
> set the major mode to org-mode.
Mhh.. This looks too complex to me.
My guess is that message-mode and mail-mode are the modes where
orgstruct-mode is the most used, so having it doing what the users
expect is important.
At least there should be no regression wrt the previous behavior
of orgstruct-mode.
> This should give one all the power of
> Org, including links, footnotes, font-lock and so on, without that
> orgstruct-mess.
I sympathetize with your blame on the mess... but still, let's fix
the code, not users' behavior :)
But things are fine for me at the moment, I'll report issues if I
find some.
Best,
--
Bastien
next prev parent reply other threads:[~2013-05-14 9:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 15:03 Bug in structmode++? Igor Sosa Mayor
2013-05-02 8:31 ` Igor Sosa Mayor
2013-05-02 8:33 ` Nicolas Goaziou
2013-05-02 8:51 ` Igor Sosa Mayor
2013-05-02 13:37 ` Nicolas Goaziou
2013-05-06 17:07 ` Christopher Schmidt
2013-05-07 10:16 ` Bastien
2013-05-07 12:28 ` Sebastien Vauban
2013-05-07 14:31 ` Christopher Schmidt
2013-05-14 8:59 ` Bastien [this message]
2013-05-14 11:16 ` Daniel Bausch
2013-05-12 14:10 ` The Dude
2013-05-12 14:59 ` Christopher Schmidt
2013-05-12 18:34 ` Igor Sosa Mayor
2013-05-23 6:29 ` The Dude
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=87d2sulyp0.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=christopher@ch.ristopher.com \
--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).