Backslash in Path
up vote
0
down vote
favorite
I would like to know what the meaning of the backslash is when used in a path, e.g.:
ll /opt/deployment/release175/war-files files/
output, for example is:
accounting-module.war
finance-module.war
Thanks.
shell
add a comment |
up vote
0
down vote
favorite
I would like to know what the meaning of the backslash is when used in a path, e.g.:
ll /opt/deployment/release175/war-files files/
output, for example is:
accounting-module.war
finance-module.war
Thanks.
shell
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I would like to know what the meaning of the backslash is when used in a path, e.g.:
ll /opt/deployment/release175/war-files files/
output, for example is:
accounting-module.war
finance-module.war
Thanks.
shell
I would like to know what the meaning of the backslash is when used in a path, e.g.:
ll /opt/deployment/release175/war-files files/
output, for example is:
accounting-module.war
finance-module.war
Thanks.
shell
shell
edited Nov 26 at 14:05
Kusalananda
118k16223364
118k16223364
asked Nov 26 at 12:49
user322848
6
6
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
4
down vote
The backslash is the escape character to tell the shell not to interpret some special characters. In your case, it escapes the space character.
In shell, a space is normally used to split arguments. Without the backslash, your shell would interpret the space as usually. You would have 2 arguments to your ll
call, which would probably lead to a "File or Directory not found" error.
Alternatively you could surround your argument with quotes:
ll /opt/deployment/release175/war-files files/
ll "/opt/deployment/release175/war-files files/"
ll '/opt/deployment/release175/war-files files/'
Backslash is also used to escape other special characters:
(
$
{
*
#
\
... and under some circumstances!
when combined with other characters (interactivebash
to avoid history expansion).
– Kusalananda
Nov 26 at 13:47
add a comment |
up vote
2
down vote
In Unix/Linux (or POSIX), the backslash is an escape character.
In that particular case, the backslash is escaping white space. If it weren't there then the ll
command would attempt to operate on:
/opt/deployment/release175/war-files
and
files/
You can also use double or single quotes
ll "opt/deployment/release175/war-files files/"
ll 'opt/deployment/release175/war-files files/'
The backslash can also be used to escape other special characters with other commands:
rpm -qa | postgre*
grep .regex file
sed 's//this/path//that//path/g'
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
The backslash is the escape character to tell the shell not to interpret some special characters. In your case, it escapes the space character.
In shell, a space is normally used to split arguments. Without the backslash, your shell would interpret the space as usually. You would have 2 arguments to your ll
call, which would probably lead to a "File or Directory not found" error.
Alternatively you could surround your argument with quotes:
ll /opt/deployment/release175/war-files files/
ll "/opt/deployment/release175/war-files files/"
ll '/opt/deployment/release175/war-files files/'
Backslash is also used to escape other special characters:
(
$
{
*
#
\
... and under some circumstances!
when combined with other characters (interactivebash
to avoid history expansion).
– Kusalananda
Nov 26 at 13:47
add a comment |
up vote
4
down vote
The backslash is the escape character to tell the shell not to interpret some special characters. In your case, it escapes the space character.
In shell, a space is normally used to split arguments. Without the backslash, your shell would interpret the space as usually. You would have 2 arguments to your ll
call, which would probably lead to a "File or Directory not found" error.
Alternatively you could surround your argument with quotes:
ll /opt/deployment/release175/war-files files/
ll "/opt/deployment/release175/war-files files/"
ll '/opt/deployment/release175/war-files files/'
Backslash is also used to escape other special characters:
(
$
{
*
#
\
... and under some circumstances!
when combined with other characters (interactivebash
to avoid history expansion).
– Kusalananda
Nov 26 at 13:47
add a comment |
up vote
4
down vote
up vote
4
down vote
The backslash is the escape character to tell the shell not to interpret some special characters. In your case, it escapes the space character.
In shell, a space is normally used to split arguments. Without the backslash, your shell would interpret the space as usually. You would have 2 arguments to your ll
call, which would probably lead to a "File or Directory not found" error.
Alternatively you could surround your argument with quotes:
ll /opt/deployment/release175/war-files files/
ll "/opt/deployment/release175/war-files files/"
ll '/opt/deployment/release175/war-files files/'
Backslash is also used to escape other special characters:
(
$
{
*
#
\
The backslash is the escape character to tell the shell not to interpret some special characters. In your case, it escapes the space character.
In shell, a space is normally used to split arguments. Without the backslash, your shell would interpret the space as usually. You would have 2 arguments to your ll
call, which would probably lead to a "File or Directory not found" error.
Alternatively you could surround your argument with quotes:
ll /opt/deployment/release175/war-files files/
ll "/opt/deployment/release175/war-files files/"
ll '/opt/deployment/release175/war-files files/'
Backslash is also used to escape other special characters:
(
$
{
*
#
\
edited Nov 26 at 13:18
answered Nov 26 at 12:55
RoVo
2,354215
2,354215
... and under some circumstances!
when combined with other characters (interactivebash
to avoid history expansion).
– Kusalananda
Nov 26 at 13:47
add a comment |
... and under some circumstances!
when combined with other characters (interactivebash
to avoid history expansion).
– Kusalananda
Nov 26 at 13:47
... and under some circumstances
!
when combined with other characters (interactive bash
to avoid history expansion).– Kusalananda
Nov 26 at 13:47
... and under some circumstances
!
when combined with other characters (interactive bash
to avoid history expansion).– Kusalananda
Nov 26 at 13:47
add a comment |
up vote
2
down vote
In Unix/Linux (or POSIX), the backslash is an escape character.
In that particular case, the backslash is escaping white space. If it weren't there then the ll
command would attempt to operate on:
/opt/deployment/release175/war-files
and
files/
You can also use double or single quotes
ll "opt/deployment/release175/war-files files/"
ll 'opt/deployment/release175/war-files files/'
The backslash can also be used to escape other special characters with other commands:
rpm -qa | postgre*
grep .regex file
sed 's//this/path//that//path/g'
add a comment |
up vote
2
down vote
In Unix/Linux (or POSIX), the backslash is an escape character.
In that particular case, the backslash is escaping white space. If it weren't there then the ll
command would attempt to operate on:
/opt/deployment/release175/war-files
and
files/
You can also use double or single quotes
ll "opt/deployment/release175/war-files files/"
ll 'opt/deployment/release175/war-files files/'
The backslash can also be used to escape other special characters with other commands:
rpm -qa | postgre*
grep .regex file
sed 's//this/path//that//path/g'
add a comment |
up vote
2
down vote
up vote
2
down vote
In Unix/Linux (or POSIX), the backslash is an escape character.
In that particular case, the backslash is escaping white space. If it weren't there then the ll
command would attempt to operate on:
/opt/deployment/release175/war-files
and
files/
You can also use double or single quotes
ll "opt/deployment/release175/war-files files/"
ll 'opt/deployment/release175/war-files files/'
The backslash can also be used to escape other special characters with other commands:
rpm -qa | postgre*
grep .regex file
sed 's//this/path//that//path/g'
In Unix/Linux (or POSIX), the backslash is an escape character.
In that particular case, the backslash is escaping white space. If it weren't there then the ll
command would attempt to operate on:
/opt/deployment/release175/war-files
and
files/
You can also use double or single quotes
ll "opt/deployment/release175/war-files files/"
ll 'opt/deployment/release175/war-files files/'
The backslash can also be used to escape other special characters with other commands:
rpm -qa | postgre*
grep .regex file
sed 's//this/path//that//path/g'
edited Nov 26 at 17:24
answered Nov 26 at 12:57
Nasir Riley
2,231239
2,231239
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.
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%2f484197%2fbackslash-in-path%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