From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: RE: Keybinding that loops through Major Modes
Date: Tue, 3 Nov 2020 08:17:00 -0800 (PST) [thread overview]
Message-ID: <3530251f-8a97-45c6-807b-9ee0b051ee25@default> (raw)
In-Reply-To: <87v9emo9rq.fsf@web.de>
> > > A method that would be a bit cleaner in my eyes would be a command that
> > > lets you edit a specified region in a temp buffer in the correct mode.
> >
> > A narrowed, indirect buffer. (Basically the same idea, with a few things
> > automated.)
>
> AFAIK the problem with indirect buffers is that AFAIK font-lock isn't
> supported (unless you use the same mode and settings as the base
> buffer).
Correct. Indirect buffers only get you so far. Font
lock and other things are tied to the buffer. You can
change them in the indirect buffer AND the base buffer,
but you can't have them different between the two.
And current multiple-major-modes implementations also
only get you so far.
A flexible, robust implementation of multiple major
modes is a (big) feature that's really waiting for
some brilliant, dedicated, probably collaborative work
(IMHO). That grail would be welcomed by all.
___
Anyway, for using narrowed indirect buffers, I offer
library `narrow-indirect.el'.
Description:
https://www.emacswiki.org/emacs/NarrowIndirect
Code:
https://www.emacswiki.org/emacs/download/narrow-indirect.el
next prev parent reply other threads:[~2020-11-03 16:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 20:32 Keybinding that loops through Major Modes Christopher Dimech
2020-11-02 20:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-02 21:10 ` Christopher Dimech
2020-11-02 21:31 ` Vegard Vesterheim
2020-11-02 22:11 ` Christopher Dimech
2020-11-03 8:11 ` tomas
2020-11-03 8:49 ` Christopher Dimech
2020-11-03 9:44 ` Jean Louis
2020-11-03 11:27 ` Christopher Dimech
2020-11-03 12:19 ` Michael Heerdegen
2020-11-03 12:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-03 12:50 ` Michael Heerdegen
2020-11-03 14:19 ` Christopher Dimech
2020-11-03 13:09 ` Joost Kremers
2020-11-03 13:22 ` Michael Heerdegen
2020-11-03 14:35 ` Stefan Monnier
2020-11-03 14:52 ` Joost Kremers
2020-11-03 16:17 ` Drew Adams [this message]
2020-11-02 22:54 ` Christopher Dimech
2020-11-02 23:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-02 23:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-02 21:02 ` Stefan Monnier
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3530251f-8a97-45c6-807b-9ee0b051ee25@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
/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.
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).