Tag Info

New answers tagged

0

Remote GUI (X11) connections go through TCP port 6000+n where n is the display number┬╣. So the two messages refer to the same problem: some program tried to connect to display 12 and failed. Emacsclient doesn't make X11 connections, Emacs does. So if you see this message, it means Emacsclient managed to contact Emacs and tell it to open a new frame. ...


0

Nevermind, after googling I found after more research that the vertical split requires at least version 4.1 of screen, and I have version 4.0, not yet sure why the commands don't always work first go, if anyone knows why this might be the case please put an answer.


1

Terminals transmit characters┬╣, not keys. When you press a key or key combination like Ctrl+Alt+Enter, the terminal has to translate it to a character or character sequence. There aren't nearly enough characters to represent all keys, so most such combinations are transmitted as escape sequences: a sequence of characters starting with the escape character. ...


3

Note that screen is a terminal emulator. So your question is a bit like asking how can I start xterm from gnome-terminal and have what was last displayed in xterm visible in my gnome-terminal when xterm exits. Now the difference between xterm and screen is that while xterm uses the X protocol to draw its screen, screen uses a host terminal. By default, ...


1

I did itusing a bit of a hackier way: Using tcsh I put the following in my .cshrc # escape sequence to set the screen title alias stitle 'echo -n "^[k\!*^[\\"' # shorthand to set the screen title to the hostname alias H stitle `hostname -s` # shorthand to set the screen title to the filename, launch vim, and then set it back alias ...


2

If you just want to get rid of this screen session , you can do: kill 9667; screen -wipe


1

It looks like you're missing a few dependencies. That would be a bug in the configure script. You might want to file a bugreport to the screen maintainers.


0

Now byobu is based on tmux, the easiest way is to directly use tmux. in my case I use the following syntax: tmux new -d -s session-name /path/to/my/Script.sh and connect to it I use: tmux session has -t-name in your crontab you will have to enter: @reboot tmux new -d -s session-name /path/to/my/Script.sh


2

Unless the screen session in question is created with multiuser on, you can't. Even if you set your SCREENDIR variable to point at the other user's socket directory, screen will just complain that you don't own the directory and quit when you try to use it. Of course, you can simply su to the other user and use screen in the normal way.



Top 50 recent answers are included