From: Christopher Dimech <dimech@gmx.com>
To: Vegard Vesterheim <vegard.vesterheim@uninett.no>
Cc: help-gnu-emacs@gnu.org, moasenwood@zoho.eu
Subject: Re: Keybinding that loops through Major Modes
Date: Mon, 2 Nov 2020 23:11:57 +0100 [thread overview]
Message-ID: <trinity-03dfb89d-fb4e-4f4b-b0f4-c4bf041b8b3c-1604355117911@3c-app-mailcom-bs09> (raw)
In-Reply-To: <877dr3h2e6.fsf@uninett.no>
Have used Org Babel before. My situation is more complicated
because I use Org Commands in Source Files as well. To add
further complication, I also add rec commands that can be parsed
by Gnu Recutils, which is useful to we because I can compute some
metrics for my code, such as the Cyclomatic Complexity of each
function.
> Sent: Monday, November 02, 2020 at 10:31 PM
> From: "Vegard Vesterheim" <vegard.vesterheim@uninett.no>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: moasenwood@zoho.eu, help-gnu-emacs@gnu.org
> Subject: Re: Keybinding that loops through Major Modes
>
> On Mon, 2 Nov 2020 22:10:02 +0100 Christopher Dimech <dimech@gmx.com> 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.
>
> I realize this is not an answer to your original question. But have you
> considered writing your file in org-mode? Org-mode can export to
> several formats, also texi.
>
> Org-mode has this thing called babel
> (https://orgmode.org/worg/org-contrib/babel/) which allows you to embed
> (and even execute) blocks of code in your document.
>
> From the manual
> (https://orgmode.org/manual/Editing-Source-Code.html#Editing-Source-Code):
>
> Use C-c ' to edit the current code block. It opens a new major mode edit
> buffer containing the body of the source code block, ready for any edits.
>
> --
> Vennlig hilsen/Best regards
> Vegard Vesterheim
> Senior Software engineer
> +47 48 11 98 98
> vegard.vesterheim@uninett.no
>
next prev parent reply other threads:[~2020-11-02 22:11 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 [this message]
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-03dfb89d-fb4e-4f4b-b0f4-c4bf041b8b3c-1604355117911@3c-app-mailcom-bs09 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
--cc=vegard.vesterheim@uninett.no \
/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).