-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
clear command does not work #72
Comments
@avylove, thanks for opening the issue. |
It doesn't seem to. Both this version and the original one work fine when launched outside of Spyder, but don't work both during initialization and if I open additional terminals once Spyder is up. |
Does the console output keeps the same? |
Yes, same output. |
No, the idea is to clean all console output and leave only a single
prompt on it. That's how %clear works on Linux/Mac, but does not on Windows.
El 05/07/17 a las 16:08, Edgar Andrés Margffoy Tuay escribió:
…
Does the console output keeps the same?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#72 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAWS7QZ-cl_ahc7z9Hws2_X6SgxhCG07ks5sK_tHgaJpZM4OH74m>.
|
It seems like something about the Spyder integration interferes with the clear command. I'm not sure it's a timing issue because the clear command does not clear the screen even after I can interact with the console, yet it works fine when the server is run independently and the console is accessed through Chrome. |
Does this happens only with the first console, or does it also happens with new terminal tabs? |
New terminal tabs as well |
Well I have mixed news. Turns out the issue must have been in Spyder because I don't have the issue with 0.1.2 when I bootstrap Spyder 3.x. Wish I had thought to do that before. I found this out because I installed the spyder-terminal master branch and didn't have the spyder-terminal plugin available in Spyder, so I thought maybe there was a dependency on the latest. Well it didn't work there either. Not sure what the issue is. How do I see some output? |
Have you tried to open an internal console and see if there is some output there? |
First thing I tried. Nothing there. |
How did you installed the plugin? |
Is the plugin visible? Sometimes the plugin might be not be shown because its visibility is disabled |
It wasn't visible or on the panes menu. I just realized I was using your fork instead of the master branch. Trying with the master branch now and having issues with bower not being in the path. Installing with pip. Added --no-deps because it was failing with the Spyder version. Spyder isn't installed, just launching with bootstap script. pip3 install --user --no-deps git+https://github.com/spyder-ide/spyder-terminal.git Is there a better way to go about this? |
Well, to install bower, you just need to execute: npm install -g bower |
I would prefer to emit the following commands: # From spyder master branch
python setup.py install
# From spyder-terminal master branch
pip install -U . |
Well I don't install things globally that aren't in rpms, but I did run: npm install bower Then I added ~/node_modules/.bin to my PATH. It installed and everything looks fine with spyder-terminal@master and spyder@3.x. |
@avylove Great to hear that is working! |
Release v0.2 of spyder-terminal will come on the following days |
The clear command does not seem to function. I'm not sure if this is a xterm.js bug or a spyder-terminal bug.
What steps will reproduce the problem?
What is the expected output? What do you see instead?

Expected:
[avylove@localhost Project]$
Actual:
Please provide any additional information below
Neither clear nor reset commands seem to do anything. I tried changing the clearTerm() function from to user term.clear(), which removed the clear command from the terminal, but still didn't clear the terminal.
Versions and main components
The text was updated successfully, but these errors were encountered: