From: Christopher Dimech <dimech@gmx.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Joost Kremers <joostkremers@fastmail.fm>, help-gnu-emacs@gnu.org
Subject: Re: RE: Same file on two buffers - Two different major modes
Date: Wed, 4 Nov 2020 22:47:49 +0100 [thread overview]
Message-ID: <trinity-64423e49-654d-48a9-bef5-66cac6722d6a-1604526469596@3c-app-mailcom-bs01> (raw)
In-Reply-To: <fbfa55b4-9888-41d0-b1b4-9f16687c0420@default>
For instance, I have source code with org-mode and rec-wode
commands. Thus while I am working on the source code I could
be navigating the same file in org-mode.
> Sent: Wednesday, November 04, 2020 at 10:40 PM
> From: "Drew Adams" <drew.adams@oracle.com>
> To: "Christopher Dimech" <dimech@gmx.com>, "Joost Kremers" <joostkremers@fastmail.fm>
> Cc: help-gnu-emacs@gnu.org
> Subject: RE: Same file on two buffers - Two different major modes
>
> > The principal idea is to have the same buffer next to each other,
> > where one can change the major mode on each buffer, but saves
> > to the save buffer.
>
> OK, that's "the principal idea", but I don't understand the
> use case. Could you say why you want to see the same buffer
> in two windows, but in a different mode in each window?
>
> What is it you are really trying to do? That might help
> understanding.
>
>
next prev parent reply other threads:[~2020-11-04 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 11:37 Same file on two buffers - Two different major modes Christopher Dimech
2020-11-04 11:52 ` Philipp Stephani
2020-11-04 11:57 ` tomas
2020-11-04 11:55 ` tomas
2020-11-04 12:08 ` Joost Kremers
2020-11-04 12:30 ` Christopher Dimech
2020-11-04 21:40 ` Drew Adams
2020-11-04 21:47 ` Christopher Dimech [this message]
2020-11-04 22:16 ` Drew Adams
2020-11-05 0:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-04 12:30 ` Jean Louis
2020-11-04 21:18 ` Marcin Borkowski
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=trinity-64423e49-654d-48a9-bef5-66cac6722d6a-1604526469596@3c-app-mailcom-bs01 \
--to=dimech@gmx.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=joostkremers@fastmail.fm \
/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).