09-03-2002
Quote:
difference between "find ." and "find /"
Basically the "
." says `From here` or your current working directory. The "
/" indicates that you wish to start searching from the root directory (top of the directory tree).
Hope that helps.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I need help with the syntax to serach a directory and all the folders in that directorys for a single pdf file. I would than like to move that file to another folder. I don't know if this is possible with one command. Please Help. (2 Replies)
Discussion started by: johnlong
2 Replies
2. UNIX for Dummies Questions & Answers
I am accessing a UNIX server via FTP. I want to retieve a file in a directory. What is the UNIX command that I need to view and retrieve files from a directory? (1 Reply)
Discussion started by: yodaddy
1 Replies
3. UNIX for Dummies Questions & Answers
Hi,
i want to search a file in the dir , if file exists for todays date print the message that file found or if file does not exist for todays date/ if file not found i want to display message saying that file not found. How to do this.
Thx for your help. (2 Replies)
Discussion started by: nick12
2 Replies
4. UNIX for Dummies Questions & Answers
I am trying to find the list of printers(names) in the network from unix server.
can anybody help me . I need the command.
Thanks in advance.
:) (2 Replies)
Discussion started by: vijisenthil
2 Replies
5. Shell Programming and Scripting
Hi
1)How do i find files in unix that end either in .pc or .h
This does not return any output
find . -name "*(pc|h)"
2)I have a file like this
001123456
..
...
i want the output to be like
001-123-456 any tricks in regular expression can do this in vi.
regards
Hrishy (7 Replies)
Discussion started by: xiamin
7 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I have here a hard drive from a computer that was damaged, and now the costumer needs the data on the hard drive, but doesn't have any other computer to read data.
I don't really know what file system is on the disk.
How can I find out what file system is on the disk so I can read the... (4 Replies)
Discussion started by: dmarques
4 Replies
7. UNIX for Dummies Questions & Answers
Is there a way to find out all users and the UNIX groups they belong to??
:) (3 Replies)
Discussion started by: Hangman2
3 Replies
8. Shell Programming and Scripting
I need to check for username that we are logged in.There are a lot of unix users and proceed according to that
i.e
find unix user
if
then echo "x"
elif
then echo "y'
fi
fi
Now I dont know how to find and put user in if condition (8 Replies)
Discussion started by: sriki32
8 Replies
9. Homework & Coursework Questions
how can i find related pattern in a text file without using grep command in unix (2 Replies)
Discussion started by: feint
2 Replies
10. UNIX for Advanced & Expert Users
Hi,
Suppose I have a file with many lines as follows. Now I want to find the following questions from the file through shell script or commands.
My name is XYZ. XYZ works for GHT and XYZ is part of PES. GHT is a good organization. XYZ knows swimming. XYZ is also very keen in reading. XYZ is a... (2 Replies)
Discussion started by: sktkpl
2 Replies
LEARN ABOUT XFREE86
git-ls-tree
GIT-LS-TREE(1) Git Manual GIT-LS-TREE(1)
NAME
git-ls-tree - List the contents of a tree object
SYNOPSIS
git ls-tree [-d] [-r] [-t] [-l] [-z]
[--name-only] [--name-status] [--full-name] [--full-tree] [--abbrev[=<n>]]
<tree-ish> [<path>...]
DESCRIPTION
Lists the contents of a given tree object, like what "/bin/ls -a" does in the current working directory. Note that:
o the behaviour is slightly different from that of "/bin/ls" in that the <path> denotes just a list of patterns to match, e.g. so
specifying directory name (without -r) will behave differently, and order of the arguments does not matter.
o the behaviour is similar to that of "/bin/ls" in that the <path> is taken as relative to the current working directory. E.g. when you
are in a directory sub that has a directory dir, you can run git ls-tree -r HEAD dir to list the contents of the tree (that is sub/dir
in HEAD). You don't want to give a tree that is not at the root level (e.g. git ls-tree -r HEAD:sub dir) in this case, as that would
result in asking for sub/sub/dir in the HEAD commit. However, the current working directory can be ignored by passing --full-tree
option.
OPTIONS
<tree-ish>
Id of a tree-ish.
-d
Show only the named tree entry itself, not its children.
-r
Recurse into sub-trees.
-t
Show tree entries even when going to recurse them. Has no effect if -r was not passed. -d implies -t.
-l, --long
Show object size of blob (file) entries.
-z
line termination on output and do not quote filenames. See OUTPUT FORMAT below for more information.
--name-only, --name-status
List only filenames (instead of the "long" output), one per line.
--abbrev[=<n>]
Instead of showing the full 40-byte hexadecimal object lines, show only a partial prefix. Non default number of digits can be specified
with --abbrev=<n>.
--full-name
Instead of showing the path names relative to the current working directory, show the full path names.
--full-tree
Do not limit the listing to the current working directory. Implies --full-name.
[<path>...]
When paths are given, show them (note that this isn't really raw pathnames, but rather a list of patterns to match). Otherwise
implicitly uses the root level of the tree as the sole path argument.
OUTPUT FORMAT
<mode> SP <type> SP <object> TAB <file>
This output format is compatible with what --index-info --stdin of git update-index expects.
When the -l option is used, format changes to
<mode> SP <type> SP <object> SP <object size> TAB <file>
Object size identified by <object> is given in bytes, and right-justified with minimum width of 7 characters. Object size is given only for
blobs (file) entries; for other entries - character is used in place of size.
Without the -z option, pathnames with "unusual" characters are quoted as explained for the configuration variable core.quotePath (see git-
config(1)). Using -z the filename is output verbatim and the line is terminated by a NUL byte.
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-LS-TREE(1)