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

zprint COS command does not work #125

Closed
yaronmunz opened this issue Jun 27, 2019 · 5 comments
Closed

zprint COS command does not work #125

yaronmunz opened this issue Jun 27, 2019 · 5 comments

Comments

@yaronmunz
Copy link

I have installed WebTerminal on IRIS 2019.1.0 and it is working great.
However, a ZP (zprint) COS command does not work.
when issuing for example:
zl test zp
I get the USER> prompt without anything
(if issuing the same on IRIS terminal, all work fine... i.e the routine has a source).

I have seen that the ZP (zprint) command is missing on the StaticContent class.
I tried to add it there, and then autocomplete of ZP (to zprint) works, but still not output is sent back to the client.

@nikitaeverywhere
Copy link
Member

Hello @yaronmunz! Thank you for reporting this issue.

The thing is, we have a group of issues labeled Core Enhancement (blocker), which doesn't allow to run something exactly because of how WebTerminal works under the hood (on top of ObjectScript xecute + I/O redirection). Some system routines have their own rules for input/output (they switch output devices or expect some core terminal/system variables to be set by underlying I/O system), hence new problems appear.

I assume this wouldn't be the case if I implemented, for example, WebTerminal over telnet (because telnet wraps all internal execution magic and works exactly like a terminal), but it seems that this approach also has its own problems. Looks like telnet has its own disadvantages (is it Windows-only?).

So, currently, I am looking for an approach to change WebTerminal's core, which I belive will fix all similar issues, including yours.

@yaronmunz
Copy link
Author

yaronmunz commented Jun 28, 2019 via email

@nikitaeverywhere
Copy link
Member

However, I think that some of the issues that were reported (I looked at some of them in github) might be solved with minimal coding of those special cases. (probably the same way you implement the sql feature).

Do you mean just hard-coding some cases like "if command = this then execute this custom code"? If so, this is a very dangerous way to fix things... At least, it hides an original behavior from the user, which may mislead them if the command has some options not covered by this "dirty fix".

@yaronmunz
Copy link
Author

yaronmunz commented Jul 1, 2019 via email

@nikitaeverywhere
Copy link
Member

I understand this case. However, I would keep hard-coding away from the "official" releases. Just another possible case from numerous cases... If the project goes wild (for example, a maintainer changes) then people will start to hard-code everything by example, and this will turn into a total mess.

I am closing this issue - please feel free follow WebTerminal project, I think it has a good chance to be fixed one day in the future, within the core patch making it 100% compatible with standard Cache Term.

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

2 participants