From: Christopher Dimech <dimech@gmx.com>
To: moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org
Subject: Re: Keybinding that loops through Major Modes
Date: Mon, 2 Nov 2020 22:10:02 +0100 [thread overview]
Message-ID: <trinity-4b4b9c3f-cf12-47cf-9a3a-3c232a760654-1604351402619@3c-app-mailcom-bs09> (raw)
In-Reply-To: <87eelb1nmc.fsf@zoho.eu>
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.
> Sent: Monday, November 02, 2020 at 9:59 PM
> From: "Emanuel Berg via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> To: help-gnu-emacs@gnu.org
> Subject: Re: Keybinding that loops through Major Modes
>
> Christopher Dimech wrote:
>
> > Is it difficult to make an keybinding that if I continue to press
> > it, it will loop through a list of major modes in a predefined
> > order (e.g. text-mode, org-mode, normal-mode, text-mode, ...)
>
> Not difficult but perhaps not a good idea since it is probably better
> to let Emacs set the major mode automatically.
>
> If it doesn't do it to your liking there are many ways to set it up,
> depending on the situation.
>
> Based on file extension:
>
> (let ((modes (list
> '("\\.bal\\'" . balance-mode)
> '("\\.lu\\'" . lua-mode)
> '("\\.nqp\\'" . perl-mode)
> '("\\.php\\'" . html-mode)
> '("\\.pic\\'" . nroff-mode)
> '("\\.pl\\'" . prolog-mode)
> '("\\.tex\\'" . latex-mode)
> '("\\.xr\\'" . conf-xdefaults-mode)
> '("*" . text-mode) )))
> (setf auto-mode-alist (nconc modes auto-mode-alist)) )
>
> For scripts, use the hash-bang line, topmost. You probably want it
> anyway. For example, for zsh:
>
> #! /bin/zsh
>
> You can also force a mode like this, also topmost:
>
> ;;; -*- emacs-lisp -*-
>
> For the rare cases none of these methods will do, I think M-x
> perl-mode RET will do...
>
> --
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
>
>
>
next prev parent reply other threads:[~2020-11-02 21:10 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 [this message]
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
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-4b4b9c3f-cf12-47cf-9a3a-3c232a760654-1604351402619@3c-app-mailcom-bs09 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).