-
Notifications
You must be signed in to change notification settings - Fork 33
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
Small change and a question #127
Comments
Hello @joelsolon! Glad to hear from you!
Noted. Will fix it within a couple of days (possibly today).
This is just an aesthetic question. From the very beginning of development, I thought that if there is a space after |
Your comment above reminded me that my real question is: "why is there a space after the >?" Because a space after the > in InterSystems Terminal has a special meaning! If training or certification materials show a screenshot from WebTerminal that looks like this: |
Interesting. You right, in WebTerminal, the space character goes before and after Regarding the ancient form of writing routines, yep, that's true, until we find something better than using xecute under the hood in the core of WebTerminal. It might not support |
I agree; it's not an issue. It was a question added as part of an issue that almost became an issue on its own ;-). I wouldn't bother changing it now, only to support |
@joelsolon, fixed in WebTerminal v4.9.0 along with adding |
Small change: please change COS to ObjectScript in the help for /sql (and anywhere else).
Question: why is there a space between the namespace and the >?
USER > instead of USER>
The text was updated successfully, but these errors were encountered: