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: vterm-module compile error
Date: Sun, 01 Nov 2020 01:00:04 +0100 [thread overview]
Message-ID: <87k0v6djzv.fsf@zoho.eu> (raw)
In-Reply-To: X5vXIp363isi2FXt@protected.rcdrun.com
Jean Louis wrote:
>>>> But vterm has one weird thing that really bugs me... the
>>>> vterm-mode-map instantly and fully takes over your entire
>>>> keyboard! C-p is `previous-line', right? Wrong! Here it is
>>>> `vterm-send-C-p', and that does something else!
>>>
>>> [...]
>>>
>>> Of course it is customizable.
>>
>> Can I have a vterm-can-I-have-my-keys-back-please please?
>
> C-p and C-n do history back and forth in M-x term and also in M-x
> vterm
That's a problem! And here is the (one) solution...
Check out the emacs-init directory for the other stuff if it fancies
you, otherwise just use the loop to get everyday Emacs keys back.
I think I'll be adding a couple of more to that list before I'm happy
with vterm.
;;; -*- lexical-binding: t -*-
;;;
;;; this file:
;;; http://user.it.uu.se/~embe8573/emacs-init/term.el
;;; https://dataswamp.org/~incal/emacs-init/term.el
(require 'super)
(require 'switch-to-buffer-regexp)
(require 'vterm)
(defun use-vterm (new)
(interactive "P")
(when (or new (not (switch-to-buffer-regexp "vterm")))
(vterm) ))
(defalias 'vt #'use-vterm)
(let ((the-map vterm-mode-map)
(keys '(
"\C-a"
"\C-e"
"\C-n"
"\C-p"
)))
(disable-super-global-keys the-map)
(dolist (k keys)
(define-key the-map k nil) )
(define-key the-map "\C-\M-p" #'vterm-send-C-p)
(define-key the-map "\C-\M-n" #'vterm-send-C-n) )
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2020-11-01 0:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 0:26 vterm-module compile error Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-24 12:23 ` Jean Louis
2020-10-24 12:34 ` Tassilo Horn
2020-10-24 13:11 ` Jean Louis
2020-10-27 0:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-30 2:52 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-30 5:57 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-30 6:11 ` Jean Louis
2020-10-30 6:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-30 9:04 ` Jean Louis
2020-11-01 0:00 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2020-11-01 0:07 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 6:21 ` Jean Louis
2020-11-01 11:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 12:43 ` Jean Louis
2020-11-01 13:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 13:17 ` Jean Louis
2020-11-01 13:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 15:38 ` Jean Louis
2020-11-01 16:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 16:24 ` Jean Louis
2020-11-01 18:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-11-01 21:45 ` Jean Louis
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=87k0v6djzv.fsf@zoho.eu \
--to=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).