Stupide 'MORE' prompt!!!!

[Poop Loops]

Any way to get rid of it? I just died to a white centipede at dlvl 1 because I have my maa* bound to / and obviously hit 5 on the numpad to fire on the target. So I'd keep hitting /5/5/5/5/5 and it turns out whenever I hit / it was to forward the "more" prompt and then 5 meant I was losing a turn just standing there like an idiot.

Same things have happened with stores. I sell something, then like 50 pages of "more" when I'm trying to sell something else and it turns out that I just bought the thing I sold. Great.

Also, how come I can't keymap F1, F2, etc.? I am running Ubuntu if it matters. But I'd really like to bind more stuff.

[roustk]

Any way to get rid of it?

Check the Warning and disturbance options. You are looking for quick_messages (yes to allow any key to clear a more prompt) or auto_more (yes means no more prompts at all).

Also, how come I can't keymap F1, F2, etc.? I am running Ubuntu if it matters. But I'd really like to bind more stuff.

You should not make keymaps unless you really know what you're doing -- see the "Macro Problem" thread (which actually was a keymap problem).

Macros are much more robust, respect roguelike/standard mode, and support special keys (like F1, F2, etc). Set them up using the same "Interact with macros" screen, but options 2-5, not 6-9.

Kevin

[Matthias]

You should also start your marcoes with something like multiple \e (for escape) , so if there are promts left they will be closed. That one closes not only more promts, but also other things you might still have waiting for input

[Poop Loops]

All I'm looking for is a single button to do a sequence of buttons. So if I want to cast magic missile, I'd do maa* and then pick a target. So I bound / to be maa*. I don't quite understand the concept of macros. Seems a lot more complicated.

Thanks for the tip, roustk.

[roustk]

All I'm looking for is a single button to do a sequence of buttons. So if I want to cast magic missile, I'd do maa* and then pick a target. So I bound / to be maa*. I don't quite understand the concept of macros. Seems a lot more complicated.

Macros and keymaps are very similar, differing only in how the program interprets them. The complications that I can think of (e.g., inscribing with @f0) are the same for both.

A macro pushes a string (like "maa*") into the keyboard buffer when a particular keypress is made, exactly as if you simply typed "maa*". A macro can be assigned to (almost) any distinguishable keypress that your keyboard makes.

A keymap pushes a string (like "maa*") into the internal (already interpreted) buffer when a particular character is read from the buffer. A keymap can be assigned only to about 250 characters (and thus only to 'simple' keys). [Side note: I'm not sure if you can actually assign a keymap to any character above 127 using a US keyboard.]

[momo125]

yeah start a macro with /e/e/e and don't do spells with book a; inscribe books and use book 1 for magic missle.