Hello. I'm learning shell scripting right now and I'm trying simple scripts. I have a problem with the one below. The idea is to found the number of files containing asd in their name. Here's the code:
Code:
#!/bin/sh
pattern=asd
total=0
for f in *
do
[ ! -f "$f" ] && continue
if grep $pattern $f > /dev/null
then
total=`expr $toral + 1`
fi
done
echo "The number of files containing $pattern in their name is $total"
I get an error grep: 3: No such file or directory
Code:
grep: 3~: No such file or directory
and total is always 0. Where is the problem ?
Moderator's Comments:
Please use code tags next time for your code and data.
Last edited by Franklin52; 12-16-2012 at 11:43 AM..
Hi
I would like to know wheather there is anyway to pass a variable to grep argument like this
grep "$myvar" $myfile
i would put this in a function and then call this function by setting different values to myvar and myfile.
is this possible at all.
regards
Hrishy (4 Replies)
I have a large file that I am grepping to find a certain string.
grep 'C:\Data\Directory\Test.txt' test.txt
It can not find it even though I know it is in there . I know that there is a problem with the backslashes but I can't get it to work. I tried
grep... (2 Replies)
Hi there, this is a very simple question.
When I do grep -c "PWD" filename, I get 5. This means the filename contains 5 lines of "PWD" occurence.
I tried to assign to a variable. int= grep -c "PWD" filename
When I typed echo $int
The output:
5
I get an empty line space. Now I... (1 Reply)
I have a problem. Suppose I have a log named transport.log
>>
tp finished with return code: 203
meaning:
wrong syntax in tp call
....
tp finished with return code: 0
meaning:
Everything ok.
<<
What i want to do is to get the return code of the 1st one. So I would probably do:... (2 Replies)
Changed Problem its a sed actually...
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Use a sed command to create an output file from the input file. The input... (2 Replies)
Hi,
When i try this it is not executing either result or total, pls can any one help me in this.
max=month_134.log
grep result|total $max > log.txt
In month_134.log, it should contain either result or total and then send it to log.txt.It should execute result or total in log.txt
... (3 Replies)
Hi
I am trying to grep a string in a directory which is having 5000 files.
PA>> grep -iH 'linc.unisure_pr13n' *
bash: /usr/bin/grep: Arg list too long
I am getting the error. i also tried
PA>> ls -ltr | grep -iH 'linc.unisure_pr13n' *
but still i am getting the error
Please Advice... (4 Replies)
Hi everyone
i am facing a strange problem in grep below is the code
RC=0
grep $ERROR_MASK $LOG_FILE 2>&1 > /dev/null && RC=1 || RC=0
what does the above statment do i mean it search for error mask into log file and redirect the error to console null then what's the meaning of RC=1 ||... (2 Replies)
I have the following ksh
#!/bin/ksh
file=$OBS_APP_PATH/config/com/uhg/obs/inbound/configs/XMLFile_ServiceFeeDetail.xml
echo $file
cntWrd=0
echo $cntWrd
cntWrd= grep -c '<serviceFee>' $file
echo $cntWrd
while executing the above im getting the following error msg:... (2 Replies)
I don't know if you guys get this problem sometimes at Terminal but I had been having this problem since yesterday :( Maybe I overdid the Terminal. Even the codes that used to work doesn't work anymore.
Here is what 's happening:
* I wanted to remove lines containing digits so I used this... (25 Replies)
Discussion started by: Nexeu
25 Replies
LEARN ABOUT DEBIAN
lush
LUSH(1) Lisp Universal Shell LUSH(1)NAME
lush - Lisp Universal Shell
SYNOPSIS
lush [@initfile][lushfile...args...]
DESCRIPTION
lush starts the Lisp Universal Shell.
Lush is an object-oriented Lisp interpreter/compiler with features designed to please people who want to prototype large numerical applica-
tions. Lush includes an extensive library of vector/matrix/tensor manipulation, a set of graphic functions, a simple GUI toolkit, and
interfaces to various libraries such as OpenGL, SDL, the SGI Multimedia library (video/audio grabbing), the Numerical Recipes library, and
others. Lush is an ideal frontend script language for programming projects written in C or other languages.
RUNNING LUSH INTERACTIVELY
Online help on the standard library is available by typing (helptool) at the Lush prompt. You can leave Lush by typing CTRL-D at the
prompt.
On startup, Lush loads various libraries from the sys and lsh directories, as well as a .lushrc file in the user's home directory. It is
recommended to add a directory lsh in your home directory and to include the line (addpath "your-home-directory/lsh") to your .lushrc so
that your own Lush programs are found in Lush's search path.
It is quite convenient to run Lush from within Emacs, which can be done by creating somewhere in your path a symbolic link named "lisp" to
the lush executable. Then, type ESC-X run-lisp in Emacs. It is probably a good idea to add the following line in your .emacs so Emacs
switches to Lisp mode when editing a Lush file:
(setq auto-mode-alist (append (cons ".lsh$" 'lisp-mode) auto-mode-alist))
RUNNING NON-INTERACTIVE LUSH SCRIPTS
In Unix, Lush can be used to write scripts that can be called from a shell prompt (like shell or Perl scripts). A list of command-line
arguments are put in the argv variable.
Here is an example: create a file (say "capargs") with the following content (replacing the first line by the path to your lush exe-
cutable):
#!/bin/sh
exec lush "$0" "$@"
!#
(printf "capitalizing the arguments:0)
(each ((arg argv)) (printf "%s %s0 arg (upcase arg)))
then, make capargs executable: chmod a+x capargs. You can now invoke capargs at the shell prompt:
% capargs asd gfdf
capitalizing the arguments:
capargs CAPARGS
asd ASD
gfdf GFDF
FILES
/usr/share/lush
The top of the Lush directory structure
/usr/share/lush/src
Source code of the interpreter
/usr/share/lush/sys
Core libraries (lush sources) without which Lush cannot run. A minimal/customized version of Lush needs only that directory to run.
/usr/share/lush/etc
Various shell scripts and utilities
/usr/share/lush/include
/usr/share/lush/lsh
Library files (lush sources) that are part of the standard distribution. Although they are not required for Lush to run, life would
really suck without them.
/usr/share/lush/packages
Library files (lush sources) for special applications or platforms, or programs that have been contributed by users and cannot be
assumed to be present/working in all installations of Lush.
/usr/share/lush/local
Lush libraries that are specific to your site.
~/.lushrc
Personal Lush initialization file
~/.lush
Personal Lush directory: on-demand built libraries, etc
HISTORY
Lush is the direct descendant of the SN system. SN was first developed as a neural network simulator with a Lisp-like scripting language.
The project was started in 1987 by Leon Bottou and Yann LeCun, and rewritten several times since then. SN was used at AT&T for many
research projects in machine learning, pattern recognition, and image processing. Its various incarnations were used at AT&T Bell Labs,
AT&T Labs, the Salk Institute, the University of Toronto, Universite of Montreal, UC Berkeley, and many other research institutions. The
commercial versions of SN were used in several large companies as a prototyping tool: Thomson-CSF, ONERA.
SEE ALSO
Use (helptool) in an interactive lush session for browsing of online documentation.
AUTHORS
Lush was written by Leon Bottou and Yann LeCun. Contributors include: Patrice Simard, Yoshua Bengio, Jean Bourrelly, Patrick Haffner, Pas-
cal Vincent, Sergey Ioffe, and many others.
This manual page was written by Kevin Rosenberg <kmr@debian.org> for the Debian Project (but may be used by others).
1.1 2005-12-14 LUSH(1)
12-16-2012
