unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tatsu Takamaro <tatsu.takamaro@gmail.com>
To: Robert Pluim <rpluim@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Remapping keys and creating my own keymap \\ too complicated\\
Date: Wed, 4 Dec 2024 19:37:11 +0300	[thread overview]
Message-ID: <48d40943-c50f-6cfe-21a5-b6ea8a9662c0@gmail.com> (raw)
In-Reply-To: <87plm7cu05.fsf@gmail.com>

Thank you! OK, so once again, am I right that if I just want to set my 
own key bindings (not changing all of them, but just some), then it's 
better to just use keymap-global-set (anticipated by 
keymap-global-unset)? And I may don't care about touching and changing 
the default settings?

And can I be sure that everything is all right when I change the global 
keymap, won't I be necessarily have to reinstall Emacs everytime I do 
something wrong (if I do...) with the global key assignment?

Is it just a matter of the ".emacs" file, and all wiil turn right if I 
just zeroize the ".emacs" settings?

And if so, I can just have my own settings inside of the ".emacs" file, 
and if I go to another computer I can just bring my ".emacs" file with 
me and it will work the way I want? And so it means I don't need a 
separate keymap file, do I?

ср, 04.12.2024 19:06, Robert Pluim пишет:
>>>>>> On Wed, 4 Dec 2024 18:55:00 +0300, Tatsu Takamaro<tatsu.takamaro@gmail.com>  said:
>      Tatsu> So, the concrete questions that bother me are as they were in the
>      Tatsu> original question. Like 1) Is my idea to create an own keymap the best
>      Tatsu> (or is it OK just to change the defaults)?, 2) What about the
>      Tatsu> differenced in the approach and the syntax matters, 3) What is the
>      Tatsu> correct way of creating my keymap. Sould it be inside of the ".emacs"
>      Tatsu> file or a separate one? What commands should I use?
>
> If you want to change global bindings, you can do that in the global
> map with eg `global-set-key' or `keymap-global-set' in more recent
> emacs. Iʼd use the latter, if possible, as the syntax of key sequences
> it uses is easier to write.
>
> Remember: your .emacs is yours, and changing defaults to suit you
> (including default bindings) is encouraged.
>
> Robert


  reply	other threads:[~2024-12-04 16:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 16:59 Remapping keys and creating my own keymap \\ too complicated\\ Tatsu Takamaro
2024-12-04  7:43 ` Jean Louis
2024-12-04 15:49   ` Tatsu Takamaro
2024-12-04 15:55   ` Tatsu Takamaro
2024-12-04 16:06     ` Robert Pluim
2024-12-04 16:37       ` Tatsu Takamaro [this message]
2024-12-04 16:40         ` Robert Pluim
2024-12-04 17:05           ` Tatsu Takamaro
2024-12-05 10:25             ` Robert Pluim
2024-12-05 18:08               ` Tatsu Takamaro
2024-12-06  9:57                 ` Robert Pluim
2024-12-06 10:38                   ` Jean Louis
2024-12-06 13:18                     ` Robert Pluim
2024-12-08 16:16                       ` Tatsu Takamaro
2024-12-08 23:07                         ` Stephen Berman
2024-12-09 22:34                           ` Tatsu Takamaro
2024-12-04 16:25 ` Jean Louis
2024-12-04 16:57   ` Tatsu Takamaro

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=48d40943-c50f-6cfe-21a5-b6ea8a9662c0@gmail.com \
    --to=tatsu.takamaro@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=rpluim@gmail.com \
    /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).