#2411 please give us a more user friendly auto type configuration

[lhpitn]

i want to add some return stuff after autotyping for one of my otp entries, so i do

see 2026-01-08 11_22_40-Eintrag bearbeiten.png

fine, it worked i guess, no error,

then i try to test it (cause i know software is made by people and not goods)

what i get is:

see 2026-01-08 11_22_49-KeePass.png

so my question is, why do i get this here and not as a warning on saving this change (would be more apropriate there (ovious i guess))

why is {return} not an alias for {enter}

so some things you could do to make it more usable for everyone i guess

thanks in advance and keep up the good work

TN

[lhpitn]

also this bug report form is a pain, no web 2.0 features like pasting an image inline from the clipboard at all only one manual upload

btw:

---

KeePass

Der folgende Auto-Type-Platzhalter oder Spezialtasten-Code ist unbekannt bzw. wird nicht unterstützt:
{return}

---

OK

means sth like:

---

KeePass

The following auto-type placeholder or special key code is unknown or not supported:
{return}

---

OK

[Paul]

All of the keys are shown when you edit the Auto-Type. No need to guess or type.

cheers, Paul

p.s. please don't open bugs for usability requests. Use the Open Discussion forum.

[Dominik Reichl]

I agree with Paul. Supported auto-type commands and placeholders are listed in the auto-type sequence dialog (which is shown when clicking the 'Edit' button) and in the documentation:
https://keepass.info/help/base/autotype.html#autoseq
https://keepass.info/help/base/placeholders.html
Trying to guess them can easily result in problems; I don't recommend that.

KeePass cannot really validate (beyond simple syntax coloring) an auto-type sequence without executing it, because it doesn't know all auto-type commands and placeholders; plugins can add custom ones. I could imagine allowing plugins to somehow help with the validation, but in any case, I don't see a bug here; a validation is not expected at the moment.

Two different names ('Return' is not an abbreviation of 'Enter' and vice versa) for the same key would cause confusion, thus I'm currently not planning to add that.

Other key sending engines also support {ENTER} only, not {RETURN}:
https://learn.microsoft.com/en-us/dotnet/api/system.windows.forms.sendkeys
https://learn.microsoft.com/en-us/office/vba/language/reference/user-interface-help/sendkeys-statement
https://www.codeproject.com/articles/SendKeys-in-C-

Best regards,
Dominik