From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.help Subject: Re: vterm-module compile error Date: Sun, 1 Nov 2020 09:21:57 +0300 Message-ID: References: <87zh4cwjsp.fsf@zoho.eu> <20201024122320.GB25493@stw1.rcdrun.com> <87mu08o6it.fsf@zoho.eu> <878sbos9wc.fsf@zoho.eu> <87v9esqmrj.fsf@zoho.eu> <87r1pgql8l.fsf@zoho.eu> <87k0v6djzv.fsf@zoho.eu> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8030"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/+ (1036f0e) (2020-10-18) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Sun Nov 01 07:22:47 2020 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kZ6lJ-0001xe-4w for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 01 Nov 2020 07:22:45 +0100 Original-Received: from localhost ([::1]:38658 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kZ6lI-00068Q-6R for geh-help-gnu-emacs@m.gmane-mx.org; Sun, 01 Nov 2020 01:22:44 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:57854) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kZ6ke-00068B-A9 for help-gnu-emacs@gnu.org; Sun, 01 Nov 2020 01:22:04 -0500 Original-Received: from static.rcdrun.com ([95.85.24.50]:34349) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kZ6kc-0002Ge-7Z for help-gnu-emacs@gnu.org; Sun, 01 Nov 2020 01:22:03 -0500 Original-Received: from localhost ([::ffff:197.157.0.60]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by static.rcdrun.com with ESMTPSA id 00000000002A0B38.000000005F9E5407.00002418; Sun, 01 Nov 2020 06:21:59 +0000 Content-Disposition: inline In-Reply-To: <87k0v6djzv.fsf@zoho.eu> Received-SPF: pass client-ip=95.85.24.50; envelope-from=bugs@gnu.support; helo=static.rcdrun.com X-detected-operating-system: by eggs.gnu.org: First seen = 2020/11/01 01:59:45 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -3 X-Spam_score: -0.4 X-Spam_bar: / X-Spam_report: (-0.4 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:124842 Archived-At: * Emanuel Berg via Users list for the GNU Emacs text editor [2020-11-01 03:01]: > 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) ) It depends what you are familiar to. Please tell me why you disable C-n and C-p? In terminals including in built-in ansi-term or term it does the same command history functions. If you disable it, then for what use?