Minor annoyance with the Screen linux utility; when connected to a Linux (Fedora) box from my Mac (using Terminal), when I'm writing out a long command, usually when the text reaches the edge of the terminal window, the cursor drops down a line and continues the command. However, if I'm currently on the bottom row of the terminal, and run off the edge, instead of adding a new line and pushing everything up, it blanks the line and puts the cursor at the beginning of the row. If I grab the terminal window and resize its width, the command automatically pops down to a second row as the screen refreshes. Is there a way to get the command to break to a second row properly without resizing the window? Some configuration setting in Screen to get it to play nicely with Mac's Terminal?
I have a Mac which uses MacPorts to have multiple versions of Python installed and use the python_select application to switch between them.
Currently, this Mac has OS 10.6.6, which comes with Python 2.6.1 installed as /usr/bin/python. Using MacPorts, I've installed the python27, python31, and python_select ports and now have this issue: python_select seems to not be switching the default python properly:
$ which python
/usr/bin/python
$ python -V
Python 2.6.1
$ /usr/bin/python -V
Python 2.6.1
$ sudo python_select python27
Selecting version "python27" for python
$ which python
/opt/local/bin/python
$ ls -l /opt/local/bin/python
lrwxr-xr-x 1 root admin 24B Mar 18 10:24 /opt/local/bin/python -> /opt/local/bin/python2.7
$ python -V
Python 2.6.1 # <-- Wrong!!!
$ /opt/local/bin/python -V
Python 2.7.1 # <-- Why are you not default?
So, after running python_select, which python seems to think that the /opt/local/bin version is going to be used, but in reality, it seems that the /usr/bin one is taking precedent unless I specifically call the /opt/local/bin one.
Is there something I'm doing wrong?
So, on a CentOS box, I accidentally executed :w<Down> in a vim editor, with "<Down>" being literally pressing the down arrow key on the keyboard (rendered onscreen as "<Down>"), and now I have a file named "<Down>" which I can't seem to get rid of; running "rm <Down>" (literally spelling out "less-than, D, o, w, n, greater-than") gives a syntax error.
How can I get rid of this file with the funky name?
Given a setup of a headless Linux box running on a network, but having Xorg installed, and having various other machines on the network capable of using SSH with X-forwarding to connect to that box, and have X11 apps run on the local machine, I have an interesting question.
I'm familiar with using 'screen' to encapsulate an SSH session such that I can detach and reattach to it from a different machine, and while detached, processes continue to run, and when I reattach, I can scroll back through the buffer and see what was output.
Is the same thing possible for X11 apps? I ran into the situation where I wanted to run wireshark for some time to do some packet sniffing, but while it was running, I needed to switch computers, but realized there was no way that I knew to 'disconnect' from the wireshark thread, while still leaving it running, and in a state that I could reconnect to it at a later time (perhaps from a different machine) through another SSH session. Is there a similar process to the 'screen' disconnect/reconnect that can be done with X11 apps that are forwarded to a remote machine?