Printrun
Printrun copied to clipboard
kliment
Only auto-capitalize if first charater is lower-case
Auto-capitalize commands only if the first character is both a command character and a lower-case one.
This follows the behavior as described by https://github.com/kliment/Printrun/issues/216#issuecomment-18603449.
@frhepo FIY
Hi, I'm happy with the changes and they do work as intended. However, this change might break some people's configurations which relied on pronsole being clever there. Might not break anything since probably most firmwares are already prepared to accept lower-case commands here and there. But I can't really speak for all firmwares. I would leave this kind of change for a future 2.1.x release. I'd even suggest making auto-capitalization an option, being turned off by default. Which falls into the "feature request" category more than a "fix", hence the wait for the next minor version release.
I'm open for comments/suggestions here though.
I know I ran into the autocapitalization issue a few times myself, and every time I rediscovered the @ prefix (I mostly use "printcore", only rarely "pronsole").
It's a double edge sword, I wonder how often people type in lower case and expect the same to work in gcode later.
But without digressing, how do you propose to set such an option? Using a variable as set via "set [var] [v]"? When I run "set" via pronsole I get nothing. Are there any options yet?
Hi, I'm happy with the changes and they do work as intended. However, this change might break some people's configurations which relied on pronsole being clever there. Might not break anything since probably most firmwares are already prepared to accept lower-case commands here and there. But I can't really speak for all firmwares. I would leave this kind of change for a future 2.1.x release. I'd even suggest making auto-capitalization an option, being turned off by default. Which falls into the "feature request" category more than a "fix", hence the wait for the next minor version release.
I'm open for comments/suggestions here though.
I agree. It's not that urgent and allowing the user to switch on/off would be fine.
How do you propose to set such an option? Using a variable as set via "set [var] [v]"? When I run "set" via pronsole I get nothing. Are there any options yet?
Haven't thought about it much yet, but yes, a configuration variable sounds like a good idea.