unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: tomas@tuxteam.de
Cc: help-gnu-emacs@gnu.org
Subject: Re: Keybinding that loops through Major Modes
Date: Tue, 3 Nov 2020 09:49:18 +0100	[thread overview]
Message-ID: <trinity-b029895a-c5a2-44b8-812b-05bd48e32182-1604393358670@3c-app-mailcom-bs09> (raw)
In-Reply-To: <20201103081105.GA17899@tuxteam.de>




> Sent: Tuesday, November 03, 2020 at 9:11 AM
> From: tomas@tuxteam.de
> To: help-gnu-emacs@gnu.org
> Subject: Re: Keybinding that loops through Major Modes
>
> On Mon, Nov 02, 2020 at 10:10:02PM +0100, Christopher Dimech wrote:
> > I shall explain better then.  In my .texi files I customarily include commands
> > from other modes or want to use some hooks from other modes (e.g. org-mode).
> > So even after I load a file with the default mode, I would need to quickly
> > shift to another mode temporarily, then switch back to normal-mode.
>
> Perhaps your problem becomes different [0] if you squint at it from
> another angle (space vs time): do you really want your whole buffer
> to "switch mode", or are you looking after some regions "having a
> different mode"?

That's what I had in mind, for the whole buffer

> In the second case, look, e.g. for "multiple major modes" [1]. It's
> a class of problems for which need exists (e.g. Org source snippets,
> but also those PHP cum HTML cum Javascript thingies.

Indeed.  Customarily I would need to change mode on just a portion of the
code I would be working with.

>
> Cheers
>
> [0] Not necessarily better, but perhaps exciting in a different
>    way?
> [1] https://www.emacswiki.org/emacs/MultipleModes
>
>  - t
>



  reply	other threads:[~2020-11-03  8:49 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 [this message]
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
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=trinity-b029895a-c5a2-44b8-812b-05bd48e32182-1604393358670@3c-app-mailcom-bs09 \
    --to=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=tomas@tuxteam.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).