emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Russell Adams <RLAdams@adamsinfoserv.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Regarding arbitrary Org blocks
Date: Thu, 12 May 2022 18:19:35 +0800	[thread overview]
Message-ID: <874k1vhx3c.fsf@localhost> (raw)
In-Reply-To: <Ynvg/SkJztAW7EWL@tahm.private>

Russell Adams <RLAdams@adamsinfoserv.com> writes:

> I used to insert arbitrary blocks like:
>
> #+BEGIN_IMPORTANT
> yadda yadda
> #+END_IMPORTANT
>
> in my documents, and when I hit C-c ' to edit them it would give me a
> basic buffer and I could edit the plain text within.
>
> 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?

> I'm really just editing text blocks for Latex export, and the source
> block type triggers some latex formatting. It's not source code
> language, just plain text.
>
> 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.

Best,
Ihor



  parent reply	other threads:[~2022-05-12 10:29 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 [this message]
2022-05-12 12:44   ` Russell Adams

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=874k1vhx3c.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=RLAdams@adamsinfoserv.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).