Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Bash : Why are spaces important here ?
Top Forums Shell Programming and Scripting Bash : Why are spaces important here ? Post 302932299 by cfajohnson on Tuesday 20th of January 2015 01:13:18 PM
Old 01-20-2015
Quote:
Originally Posted by Corona688
Code:
$ whereis [

[: /usr/bin/[
$

It's usually a built-in as well, but the command must exist. The shell must treat it as a command.

Rather than whereis, use type; It tells you what the shell will actually use:

Code:
$ type [
[ is a shell builtin

With the -a option, it gives all the possible commands that could be executed:

Code:
$ type -a [
[ is a shell builtin
[ is /usr/bin/[

[ is also a synonym for test.
These 4 Users Gave Thanks to cfajohnson For This Post:
balajesuri John K migurus Scrutinizer
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

bash - add backslash in front of variables w/ spaces

Hello, Im writing a script that works by recursively going into directories with find. But I have some directories that have spaces in them.. so I need to parse the variables to add a backslash before the spaces. Im not exactly sure how how to do this in bash, and honestly I dont think I know... (3 Replies)
Discussion started by: trey85stang
3 Replies

2. Shell Programming and Scripting

bash replace spaces in list.txt with \

I'm trying to run a Linux virus scan on a list of files/folders I have ported to list.txt in a format: some file with spaces some other file but I need to feed my scanning script in the format: some\ file\ with\ spaces/ some\ other\ file/ so I would like to read in list.txt and output... (6 Replies)
Discussion started by: unclecameron
6 Replies

3. Shell Programming and Scripting

white spaces in bash autocompletion

Hello dear community! I've recently written a BASH function for auto completion of options. It works like following: if a user types a command and then an argument to this command which starts with "^-" and then presses TAB, then 'user_command --help (or -h)' is invoked and possible options are... (0 Replies)
Discussion started by: sidorenko
0 Replies

4. Shell Programming and Scripting

[BASH] Allow name with spaces (regex)

Hey all, I have a very simple regular expression that I use when I want to allow only letters with spaces. (I know this regex has a lot of shortcomings, but I'm still trying to learn them) isAlpha='^*$'However, when I bring this over to BASH it doesn't allow me to enter spaces. I use the... (3 Replies)
Discussion started by: whyte_rhyno
3 Replies

5. Shell Programming and Scripting

Bash - read white spaces

Hello! I have one problem with my bash script - I would like to be able to read white space characters from stdin (for example single " ") - can I acomplish that somehow? I need to read only one character at the time, so I use read -s -n 1 var but it doesn't work for whitespaces apparently. ... (3 Replies)
Discussion started by: xqwzts
3 Replies

6. Shell Programming and Scripting

Bash- Command run from script does not pass full parameters with spaces inside

There's a JavaScript file that I call from command line (there's a framework) like so: ./RunDiag.js param1:'string one here' param2:'string two here' I have a shell script where I invoke the above command. I can run it in a script as simple as this #!/bin/bash stuff="./RunDiag.js... (4 Replies)
Discussion started by: AcerAspirant
4 Replies

7. Shell Programming and Scripting

open application with spaces in name [bash][OSX]

Hi guys, I'm new here and new to shell scripting so don't be hard on me I'm trying to create a bash script to restart a process by name in Mac OSX. I have no problem killing the application, the problem comes when launching it again. I managed to store the path in a variable lets say ... (8 Replies)
Discussion started by: jonathanwiesel
8 Replies

8. Shell Programming and Scripting

Dealing with white spaces in bash scripts

I'm trying to search for all files in directory with particular GID then change the GID to match the UID of each file: #!/bin/sh for i in $(find /dump -gid 200 | sed 's/\ /\\\ /g' | sed 's/\&/\\\&/g'); do chgrp $(ls -ln ${i} | awk '{print $3}') ${i} done I'm using sed to deal with... (7 Replies)
Discussion started by: venmx
7 Replies

9. Shell Programming and Scripting

Populating a BASH array with a list of files including spaces-in-the-name

For the record, I already tried telling mgmt and the users to disallow spaces in filenames for this script, but it isn't happening for a number of ID10T-error-based reasons. I have simple list of 3 files in a directory that are named like this: bash-3.2$ ls -1 file* file1 file1 part2... (2 Replies)
Discussion started by: ckmehta
2 Replies

10. Shell Programming and Scripting

Bash script not parsing file with spaces in path

Hi everyone, I'm trying to write my first ever shell script, the OS is Raspbian. The code I have written must be executed whenever a certain database has been modified. The database resides on a Windows server to which I have a mount point, and I have no control over the Windows server at all so... (2 Replies)
Discussion started by: gjws
2 Replies

LEARN ABOUT FREEBSD

whereis

WHEREIS(1)						    BSD General Commands Manual 						WHEREIS(1)

NAME

     whereis -- locate programs

SYNOPSIS

     whereis [-abmqsux] [-BMS dir ... -f] program ...

DESCRIPTION

     The whereis utility checks the standard binary, manual page, and source directories for the specified programs, printing out the paths of any
     it finds.	The supplied program names are first stripped of leading path name components, any single trailing extension added by gzip(1),
     compress(1), or bzip2(1), and the leading 's.' or trailing ',v' from a source code control system.

     The default path searched is the string returned by the sysctl(8) utility for the ``user.cs_path'' string, with /usr/libexec and the current
     user's $PATH appended.  Manual pages are searched by default along the $MANPATH.  Program sources are located in a list of known standard
     places, including all the subdirectories of /usr/src and /usr/ports.

     The following options are available:

     -B      Specify directories to search for binaries.  Requires the -f option.

     -M      Specify directories to search for manual pages.  Requires the -f option.

     -S      Specify directories to search for program sources.  Requires the -f option.

     -a      Report all matches instead of only the first of each requested type.

     -b      Search for binaries.

     -f      Delimits the list of directories after the -B, -M, or -S options, and indicates the beginning of the program list.

     -m      Search for manual pages.

     -q      (``quiet'').  Suppress the output of the utility name in front of the normal output line.	This can become handy for use in a back-
	     quote substitution of a shell command line, see EXAMPLES.

     -s      Search for source directories.

     -u      Search for ``unusual'' entries.  A file is said to be unusual if it does not have at least one entry of each requested type.  Only
	     the name of the unusual entry is printed.

     -x      Do not use ``expensive'' tools when searching for source directories.  Normally, after unsuccessfully searching all the first-level
	     subdirectories of the source directory list, whereis will ask locate(1) to find the entry on its behalf.  Since this can take much
	     longer, it can be turned off with -x.

EXAMPLES

     The following finds all utilities under /usr/bin that do not have documentation:

	   whereis -m -u /usr/bin/*

     Change to the source code directory of ls(1):

	   cd `whereis -sq ls`

SEE ALSO

     find(1), locate(1), man(1), which(1), sysctl(8)

HISTORY

     The whereis utility appeared in 3.0BSD.  This version re-implements the historical functionality that was lost in 4.4BSD.

AUTHORS

     This implementation of the whereis command was written by Jorg Wunsch.

BUGS

     This re-implementation of the whereis utility is not bug-for-bug compatible with historical versions.  It is believed to be compatible with
     the version that was shipping with FreeBSD 2.2 through FreeBSD 4.5 though.

     The whereis utility can report some unrelated source entries when the -a option is specified.

BSD
								  August 22, 2002							       BSD
All times are GMT -4. The time now is 03:42 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy