Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spaces in additional attribute not working for autotype #1546

Closed
grenzor opened this issue Feb 28, 2018 · 5 comments
Closed

Spaces in additional attribute not working for autotype #1546

grenzor opened this issue Feb 28, 2018 · 5 comments
Assignees
Milestone

Comments

@grenzor
Copy link

grenzor commented Feb 28, 2018

Expected Behavior

In 2.2.4 I had an additional attribute with a space in it like SOME NAME and it worked when using it for autotype sequence using something like {S:SOME NAME}.

Current Behavior

In 2.3.0 Autotype sequences with attributes like {S:SOME NAME} containing spaces gives the error The Syntax of your Auto-type statement is incorrect (whereas {S:SOMENAME} gives no error). Not sure if this is new behavior in 2.3.0 (using KDBX4) but just something I wanted to ask about in case it's a bug.

Operating system: Windows

@googlebleh
Copy link

I'm getting the same error message for an additional attribute with an underscore in the name.

My equivalent case has the attribute SOME_NAME, and auto-type says the syntax {S:SOME_NAME} is incorrect. Changing it to SOMENAME and, respectively, {S:SOMENAME} works as expected.

OS: Ubuntu 17.10, amd64

@phoerious phoerious added this to the 2.3.1 milestone Feb 28, 2018
@TheZ3ro TheZ3ro self-assigned this Feb 28, 2018
@TheZ3ro
Copy link
Contributor

TheZ3ro commented Feb 28, 2018

Thanks for the report, I can reproduce this.

I will fix it in the next minor 2.3.1 version

@brwolfgang
Copy link

Adding some more info: Autotype also fails if the additional attribute has an accent such as í, ó, ú, â, ã, etc.
Just pointing that it is a regression since it worked fine until last version.

@TheZ3ro
Copy link
Contributor

TheZ3ro commented Mar 5, 2018

Check out release/2.3.1 branch, should be fixed now

We will close this issue once 2.3.1 is released officially

@phoerious
Copy link
Member

Fixed in #1626

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants