From: Russell Adams <RLAdams@adamsinfoserv.com>
Subject: Re: Regarding arbitrary Org blocks
Date: Wed, 11 May 2022 20:39:45 +0200 [thread overview]
Message-ID: <YnwC8XhVkv/MDzWa@tahm.private> (raw)
On Wed, May 11, 2022 at 09:23:27PM +0300, Daniel Fleischer wrote:
> Russell Adams [2022-05-11 Wed 18:14] wrote:
> > Could I add some minor mode to say text-mode with auto-fill-mode and
> > aspell somewhere when opening those blocks?
> Hi! If you're editing text why do you need a special buffer? You can
> edit them in the orgmode buffer and enjoy all its textual features.
First up, it's because it used to work and now it doesn't. ;]
Second it can be very useful to work on a sub-buffer, or indirect
buffer for some content. Why shouldn't I be able to edit the contents
of that block inside an indirect buffer where my beginning-of-buffer,
end-of-buffer, word wrap, or global find and replace are constrained
to that block of text?
This works for example blocks, but no longer for verse and quote
blocks. These are native Org block types and not my fanciful made up
ones. Why should the popup work for example blocks, but not the
others? That borders on a bug, where my question was considered as a
Finally when you edit in the popup buffer, the results are indented
which makes the document more legible. Regular text tools do that
> The special buffer is for major modes which are not orgmode such as
> programming languages or latex which use different
> completions/highlighting/minor-modes and editing them in orgmode is
> a hassle.
I think what I am using were once called "special blocks". You're
referring to source blocks. They have many more features but are
outside the question.
Russell Adams RLAdams@AdamsInfoServ.com
next prev parent reply other threads:[~2022-05-11 18:42 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 [this message]
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
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).