Hi Drew, I am very thankful for Your detailed description. Those are my first steps in Emacs and I am very pleased for your help. I am learning day by day. It's still difficult for me to get into this programming language, I am not used to it. I have a completely different job and just this year I installed "Guix OS" on my laptop with the great help of all the Guixers, and everyone was so happy with Emacs that all of them encouraged me to learn Emacs. So I decided to give it a try. It is hard to get into it, because I am not sitting the whole day in front of my laptop, but I am doing a technical job. So I managed according to your description to customize the kc-auto-delay I was already reading your keysee.el and sortie.el file twice, but I still have to read it, every time I want to do something. So slowly I understand more and more how it works. So You did a great job in helping me (and others) and also Your contributions to Emacs. I found out that You made several other packages too like highlight.el and icycles I will deal with them later, first I want to continue reading the manual. Thanks a lot for Your patience and help sincere regards Gottfried Am 14.12.22 um 19:07 schrieb Drew Adams: >> "You can customize the delay with option `kc-auto-delay'. >> but I don't know how can I do it. >> Do I have to write "kc-auto-delay" in my init.el file? > > M-x customize-option RET kc-auto-delay RET > > Use the Customize UI to edit the value, and set-and-save it. > > By default, Customize will write the setting to your init file, as code you should not modify (it adds a comment saying that). > > But it is much better to set variable `custom-file' in your init file to some other file (e.g. a new file, initially empty). Then, also in your init file, explicitly load that file, using function `load-file'. > > Defining and loading a separate `custom-file' makes Customize write your settings that it manages to that file, instead of your init file, so you don't mix generated code with your hand-written code. > > (load-file "/SOME/DIRECTORY/SOMEWHERE/my-custom-file.el") > > Or you can put the file in a directory that's in your `load-path', and use: > > (load-library "my-custom-file") > > All such info is in the Emacs manual. You should read that yourself: `C-h r' to read the manual in Emacs. `C-h i' and read the Info file, to learn how to use Info (read manuals with Emacs). > > In a manual `i' to access an index entry. E.g., in the Emacs manual `i custom-file' takes you to node `Saving Customizations, which is here in HTML: > > https://www.gnu.org/software/emacs/manual/html_node/emacs/Saving-Customizations.html > >> And is there also an option additionally to use this in the menu bar. >> Or is it only possible to do this instead of the other? >> >> If you want to complete just menu-bar menus, you can use command >> `kc-complete-menu-bar'. > > The point of that sentence is to say there is a command that _only_ shows you menu-bar commands (keys). You can bind that command to a key for quick access. > > But you don't _need_ to do that, to access the menu-bar commands. Accessing menu-bar menus and their items is already available by doing nothing. > > When you use `kc-auto-mode', for example, `S-TAB' shows you this prefix key: `menu-bar = ...' > > Choose that to descend into the menu-bar menu > (e.g. type "menu-bar ", to match that completion > candidate). > > You can then choose another menu prefix key, e.g. > `Buffers = ...' (just type `bu TAB`), to descend > into that menu. And so on. > > Choose a non-prefix-key candidate, such as > `Select Named Buffer... = switch-to-buffer', to > invoke that key/command (just type `select TAB'). > > (To show prefix keys first in the candidate sort > order, use `C-,'.) > > Please read the Commentary in files keysee.el and > sortie.el, for more help. > > - Drew > >