On my local machine, what can Screen bring, which a terminal emulator or nohup/disown can't?
up vote
-2
down vote
favorite
GNU Screen is a terminal multiplexer, which provides
Persistence: Similar to VNC, many terminal multiplexers allow the user
to start applications from one computer, and then reconnect from a
different computer and continue using the same application without
having to restart it.
Multiple windows: Multiple terminal sessions can be created, each
of which usually runs a single application.
Session Sharing: Terminal multiplexers allow multiple computers to
connect to the same session at once, enabling collaboration between
multiple users.
On my local machine, what can a terminal muplitplexer such as Screen bring to me, which a terminal emulator and nohup/disown can't?
On a local machine, I don't have to worry about unstable network connection between computer and terminal, and don't have to share session with other users.
I can use nohup or disown, if I want to make a process survive the termination of its parent, or something else.
On a terminal emulator, can I just open multiple tabs for multiplexing? Also I think emacs can do that too.
Most if not all of the features that I am interested in are listed above.
I am not questioning the usefulness of Screen. I am trying to know when I can make use of it, such as case where nohup/disown/setsid does not work.
gnu-screen terminal-emulator terminal-multiplexer
|
show 1 more comment
up vote
-2
down vote
favorite
GNU Screen is a terminal multiplexer, which provides
Persistence: Similar to VNC, many terminal multiplexers allow the user
to start applications from one computer, and then reconnect from a
different computer and continue using the same application without
having to restart it.
Multiple windows: Multiple terminal sessions can be created, each
of which usually runs a single application.
Session Sharing: Terminal multiplexers allow multiple computers to
connect to the same session at once, enabling collaboration between
multiple users.
On my local machine, what can a terminal muplitplexer such as Screen bring to me, which a terminal emulator and nohup/disown can't?
On a local machine, I don't have to worry about unstable network connection between computer and terminal, and don't have to share session with other users.
I can use nohup or disown, if I want to make a process survive the termination of its parent, or something else.
On a terminal emulator, can I just open multiple tabs for multiplexing? Also I think emacs can do that too.
Most if not all of the features that I am interested in are listed above.
I am not questioning the usefulness of Screen. I am trying to know when I can make use of it, such as case where nohup/disown/setsid does not work.
gnu-screen terminal-emulator terminal-multiplexer
1
The question is unclear. Do you want to be convinced by someone to usescreen
?
– Kusalananda
Nov 27 at 19:59
... or tmux, which you might know better.
– Tim
Nov 27 at 20:03
@whoever If you don't understand my post, it is completely okay. Just don't close it, and at least give others a chance.
– Tim
Nov 27 at 20:07
2
It's just that it seems to ask "X does these things, which I can already do. Why should I be using X?". This is asking for opinions, IMHO.
– Kusalananda
Nov 27 at 20:09
3
The main use case forscreen
ortmux
is when you need to re-attach to an existing session (e.g. one with a long-running job) because the network connection etc. was interrupted. On a local-only machine, it's difficult to imagine a scenario where this will happen. The other features are just icing on the cake, and nice to have, but you surely can do it in other ways.
– dirkt
Nov 28 at 8:16
|
show 1 more comment
up vote
-2
down vote
favorite
up vote
-2
down vote
favorite
GNU Screen is a terminal multiplexer, which provides
Persistence: Similar to VNC, many terminal multiplexers allow the user
to start applications from one computer, and then reconnect from a
different computer and continue using the same application without
having to restart it.
Multiple windows: Multiple terminal sessions can be created, each
of which usually runs a single application.
Session Sharing: Terminal multiplexers allow multiple computers to
connect to the same session at once, enabling collaboration between
multiple users.
On my local machine, what can a terminal muplitplexer such as Screen bring to me, which a terminal emulator and nohup/disown can't?
On a local machine, I don't have to worry about unstable network connection between computer and terminal, and don't have to share session with other users.
I can use nohup or disown, if I want to make a process survive the termination of its parent, or something else.
On a terminal emulator, can I just open multiple tabs for multiplexing? Also I think emacs can do that too.
Most if not all of the features that I am interested in are listed above.
I am not questioning the usefulness of Screen. I am trying to know when I can make use of it, such as case where nohup/disown/setsid does not work.
gnu-screen terminal-emulator terminal-multiplexer
GNU Screen is a terminal multiplexer, which provides
Persistence: Similar to VNC, many terminal multiplexers allow the user
to start applications from one computer, and then reconnect from a
different computer and continue using the same application without
having to restart it.
Multiple windows: Multiple terminal sessions can be created, each
of which usually runs a single application.
Session Sharing: Terminal multiplexers allow multiple computers to
connect to the same session at once, enabling collaboration between
multiple users.
On my local machine, what can a terminal muplitplexer such as Screen bring to me, which a terminal emulator and nohup/disown can't?
On a local machine, I don't have to worry about unstable network connection between computer and terminal, and don't have to share session with other users.
I can use nohup or disown, if I want to make a process survive the termination of its parent, or something else.
On a terminal emulator, can I just open multiple tabs for multiplexing? Also I think emacs can do that too.
Most if not all of the features that I am interested in are listed above.
I am not questioning the usefulness of Screen. I am trying to know when I can make use of it, such as case where nohup/disown/setsid does not work.
gnu-screen terminal-emulator terminal-multiplexer
gnu-screen terminal-emulator terminal-multiplexer
edited Nov 29 at 14:42
Rui F Ribeiro
38.4k1478127
38.4k1478127
asked Nov 27 at 19:30
Tim
25.3k72243446
25.3k72243446
1
The question is unclear. Do you want to be convinced by someone to usescreen
?
– Kusalananda
Nov 27 at 19:59
... or tmux, which you might know better.
– Tim
Nov 27 at 20:03
@whoever If you don't understand my post, it is completely okay. Just don't close it, and at least give others a chance.
– Tim
Nov 27 at 20:07
2
It's just that it seems to ask "X does these things, which I can already do. Why should I be using X?". This is asking for opinions, IMHO.
– Kusalananda
Nov 27 at 20:09
3
The main use case forscreen
ortmux
is when you need to re-attach to an existing session (e.g. one with a long-running job) because the network connection etc. was interrupted. On a local-only machine, it's difficult to imagine a scenario where this will happen. The other features are just icing on the cake, and nice to have, but you surely can do it in other ways.
– dirkt
Nov 28 at 8:16
|
show 1 more comment
1
The question is unclear. Do you want to be convinced by someone to usescreen
?
– Kusalananda
Nov 27 at 19:59
... or tmux, which you might know better.
– Tim
Nov 27 at 20:03
@whoever If you don't understand my post, it is completely okay. Just don't close it, and at least give others a chance.
– Tim
Nov 27 at 20:07
2
It's just that it seems to ask "X does these things, which I can already do. Why should I be using X?". This is asking for opinions, IMHO.
– Kusalananda
Nov 27 at 20:09
3
The main use case forscreen
ortmux
is when you need to re-attach to an existing session (e.g. one with a long-running job) because the network connection etc. was interrupted. On a local-only machine, it's difficult to imagine a scenario where this will happen. The other features are just icing on the cake, and nice to have, but you surely can do it in other ways.
– dirkt
Nov 28 at 8:16
1
1
The question is unclear. Do you want to be convinced by someone to use
screen
?– Kusalananda
Nov 27 at 19:59
The question is unclear. Do you want to be convinced by someone to use
screen
?– Kusalananda
Nov 27 at 19:59
... or tmux, which you might know better.
– Tim
Nov 27 at 20:03
... or tmux, which you might know better.
– Tim
Nov 27 at 20:03
@whoever If you don't understand my post, it is completely okay. Just don't close it, and at least give others a chance.
– Tim
Nov 27 at 20:07
@whoever If you don't understand my post, it is completely okay. Just don't close it, and at least give others a chance.
– Tim
Nov 27 at 20:07
2
2
It's just that it seems to ask "X does these things, which I can already do. Why should I be using X?". This is asking for opinions, IMHO.
– Kusalananda
Nov 27 at 20:09
It's just that it seems to ask "X does these things, which I can already do. Why should I be using X?". This is asking for opinions, IMHO.
– Kusalananda
Nov 27 at 20:09
3
3
The main use case for
screen
or tmux
is when you need to re-attach to an existing session (e.g. one with a long-running job) because the network connection etc. was interrupted. On a local-only machine, it's difficult to imagine a scenario where this will happen. The other features are just icing on the cake, and nice to have, but you surely can do it in other ways.– dirkt
Nov 28 at 8:16
The main use case for
screen
or tmux
is when you need to re-attach to an existing session (e.g. one with a long-running job) because the network connection etc. was interrupted. On a local-only machine, it's difficult to imagine a scenario where this will happen. The other features are just icing on the cake, and nice to have, but you surely can do it in other ways.– dirkt
Nov 28 at 8:16
|
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
On a local machine, I don't have to worry about unstable network
connection between computer and terminal, and don't have to share
session with other users.
But you can always close your terminal window inadvertently. Or you
can restart your X server.
I can use nohup or disown, if I want to make a process survive the
termination of its parent, or something else.
But you cannot enter input if program requested that.
On a terminal emulator, can I just open multiple tabs for
multiplexing? Also I think emacs can do that too.
Yes, you can do that.
Off the top of my head, GNU screen
also gives you:
ability to select and copy text to X clipboard without using a mouse
ability to select and copy and paste text between screen windows
without using a mouseability to search for a string on the screen without using a mouse
serial console emulator but of you course you can use other programs such as
minicom
for that purpose.
1
To add on to one of your points: nohup/disown are about removing a program from your terminal, but screen is (or, can be) about removing a program from your terminal and possibly bringing it back later
– Fox
Nov 27 at 20:07
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
On a local machine, I don't have to worry about unstable network
connection between computer and terminal, and don't have to share
session with other users.
But you can always close your terminal window inadvertently. Or you
can restart your X server.
I can use nohup or disown, if I want to make a process survive the
termination of its parent, or something else.
But you cannot enter input if program requested that.
On a terminal emulator, can I just open multiple tabs for
multiplexing? Also I think emacs can do that too.
Yes, you can do that.
Off the top of my head, GNU screen
also gives you:
ability to select and copy text to X clipboard without using a mouse
ability to select and copy and paste text between screen windows
without using a mouseability to search for a string on the screen without using a mouse
serial console emulator but of you course you can use other programs such as
minicom
for that purpose.
1
To add on to one of your points: nohup/disown are about removing a program from your terminal, but screen is (or, can be) about removing a program from your terminal and possibly bringing it back later
– Fox
Nov 27 at 20:07
add a comment |
up vote
2
down vote
accepted
On a local machine, I don't have to worry about unstable network
connection between computer and terminal, and don't have to share
session with other users.
But you can always close your terminal window inadvertently. Or you
can restart your X server.
I can use nohup or disown, if I want to make a process survive the
termination of its parent, or something else.
But you cannot enter input if program requested that.
On a terminal emulator, can I just open multiple tabs for
multiplexing? Also I think emacs can do that too.
Yes, you can do that.
Off the top of my head, GNU screen
also gives you:
ability to select and copy text to X clipboard without using a mouse
ability to select and copy and paste text between screen windows
without using a mouseability to search for a string on the screen without using a mouse
serial console emulator but of you course you can use other programs such as
minicom
for that purpose.
1
To add on to one of your points: nohup/disown are about removing a program from your terminal, but screen is (or, can be) about removing a program from your terminal and possibly bringing it back later
– Fox
Nov 27 at 20:07
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
On a local machine, I don't have to worry about unstable network
connection between computer and terminal, and don't have to share
session with other users.
But you can always close your terminal window inadvertently. Or you
can restart your X server.
I can use nohup or disown, if I want to make a process survive the
termination of its parent, or something else.
But you cannot enter input if program requested that.
On a terminal emulator, can I just open multiple tabs for
multiplexing? Also I think emacs can do that too.
Yes, you can do that.
Off the top of my head, GNU screen
also gives you:
ability to select and copy text to X clipboard without using a mouse
ability to select and copy and paste text between screen windows
without using a mouseability to search for a string on the screen without using a mouse
serial console emulator but of you course you can use other programs such as
minicom
for that purpose.
On a local machine, I don't have to worry about unstable network
connection between computer and terminal, and don't have to share
session with other users.
But you can always close your terminal window inadvertently. Or you
can restart your X server.
I can use nohup or disown, if I want to make a process survive the
termination of its parent, or something else.
But you cannot enter input if program requested that.
On a terminal emulator, can I just open multiple tabs for
multiplexing? Also I think emacs can do that too.
Yes, you can do that.
Off the top of my head, GNU screen
also gives you:
ability to select and copy text to X clipboard without using a mouse
ability to select and copy and paste text between screen windows
without using a mouseability to search for a string on the screen without using a mouse
serial console emulator but of you course you can use other programs such as
minicom
for that purpose.
answered Nov 27 at 20:00
Arkadiusz Drabczyk
7,70021734
7,70021734
1
To add on to one of your points: nohup/disown are about removing a program from your terminal, but screen is (or, can be) about removing a program from your terminal and possibly bringing it back later
– Fox
Nov 27 at 20:07
add a comment |
1
To add on to one of your points: nohup/disown are about removing a program from your terminal, but screen is (or, can be) about removing a program from your terminal and possibly bringing it back later
– Fox
Nov 27 at 20:07
1
1
To add on to one of your points: nohup/disown are about removing a program from your terminal, but screen is (or, can be) about removing a program from your terminal and possibly bringing it back later
– Fox
Nov 27 at 20:07
To add on to one of your points: nohup/disown are about removing a program from your terminal, but screen is (or, can be) about removing a program from your terminal and possibly bringing it back later
– Fox
Nov 27 at 20:07
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484499%2fon-my-local-machine-what-can-screen-bring-which-a-terminal-emulator-or-nohup-d%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
The question is unclear. Do you want to be convinced by someone to use
screen
?– Kusalananda
Nov 27 at 19:59
... or tmux, which you might know better.
– Tim
Nov 27 at 20:03
@whoever If you don't understand my post, it is completely okay. Just don't close it, and at least give others a chance.
– Tim
Nov 27 at 20:07
2
It's just that it seems to ask "X does these things, which I can already do. Why should I be using X?". This is asking for opinions, IMHO.
– Kusalananda
Nov 27 at 20:09
3
The main use case for
screen
ortmux
is when you need to re-attach to an existing session (e.g. one with a long-running job) because the network connection etc. was interrupted. On a local-only machine, it's difficult to imagine a scenario where this will happen. The other features are just icing on the cake, and nice to have, but you surely can do it in other ways.– dirkt
Nov 28 at 8:16