Is `~#` a tilde expansion of bash?
Is ~# a tilde expansion of bash? I don't find it in https://www.gnu.org/software/bash/manual/html_node/Tilde-Expansion.html. My question is from https://unix.stackexchange.com/a/506532/674. Thanks.
$ ~#
The following connections are open:
#0 client-session (t4 r0 i0/0 o0/0 fd 5/6 cc -1)
#1 x11 (t4 r3 i0/0 o0/0 fd 8/8 cc -1)
bash bash-expansion
asked 6 hours ago
TimTim
27.9k78269486
add a comment |
Is ~# a tilde expansion of bash? I don't find it in https://www.gnu.org/software/bash/manual/html_node/Tilde-Expansion.html. My question is from https://unix.stackexchange.com/a/506532/674. Thanks.
$ ~#
The following connections are open:
#0 client-session (t4 r0 i0/0 o0/0 fd 5/6 cc -1)
#1 x11 (t4 r3 i0/0 o0/0 fd 8/8 cc -1)
bash bash-expansion
asked 6 hours ago
TimTim
27.9k78269486
add a comment |
Is ~# a tilde expansion of bash? I don't find it in https://www.gnu.org/software/bash/manual/html_node/Tilde-Expansion.html. My question is from https://unix.stackexchange.com/a/506532/674. Thanks.
$ ~#
The following connections are open:
#0 client-session (t4 r0 i0/0 o0/0 fd 5/6 cc -1)
#1 x11 (t4 r3 i0/0 o0/0 fd 8/8 cc -1)
bash bash-expansion
asked 6 hours ago
TimTim
27.9k78269486
Is ~# a tilde expansion of bash? I don't find it in https://www.gnu.org/software/bash/manual/html_node/Tilde-Expansion.html. My question is from https://unix.stackexchange.com/a/506532/674. Thanks.
$ ~#
The following connections are open:
#0 client-session (t4 r0 i0/0 o0/0 fd 5/6 cc -1)
#1 x11 (t4 r3 i0/0 o0/0 fd 8/8 cc -1)
bash bash-expansion
bash bash-expansion
asked 6 hours ago
TimTim
27.9k78269486
asked 6 hours ago
TimTim
27.9k78269486
edited 5 hours ago
Tim
asked 6 hours ago
TimTim
27.9k78269486
asked 6 hours ago
TimTim
27.9k78269486
asked 6 hours ago
TimTim
27.9k78269486
27.9k78269486
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
No, it's a special escape code of ssh that lists forwarded connections. You are obviously connected to your shell over an SSH connection.
bash itself will respond with a "command not found" if you type ~# on the command line:
$ ~#
bash: ~#: command not found
Note that to type an ~ into the shell as the first character after pressing Enter, you will have to press ~ twice if your shell is on the other side of an SSH connection, just because of these escape codes.
Other commands that are available are listed in the ssh manual (these need to be entered as the first characters after pressing Enter):
~. Disconnect.
~^Z Background ssh.
~# List forwarded connections.
~& Background ssh at logout when waiting for forwarded connection /
X11 sessions to terminate.
~? Display a list of escape characters.
~B Send a BREAK to the remote system (only useful if the peer
supports it).
~C Open command line. Currently this allows the addition of port
forwardings using the -L, -R and -D options (see above). It also
allows the cancellation of existing port-forwardings with
-KL[bind_address:]port for local, -KR[bind_address:]port for
remote and -KD[bind_address:]port for dynamic port-forwardings.
!command allows the user to execute a local command if the
PermitLocalCommand option is enabled in ssh_config(5). Basic
help is available, using the -h option.
~R Request rekeying of the connection (only useful if the peer
supports it).
~V Decrease the verbosity (LogLevel) when errors are being written
to stderr.
~v Increase the verbosity (LogLevel) when errors are being written
to stderr.
answered 6 hours ago
KusalanandaKusalananda
137k17258426
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2f507843%2fis-a-tilde-expansion-of-bash%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
No, it's a special escape code of ssh that lists forwarded connections. You are obviously connected to your shell over an SSH connection.
bash itself will respond with a "command not found" if you type ~# on the command line:
$ ~#
bash: ~#: command not found
Note that to type an ~ into the shell as the first character after pressing Enter, you will have to press ~ twice if your shell is on the other side of an SSH connection, just because of these escape codes.
Other commands that are available are listed in the ssh manual (these need to be entered as the first characters after pressing Enter):
~. Disconnect.
~^Z Background ssh.
~# List forwarded connections.
~& Background ssh at logout when waiting for forwarded connection /
X11 sessions to terminate.
~? Display a list of escape characters.
~B Send a BREAK to the remote system (only useful if the peer
supports it).
~C Open command line. Currently this allows the addition of port
forwardings using the -L, -R and -D options (see above). It also
allows the cancellation of existing port-forwardings with
-KL[bind_address:]port for local, -KR[bind_address:]port for
remote and -KD[bind_address:]port for dynamic port-forwardings.
!command allows the user to execute a local command if the
PermitLocalCommand option is enabled in ssh_config(5). Basic
help is available, using the -h option.
~R Request rekeying of the connection (only useful if the peer
supports it).
~V Decrease the verbosity (LogLevel) when errors are being written
to stderr.
~v Increase the verbosity (LogLevel) when errors are being written
to stderr.
answered 6 hours ago
KusalanandaKusalananda
137k17258426
add a comment |
No, it's a special escape code of ssh that lists forwarded connections. You are obviously connected to your shell over an SSH connection.
bash itself will respond with a "command not found" if you type ~# on the command line:
$ ~#
bash: ~#: command not found
Note that to type an ~ into the shell as the first character after pressing Enter, you will have to press ~ twice if your shell is on the other side of an SSH connection, just because of these escape codes.
Other commands that are available are listed in the ssh manual (these need to be entered as the first characters after pressing Enter):
~. Disconnect.
~^Z Background ssh.
~# List forwarded connections.
~& Background ssh at logout when waiting for forwarded connection /
X11 sessions to terminate.
~? Display a list of escape characters.
~B Send a BREAK to the remote system (only useful if the peer
supports it).
~C Open command line. Currently this allows the addition of port
forwardings using the -L, -R and -D options (see above). It also
allows the cancellation of existing port-forwardings with
-KL[bind_address:]port for local, -KR[bind_address:]port for
remote and -KD[bind_address:]port for dynamic port-forwardings.
!command allows the user to execute a local command if the
PermitLocalCommand option is enabled in ssh_config(5). Basic
help is available, using the -h option.
~R Request rekeying of the connection (only useful if the peer
supports it).
~V Decrease the verbosity (LogLevel) when errors are being written
to stderr.
~v Increase the verbosity (LogLevel) when errors are being written
to stderr.
answered 6 hours ago
KusalanandaKusalananda
137k17258426
add a comment |
No, it's a special escape code of ssh that lists forwarded connections. You are obviously connected to your shell over an SSH connection.
bash itself will respond with a "command not found" if you type ~# on the command line:
$ ~#
bash: ~#: command not found
Note that to type an ~ into the shell as the first character after pressing Enter, you will have to press ~ twice if your shell is on the other side of an SSH connection, just because of these escape codes.
Other commands that are available are listed in the ssh manual (these need to be entered as the first characters after pressing Enter):
~. Disconnect.
~^Z Background ssh.
~# List forwarded connections.
~& Background ssh at logout when waiting for forwarded connection /
X11 sessions to terminate.
~? Display a list of escape characters.
~B Send a BREAK to the remote system (only useful if the peer
supports it).
~C Open command line. Currently this allows the addition of port
forwardings using the -L, -R and -D options (see above). It also
allows the cancellation of existing port-forwardings with
-KL[bind_address:]port for local, -KR[bind_address:]port for
remote and -KD[bind_address:]port for dynamic port-forwardings.
!command allows the user to execute a local command if the
PermitLocalCommand option is enabled in ssh_config(5). Basic
help is available, using the -h option.
~R Request rekeying of the connection (only useful if the peer
supports it).
~V Decrease the verbosity (LogLevel) when errors are being written
to stderr.
~v Increase the verbosity (LogLevel) when errors are being written
to stderr.
answered 6 hours ago
KusalanandaKusalananda
137k17258426
No, it's a special escape code of ssh that lists forwarded connections. You are obviously connected to your shell over an SSH connection.
bash itself will respond with a "command not found" if you type ~# on the command line:
$ ~#
bash: ~#: command not found
Note that to type an ~ into the shell as the first character after pressing Enter, you will have to press ~ twice if your shell is on the other side of an SSH connection, just because of these escape codes.
Other commands that are available are listed in the ssh manual (these need to be entered as the first characters after pressing Enter):
~. Disconnect.
~^Z Background ssh.
~# List forwarded connections.
~& Background ssh at logout when waiting for forwarded connection /
X11 sessions to terminate.
~? Display a list of escape characters.
~B Send a BREAK to the remote system (only useful if the peer
supports it).
~C Open command line. Currently this allows the addition of port
forwardings using the -L, -R and -D options (see above). It also
allows the cancellation of existing port-forwardings with
-KL[bind_address:]port for local, -KR[bind_address:]port for
remote and -KD[bind_address:]port for dynamic port-forwardings.
!command allows the user to execute a local command if the
PermitLocalCommand option is enabled in ssh_config(5). Basic
help is available, using the -h option.
~R Request rekeying of the connection (only useful if the peer
supports it).
~V Decrease the verbosity (LogLevel) when errors are being written
to stderr.
~v Increase the verbosity (LogLevel) when errors are being written
to stderr.
answered 6 hours ago
KusalanandaKusalananda
137k17258426
edited 5 hours ago
answered 6 hours ago
KusalanandaKusalananda
137k17258426
answered 6 hours ago
KusalanandaKusalananda
137k17258426
answered 6 hours ago
KusalanandaKusalananda
137k17258426
137k17258426
add a comment |
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.
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%2f507843%2fis-a-tilde-expansion-of-bash%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
