Timeline for How can I see what Major and Minor modes I'm currently in?
Current License: CC BY-SA 4.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 27, 2020 at 5:26 | comment | added | phils | n.b. It's probably best not to clobber the primary "help" key binding in your Emacs config (or indeed for any application), if you're liable to forget that you've done it. However, if you're determined to keep your custom C-h binding, then try using <f1> in its place. Assuming you haven't also clobbered that, you can just mentally substitute that for C-h when you see those key sequences. | |
| Jun 26, 2020 at 22:16 | comment | added | NickD | @db48x I think you should add the previous comment to your answer. | |
| Jun 26, 2020 at 20:18 | history | edited | NickD | CC BY-SA 4.0 | Spell out the command that `C-h m` is usually bound to. |
| Jun 26, 2020 at 19:09 | comment | added | db48x | It sounds like you'll also want to know about describe-key and describe-function. describe-key lets you type in a key sequence, and it tells you what command that sequence will run. describe-function prompts for a function name and gives you the documentation of that function, as well as what keys it is bound to. In this case you could run M-x describe-function describe-function to get the help for describe-function as well as to find out what key or keys it is bound to, if any. Then you can use that keyboard shortcut in place of C-h m. | |
| Jun 26, 2020 at 19:05 | comment | added | interstar | OK ... I guess that's it, but M-x describe-mode was really what I was looking for. Thanks. | |
| Jun 26, 2020 at 18:58 | comment | added | Drew | Start from emacs -Q. Something in your init file is making Emacs use different key bindings, so you and those commenting here are not communicating. Otherwise, use M-x describe-mode to get past the communication blockage. | |
| Jun 26, 2020 at 18:57 | comment | added | interstar | Because C-h just takes me to the top of the buffer. | |
| Jun 26, 2020 at 18:52 | comment | added | Tyler | Why are you doing C-c? C-h m, no C-c | |
| Jun 26, 2020 at 18:51 | comment | added | interstar | OK ... I can do that (ctl-c ctl-h) But if I go on to type "m" it doesn't seem to call the describe-mode function. | |
| Jun 26, 2020 at 18:47 | comment | added | Tyler | @interstar C-h m opens a help buffer that lists all the modes that are active in the buffer you started in. You should end up in a help buffer. | |
| Jun 26, 2020 at 18:32 | comment | added | interstar | That's not working for me. Ctrl+h just takes me to the top of the buffer :-( | |
| Jun 26, 2020 at 18:14 | comment | added | glucas | Yes, Ctrl+h and then m. This calls the command describe-mode for whatever buffer you are currently in. The result is a new buffer that lists all the enabled modes and describes each one. | |
| Jun 26, 2020 at 18:08 | comment | added | interstar | I can do ctrl-c ctrl-h to get into a help screen. But then I'm in a help buffer. I want to see the modes enabled in the buffer I'm currently working in. (And to get a list of their names, not just see the mode line ... I'm trying to understand what the mode line is actually telling me) | |
| Jun 26, 2020 at 18:03 | comment | added | interstar | C-h m? Ctrl + h and then m? | |
| Jun 26, 2020 at 17:38 | history | answered | db48x | CC BY-SA 4.0 |