From: Russell Adams <RLAdams@adamsinfoserv.com>
Subject: Re: Regarding arbitrary Org blocks
Date: Thu, 12 May 2022 14:44:10 +0200 [thread overview]
Message-ID: <Yn0BGtc9kUemail@example.com> (raw)
On Thu, May 12, 2022 at 06:19:35PM +0800, Ihor Radchenko wrote:
> > Some recent change instead now says "No special environment to edit
> > here". How can I get back that behavior?
> I am unable to get the described behaviour even using Org 8.2.10. Could
> you elaborate what you mean by "used to"? Which Org version?
It's been quite some time. I've been using Org for years and I don't
keep it up to date. I can't identify when it changed, only that my
muscle memory started throwing errors. ;]
To be fair, I think I only moved to v9 this year. So I may have
learned this in versions before v8.
> > Could I add some minor mode to say text-mode with auto-fill-mode and
> > aspell somewhere when opening those blocks?
> Not currently, unless you advice org-edit-special. Though we might add
> something like org-edit-special-hook (similar to org-ctrl-c-ctrl-c-hook)
> if others are also interested in this functionality.
That's the kind of configuration I was referring to. It'd be fine to
me to add items to match the tags I use.
On the other hand, perhaps it would be useful to have a fallback
behavior to use the current org-mode settings in a popup buffer for a
block that has no mode associated with it?
Russell Adams RLAdams@AdamsInfoServ.com
prev parent reply other threads:[~2022-05-12 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 16:14 Regarding arbitrary Org blocks Russell Adams
2022-05-11 18:23 ` Daniel Fleischer
2022-05-11 18:39 ` Russell Adams
2022-05-11 19:06 ` Colin Baxter
2022-05-11 21:39 ` Greg Minshall
2022-05-11 23:06 ` Russell Adams
2022-05-12 10:19 ` Ihor Radchenko
2022-05-12 12:44 ` Russell Adams [this message]
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).