Typing a string literal in the console on Kubuntu 24.04 raises a syntax error

[ncg777]

The title says it all. I've downgraded back to version 7.7b on Windows. I'm stuck with version 8 on linux though. So much crucial software is failing these days!!!

[nosuchtim]

I just recompiled the latest github main branch of keykit (i.e. version 8.2) on Windows 11 with the makewindows.bat script (i.e. visual studio 2019), and I can't reproduce any failure with typeof. Ditto with the existing pre-compiled binaries in dist/key82_win.zip file. In the gui version (key.exe) I can type:

print typeof("some string")
and it prints

string

Using the non-gui version (lowkey.exe), I can type:

lowkey -c "print(typeof(\"some string\"))"
and it produces the same output.

Please add more details to this issue to help reproduce the issue.

[ncg777]

It happens on my Kubuntu 24.04 setup. I indeed haven't observed this on Windows.

Here is a screenshot as proof:

[ncg777]

Wait a minute... I get a syntax error every time I try to write a string literal...

[nosuchtim]

I'll check things out on Unbuntu. I think you said you went back to 7.something on Windows. What was the reason for that?

…

On Sun, Dec 1, 2024 at 4:04 PM Nicolas Couture-Grenier < ***@***.***> wrote: It happens on my Kubuntu 24.04 setup. I indeed haven't observed this on Windows. Here is a screenshot as proof: image.png (view on web) <https://github.com/user-attachments/assets/d115fb4e-a9af-4085-a785-59262925a6ae> — Reply to this email directly, view it on GitHub <#3456 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABESNRAHPVIHNO4HL5UBH32DOPYHAVCNFSM6AAAAABSZHDF3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJQGMYTONJRGY> . You are receiving this because you commented.Message ID: ***@***.***>

[ncg777]

I just thought typeof was failing. 🤷

Why do strings raise syntax errors?

[ncg777]

I'm using the US international keyboard layout with dead keys. I don't know; it might be related...

[nosuchtim]

On Ubuntu 20.04.6 LTS (GNU/Linux 5.4.0-155-generic x86_64), I compile and execute lowkey and:
lowkey -c 'print(typeof("hi"))'
produces
hi
I don't have access to a linux machine with graphics, so can't test it in the GUI at the moment. I'm not sure what "dead keys" means. Can you try it with a different keyboard and/or keyboard layout?

[ncg777]

I just tried another layout and still have the problem, so it is unrelated to the layout apparently.
I think "dead keys" means that some characters, such as accented characters, requires the user to press many keys in order to produce them.

For example, to make an é, I press ' then e. With that layout, I can put accents on any character! Isn't that fun? But now I know it has nothing to do with the issue I am experiencing...

You don't have access to a linux machine with graphics? Really? Why not?

I'll try to look into this; I rarely ever coded in C or C++ but I may be able to solve this.

[ncg777]

Can lowkey be used as an interactive shell? That would be super useful if it not already the case. I never really used the graphical tools in keykit and a CLI shell would be all I'd use.

[nosuchtim]

I only use Linux on cloud-based servers. I use and prefer Windows everywhere else. I occasionally set up a Linux machine at home to test things, but I don’t have one at the moment. …Tim…

…

On Thu, Dec 12, 2024 at 8:25 PM Nicolas Couture-Grenier < ***@***.***> wrote: I just tried another layout and still have the problem, so it is unrelated to the layout apparently. I think "dead keys" means that some characters, such as accented characters, requires the user to press many keys in order to produce them. For example, to make an é, I press ' then e. With that layout, I can put accents on any character! Isn't that fun? But now I know it has nothing to do with the issue I am experiencing... You don't have access to a linux machine with graphics? Really? Why not? — Reply to this email directly, view it on GitHub <#3456 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABESNQX6BUFRGPN7XUZJUD2FJOVBAVCNFSM6AAAAABSZHDF3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBQGUZDGOJTGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[nosuchtim]

Lowkey can’t be used as an interactive shell. It would be nice, yes. …Tim…

…

On Thu, Dec 12, 2024 at 8:49 PM Nicolas Couture-Grenier < ***@***.***> wrote: Can lowkey be used as an interactive shell? That would be super useful if it not already the case. I never really used the graphical tools in keykit and a CLI shell would be all I'd use. — Reply to this email directly, view it on GitHub <#3456 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABESNU2K4LQ25S56VA66TD2FJROFAVCNFSM6AAAAABSZHDF3SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBQGU2DMMBTGI> . You are receiving this because you commented.Message ID: ***@***.***>

[ncg777]

I prefer windows too, but I own a PC which does not support Windows 11+ because of the TPM requirement so I installed Kubuntu on it and now I'm kind of hooked...

[ncg777]

By the way, my little lib does not seem to work with version 82 on Windows.

I set the KEYROOT environment var to the root of KeyKit, either version 77 or 82 and run key.exe from the root of my lib.

In the case of 77, my lib is loaded correctly but with 82, it is not loaded at all and function names are unrecognized.