unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Jean Louis <bugs@gnu.support>
To: help-gnu-emacs@gnu.org
Subject: Re: vterm-module compile error
Date: Sun, 1 Nov 2020 16:17:21 +0300	[thread overview]
Message-ID: <X561YXkeyyhmdtAU@protected.rcdrun.com> (raw)
In-Reply-To: <87blghxm4c.fsf@zoho.eu>

* Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> [2020-11-01 16:07]:
> > When I am in Xterm or if I am on console, C-n and C-p are in Emacs
> > bindings for shell like cursor up and down and those are normally
> > askin for previous or next history items. That is what I expect
> > when I am on M-x term or M-x vterm or M-x ansi-term as those are
> > terminal emulators.
> 
> Well, yes, but then we expect different. I want all the basic cursor
> movements commands to be the same everywhere. Doesn't matter if it is
> vterm, King Khan, or King Kong. I like basic input to be consistent,
> doesn't matter if it is ERC, Gnus, programming, whatever.

I would like to have M-x in Emacs terminal M-x term or M-x ansi-term

(define-key term-mode-map (kbd "M-x") 'execute-extended-command)

is not working. How do you suggest to change it for M-x term?










  reply	other threads:[~2020-11-01 13:17 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
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 [this message]
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=X561YXkeyyhmdtAU@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=help-gnu-emacs@gnu.org \
    /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).