unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
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: Tue, 3 Nov 2020 15:19:18 +0100	[thread overview]
Message-ID: <trinity-3914d209-1cf3-406e-85df-1d031439c511-1604413158951@3c-app-mailcom-bs09> (raw)
In-Reply-To: <87sg9qzkrj.fsf@zoho.eu>



> Sent: Tuesday, November 03, 2020 at 1:29 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
>
> Michael Heerdegen wrote:
>
> >> The major power would not be the highlighting itself, but the
> >> operations associated with the mode.
> >
> > 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.
>
> The best method:
>
> - several files
>
> - one file, one mode
>
> - the "associated operations" belonging to one mode can easily enough
>   be made generic if indeed correct they are useful for another mode


In principle you are correct.  However, if one uses ogg and rec you want
those features available some of the time, because if the file is a fortran
file, I would be mainly working in fortran mode.  Some modes are very rich
and not completely applicable to code.

>
> BOOM
>
> --
> underground experts united
> http://user.it.uu.se/~embe8573
> https://dataswamp.org/~incal
>
>
>



  parent reply	other threads:[~2020-11-03 14:19 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 [this message]
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-3914d209-1cf3-406e-85df-1d031439c511-1604413158951@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).