hotwire-shell - Project Hosting on Google Code

Earlier this year Mar 29, 2009 issue 211 (Add the editor joe to list of terminal commands) reported by sean.flanigan - What steps will reproduce the problem? 1. bash> export EDITOR=joe 2. bash> hotwire 3. hotwire> ed hello.txt What is the expected output? What do you see instead? joe should come up in a new terminal window, instead, I get: Processing '/etc/joe/joerc'...Processing '/etc/joe/ftyperc'...done done cm=(nil) ch=(nil) cv=(nil) ho=(nil) lf=0x8a0a13c DO=(nil) ll=(nil) up=(nil) UP=(nil) cr=0x8a0a140 Sorry, your terminal can't do absolute cursor positioning. It's broken What version of the product are you using? On what operating system? 0.721 on F9 Please provide any additional information below. Perhaps Hotwire should always treat the default EDITOR as a terminal application. What steps will reproduce the problem? 1. bash> export EDITOR=joe 2. bash> hotwire 3. hotwire> ed hello.txt What is the expected output? What do you see instead? joe should come up in a new terminal window, instead, I get: Processing '/etc/joe/joerc'...Processing '/etc/joe/ftyperc'...done done cm=(nil) ch=(nil) cv=(nil) ho=(nil) lf=0x8a0a13c DO=(nil) ll=(nil) up=(nil) UP=(nil) cr=0x8a0a140 Sorry, your terminal can't do absolute cursor positioning. It's broken What version of the product are you using? On what operating system? 0.721 on F9 Please provide any additional information below. Perhaps Hotwire should always treat the default EDITOR as a terminal application. Mar 21, 2009 issue 210 (can't use forward shortcut in search since it opens file men...) reported by zioLogaritmo - What steps will reproduce the problem? 1. display a text file with cat textfilename 2. hit control-s and insert something to search 3. press alt-f one or two times, at that point file menu should get opened pressing alt-b for going back works as expected What version of the product are you using? On what operating system? ubuntu intrepid hotwire 0.721 changeset: 1176 date: 2008-03-23 15:15:17 -0400 (Sun, 23 Mar 2008 What steps will reproduce the problem? 1. display a text file with cat textfilename 2. hit control-s and insert something to search 3. press alt-f one or two times, at that point file menu should get opened pressing alt-b for going back works as expected What version of the product are you using? On what operating system? ubuntu intrepid hotwire 0.721 changeset: 1176 date: 2008-03-23 15:15:17 -0400 (Sun, 23 Mar 2008 Feb 10, 2009 issue 209 (can't even run the app) reported by ker...@medianox.net - I have verified that I have all the latest packages for Python installed. Unpakced the latest verison of hotwire. When I run, I get thie: "[kameronc@kameronclinux hotwire-0.721]$ Running uninstalled, extending PYTHONPATH with: /home/kameronc/install/hotwire-0.721 Traceback (most recent call last): File "ui/hotwire", line 209, in ? main() File "ui/hotwire", line 136, in main import hotwire.completion File "/home/kameronc/install/hotwire-0.721/hotwire/completion.py", line 36, in ? from hotwire.state import History File "/home/kameronc/install/hotwire-0.721/hotwire/state.py", line 24, in ? from pysqlite2 import dbapi2 as sqlite3 ImportError: No module named pysqlite2 " I have verified that I have all the latest packages for Python installed. Unpakced the latest verison of hotwire. When I run, I get thie: "[kameronc@kameronclinux hotwire-0.721]$ Running uninstalled, extending PYTHONPATH with: /home/kameronc/install/hotwire-0.721 Traceback (most recent call last): File "ui/hotwire", line 209, in ? main() File "ui/hotwire", line 136, in main import hotwire.completion File "/home/kameronc/install/hotwire-0.721/hotwire/completion.py", line 36, in ? from hotwire.state import History File "/home/kameronc/install/hotwire-0.721/hotwire/state.py", line 24, in ? from pysqlite2 import dbapi2 as sqlite3 ImportError: No module named pysqlite2 " Jan 08, 2009 issue 207 (No ANSI Support in a Shell... AT LEAST Colors???) reported by phyo.arkarlwin - What steps will reproduce the problem? 1. Start Hotwire 2. Run any Shell command with colored output 3. Output is not colored What is the expected output? What do you see instead? Grabled , output with ANSI keys all messed up What version of the product are you using? On what operating system? Latest SVN Please provide any additional information below. Well HOTWIRE SHELL Claims to be a powerful Shell which saids "BETTER" then unix shell.. SO it should compatible with UNIX Commands . Now it have a lot of fancy stuff already but There is no Terminal Compatibility .. THat leave me no choice but to use traditional shells. HW Shell idea is good but compatibility is something important in UNIX Design Philisophy. is really a bugger for me. What steps will reproduce the problem? 1. Start Hotwire 2. Run any Shell command with colored output 3. Output is not colored What is the expected output? What do you see instead? Grabled , output with ANSI keys all messed up What version of the product are you using? On what operating system? Latest SVN Please provide any additional information below. Well HOTWIRE SHELL Claims to be a powerful Shell which saids "BETTER" then unix shell.. SO it should compatible with UNIX Commands . Now it have a lot of fancy stuff already but There is no Terminal Compatibility .. THat leave me no choice but to use traditional shells. HW Shell idea is good but compatibility is something important in UNIX Design Philisophy. is really a bugger for me. Older Oct 06, 2008 issue 157 (Ctrl-shift-c loses some ping output) commented on by teratorn - I think this is a pretty huge problem... Ctrl-Shift-C needs to send SIGINT, by default. Why must Hotwire keep track of the fact that SIGINT was sent to the process? The processing is "running" when it's running, and it should be considered "cancelled" when it exits. If you want some other button that sends SIGKILL for terminating processes that aren't playing nice, then that's fine. But it certainly shouldn't be default behavior. I guess I just don't understand why the Hotwire model needs to change in order to switch to using SIGINT instead of SIGKILL. Instead of changing state to "cancelled" when C-Shift-C is pressed, it could simply do that when the child process exits. I think this is a pretty huge problem... Ctrl-Shift-C needs to send SIGINT, by default. Why must Hotwire keep track of the fact that SIGINT was sent to the process? The processing is "running" when it's running, and it should be considered "cancelled" when it exits. If you want some other button that sends SIGKILL for terminating processes that aren't playing nice, then that's fine. But it certainly shouldn't be default behavior. I guess I just don't understand why the Hotwire model needs to change in order to switch to using SIGINT instead of SIGKILL. Instead of changing state to "cancelled" when C-Shift-C is pressed, it could simply do that when the child process exits. Oct 06, 2008 issue 154 (implement deep globs: //.py) commented on by teratorn - Please also consider the recursive glob from ZSH: /.py I often use this via a global alias: alias -g PY="*/.py" Then I can just type PY anywhere on the command-line to have it expand all python files. Please also consider the recursive glob from ZSH: */.py I often use this via a global alias: alias -g PY="*/.py" Then I can just type PY anywhere on the command-line to have it expand all python files. Oct 03, 2008 r1300 (term nethack by default ) committed by cgwalters - term nethack by default term nethack by default Aug 24, 2008 issue 206 (ssh keeps connecting until passwd entered -- seems to connec...) commented on by juhpetersen - I opened a ticket for this against hotssh: http://bugzilla.gnome.org/show_bug.cgi?id=549250 I opened a ticket for this against hotssh: http://bugzilla.gnome.org/show_bug.cgi?id=549250 Aug 20, 2008 issue 206 (ssh keeps connecting until passwd entered -- seems to connec...) reported by juhpetersen - I have been running hotwire-ssh (revision 1299) for a while. Today someone pointed out to me that it seems to connect many times to the remove sshd server when running a connection. Is this a known issue? What steps will reproduce the problem? 1. run "tail -f /var/log/secure" on remote host 2. ssh to it from hotwire (hotwire-ssh) from another machine What is the expected output? plain ssh gives on login: Aug 21 13:50:05 myserver sshd[5239]: Accepted password for testuser from 10.6.0.22 port 46075 ssh2 Aug 21 13:50:05 myserver sshd[5239]: pam_unix(sshd:session): session opened for user testuser by (uid=0) and then on logout: Aug 21 13:52:44 myserver sshd[5239]: pam_unix(sshd:session): session closed for user testuser What do you see instead? hotwire ssh gives before logging in and after logging out lots of these: Aug 21 14:00:14 myserver sshd[5550]: Connection closed by 10.6.0.22 Aug 21 14:00:18 myserver sshd[5553]: Connection closed by 10.6.0.22 Aug 21 14:00:23 myserver sshd[5556]: Connection closed by 10.6.0.22 Aug 21 14:00:27 myserver sshd[5558]: Connection closed by 10.6.0.22 Aug 21 14:00:31 myserver sshd[5562]: Connection closed by 10.6.0.22 Aug 21 14:01:24 myserver sshd[5588]: Connection closed by 10.6.0.22 Aug 21 14:01:28 myserver sshd[5591]: Connection closed by 10.6.0.22 Why does hotwire ssh repeatedly connect to the ssh server? I have been running hotwire-ssh (revision 1299) for a while. Today someone pointed out to me that it seems to connect many times to the remove sshd server when running a connection. Is this a known issue? What steps will reproduce the problem? 1. run "tail -f /var/log/secure" on remote host 2. ssh to it from hotwire (hotwire-ssh) from another machine What is the expected output? plain ssh gives on login: Aug 21 13:50:05 myserver sshd[5239]: Accepted password for testuser from 10.6.0.22 port 46075 ssh2 Aug 21 13:50:05 myserver sshd[5239]: pam_unix(sshd:session): session opened for user testuser by (uid=0) and then on logout: Aug 21 13:52:44 myserver sshd[5239]: pam_unix(sshd:session): session closed for user testuser What do you see instead? hotwire ssh gives before logging in and after logging out lots of these: Aug 21 14:00:14 myserver sshd[5550]: Connection closed by 10.6.0.22 Aug 21 14:00:18 myserver sshd[5553]: Connection closed by 10.6.0.22 Aug 21 14:00:23 myserver sshd[5556]: Connection closed by 10.6.0.22 Aug 21 14:00:27 myserver sshd[5558]: Connection closed by 10.6.0.22 Aug 21 14:00:31 myserver sshd[5562]: Connection closed by 10.6.0.22 Aug 21 14:01:24 myserver sshd[5588]: Connection closed by 10.6.0.22 Aug 21 14:01:28 myserver sshd[5591]: Connection closed by 10.6.0.22 Why does hotwire ssh repeatedly connect to the ssh server? Aug 20, 2008 issue 183 (vim fails to find .vimrc) commented on by dmishd - related to this (I think), typing "powertop" in hotwire brings up a terminal with no output. The status line above the terminal environment says "Running (pid -1)". But no input seems to matter. Ctrl-C and Ctrl-Shift-C do nothing. Enter does not close the window. I have to do Alt-F4 (or use the mouse) to close the window. In a normal terminal, the output is: mish@whisper:~$ powertop The program 'powertop' is currently not installed. You can install it by typing: sudo apt-get install powertop bash: powertop: command not found And if I do "term sh -c 'powertop; sleep 3'" then I get "sh: powertop: not found". And pressing enter closes the window, as expected. If I do "term sh -c 'powertop'" I get a blank window, but pressing enter does close the window. related to this (I think), typing "powertop" in hotwire brings up a terminal with no output. The status line above the terminal environment says "Running (pid -1)". But no input seems to matter. Ctrl-C and Ctrl-Shift-C do nothing. Enter does not close the window. I have to do Alt-F4 (or use the mouse) to close the window. In a normal terminal, the output is: mish@whisper:~$ powertop The program 'powertop' is currently not installed. You can install it by typing: sudo apt-get install powertop bash: powertop: command not found And if I do "term sh -c 'powertop; sleep 3'" then I get "sh: powertop: not found". And pressing enter closes the window, as expected. If I do "term sh -c 'powertop'" I get a blank window, but pressing enter does close the window. Aug 07, 2008 r1299 (Don't stop processing on invalid unicode ) committed by cgwalters - Don't stop processing on invalid unicode Don't stop processing on invalid unicode Jul 30, 2008 issue 158 (no user feedback if term returns immediately) commented on by juhpetersen - Hmm, I confess to slowly getting used to it, but the extra Return still seems a waste to me. How about an option to "term" to skip the Return, which could be used for aliases like man, top, etc that don't need it but keep Return by default? Hmm, I confess to slowly getting used to it, but the extra Return still seems a waste to me. How about an option to "term" to skip the Return, which could be used for aliases like man, top, etc that don't need it but keep Return by default? Jul 30, 2008 issue 187 ("cd" automatically does "ls") commented on by juhpetersen - I sympathize with the reporter - I mostly find auto-ls too slow to be useful as well. I would make it a config option at least and maybe even default to off. I sympathize with the reporter - I mostly find auto-ls too slow to be useful as well. I would make it a config option at least and maybe even default to off.

issue 206 (ssh keeps connecting until passwd entered -- seems to connec...) reported by juhpetersen - I have been running hotwire-ssh (revision 1299) for a while. Today someone pointed out to me that it seems to connect many times to the remove sshd server when running a connection. Is this a known issue? What steps will reproduce the problem? 1. run "tail -f /var/log/secure" on remote host 2. ssh to it from hotwire (hotwire-ssh) from another machine What is the expected output? plain ssh gives on login: Aug 21 13:50:05 myserver sshd[5239]: Accepted password for testuser from 10.6.0.22 port 46075 ssh2 Aug 21 13:50:05 myserver sshd[5239]: pam_unix(sshd:session): session opened for user testuser by (uid=0) and then on logout: Aug 21 13:52:44 myserver sshd[5239]: pam_unix(sshd:session): session closed for user testuser What do you see instead? hotwire ssh gives before logging in and after logging out lots of these: Aug 21 14:00:14 myserver sshd[5550]: Connection closed by 10.6.0.22 Aug 21 14:00:18 myserver sshd[5553]: Connection closed by 10.6.0.22 Aug 21 14:00:23 myserver sshd[5556]: Connection closed by 10.6.0.22 Aug 21 14:00:27 myserver sshd[5558]: Connection closed by 10.6.0.22 Aug 21 14:00:31 myserver sshd[5562]: Connection closed by 10.6.0.22 Aug 21 14:01:24 myserver sshd[5588]: Connection closed by 10.6.0.22 Aug 21 14:01:28 myserver sshd[5591]: Connection closed by 10.6.0.22 Why does hotwire ssh repeatedly connect to the ssh server?

I have been running hotwire-ssh (revision 1299) for a while. Today someone pointed out to me that it seems to connect many times to the remove sshd server when running a connection. Is this a known issue? What steps will reproduce the problem? 1. run "tail -f /var/log/secure" on remote host 2. ssh to it from hotwire (hotwire-ssh) from another machine What is the expected output? plain ssh gives on login: Aug 21 13:50:05 myserver sshd[5239]: Accepted password for testuser from 10.6.0.22 port 46075 ssh2 Aug 21 13:50:05 myserver sshd[5239]: pam_unix(sshd:session): session opened for user testuser by (uid=0) and then on logout: Aug 21 13:52:44 myserver sshd[5239]: pam_unix(sshd:session): session closed for user testuser What do you see instead? hotwire ssh gives before logging in and after logging out lots of these: Aug 21 14:00:14 myserver sshd[5550]: Connection closed by 10.6.0.22 Aug 21 14:00:18 myserver sshd[5553]: Connection closed by 10.6.0.22 Aug 21 14:00:23 myserver sshd[5556]: Connection closed by 10.6.0.22 Aug 21 14:00:27 myserver sshd[5558]: Connection closed by 10.6.0.22 Aug 21 14:00:31 myserver sshd[5562]: Connection closed by 10.6.0.22 Aug 21 14:01:24 myserver sshd[5588]: Connection closed by 10.6.0.22 Aug 21 14:01:28 myserver sshd[5591]: Connection closed by 10.6.0.22 Why does hotwire ssh repeatedly connect to the ssh server?

Earlier this year

Older