TCSH IF syntax issue

Thread Tools Search this Thread
Top Forums Shell Programming and Scripting TCSH IF syntax issue
# 1  
Old 10-24-2013
TCSH IF syntax issue

Hi All,

I'm trying to write a simple if statement in TCSH and I honestly can't figure out what I'm doing wrong. I've played around with all sorts of permutations of syntax.

if ($DESKTOP_SESSION == "kde") then
	replace "forceFontDPI=0" "forceFontDPI=96" -- /home/$USER/.kde/share/config/kcmfonts
	echo "DPI settings have been fixed since you are running KDE."

That block of code results in the following error:
2: Syntax error: word unexpected (expecting "then")

I'm new at shell scripting, especially to TCSH but from what I've read that should work.

Last edited by Corona688; 10-24-2013 at 12:39 PM..
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Dpkg Syntax Issue . . .

Greetings! I'm trying to get dpkg to just completely extract a multi-part *.deb archive set into a single folder called "output". Simple? Hmmmm.... dpkg --noforce --unpack *.deb /output/Console after ops: However, "--noforce" is taken directly from the helpfile Options listing as furnished... (8 Replies)
Discussion started by: LinQ
8 Replies

2. Shell Programming and Scripting

Syntax Issue

Hello all. Need a bit of help... I have : previous_tmp0=`cat tmp0.txt` previous_tmp1=`cat tmp1.txt` previous_tmp2=`cat tmp2.txt` previous_tmp3=`cat tmp3.txt` previous_tmp4=`cat tmp4.txt` previous_tmp5=`cat tmp5.txt` previous_tmp6=`cat tmp6.txt` previous_tmp7=`cat tmp7.txt` Now I... (5 Replies)
Discussion started by: Junaid Subhani
5 Replies

3. Shell Programming and Scripting

syntax issue mysql in bash script

I'm running mysql in a bash script mysql <<EOF query EOF one query is like this: UPDATE $dbname.$prefix"config" SET value = $var WHERE "$prefix" = 'table colname'; with variable but it's giving an error i'm not sure what to put for "$prefix" the table... (3 Replies)
Discussion started by: vanessafan99
3 Replies

4. Shell Programming and Scripting

Syntax error, not understanding the issue?

Close please. Refer to following thread: Sub Menu issues (2 Replies)
Discussion started by: Banned
2 Replies

5. UNIX for Dummies Questions & Answers

issue with my prompt on tcsh

Hi, issue with my prompt, other gets their name, my comes with command number. Why? {118} /home/markb > echo $SHELL /bin/tcsh {119} /home/markb > echo $SHELL /bin/tcsh {120} /home/markb > my .cshrc has this.... set prompt="%{\0330;%n@%M : %~%L \007%} `pwd` >%{\033 ... (3 Replies)
Discussion started by: samnyc
3 Replies

6. Shell Programming and Scripting

expr/bc syntax issue

Hi, I am facing issues in my shell script while trying to add two variables. Look at the snippet below for details: # Initially variable SAMPLE1 and SAMPLE2 are set from different sources. Have trucated decimal to avoid numeric errors in expr SAMPLE1=`/usr/bin/top -n 1 | head -3 | tail -1... (3 Replies)
Discussion started by: animesh303
3 Replies

7. Shell Programming and Scripting

for / foreach syntax issues (in bash or tcsh)

So I am new to unix, and actually anything outside drag and drop with the mouse (been learning for about a week so far) . I have been using the foreach command in tcsh because I am working on a group of files. Basically what I need is to insert part of the filename as the first line in the file.... (0 Replies)
Discussion started by: thepolypore
0 Replies

8. Shell Programming and Scripting

Help with a possiable syntax issue in my script

Hello I have tried to my best ability to work around this script tht will reference my m-names.txt which contains the format of: Then I call a cli named getzoneprof that will set the $subnet from each of the lines in the... (6 Replies)
Discussion started by: richsark
6 Replies

9. Shell Programming and Scripting

Help understanding syntax error Issue

Hi i as you may already know i am creating a menu driven program. I have chosen to take the approach of implementing each interface individually, after adding another interface and attempting to run the program i am faced with the following error: ./Assigntest: line 32: syntax error near... (6 Replies)
Discussion started by: warlock129
6 Replies

10. Shell Programming and Scripting

syntax issue in ksh file

Hi all, I am struck with syntax for long time, Need to purge some lines from given file Not able to use value of $x Example of ksh script... Facing some syntax issue. Have Tried ‘with single , double ,backtick “” ` and \ escape character , doesn't seem to work. <line 1> echo $x #... (2 Replies)
Discussion started by: manav666
2 Replies
Login or Register to Ask a Question
GROG(1)                                                       General Commands Manual                                                      GROG(1)

grog -- guess options for a following groff command SYNOPSIS
grog [-C] [--run] [--warnings] [--ligatures] [ groff-option ....] [--] [ filespec ....] grog -h | --help grog -v | --version DESCRIPTION
grog reads the input (file names or standard input) and guesses which of the groff(1) options are needed to perform the input with the groff program. The corresponding groff command is usually displayed in standard output. With the option --run, the generated line is output into standard error and the generated groff command is run on the standard output. OPTIONS
The option -v or --version prints information on the version number. Also -h or --help prints usage information. Both of these options automatically end the grog program. Other options are thenignored, and no groff command line is generated. The following 3 options are the only grog options, -C this option means enabling the groff compatibility mode, which is also transfered to the generated groff command line. --ligatures this option forces to include the arguments -P-y -PU within the generated groff command line. --run with this option, the command line is output at standard error and then run on the computer. --warnings with this option, some more warnings are output to standard error. All other specified short options (words starting with one minus character -) are interpreted as groff options or option clusters with or without argument. No space is allowed between options and their argument. Except from the -marg options, all options will be passed on, i.e. they are included unchanged in the command for the output without effecting the work of grog. A filespec argument can either be the name of an existing file or a single minus - to mean standard input. If no filespec is specified standard input is read automatically. DETAILS
grog reads all filespec parameters as a whole. It tries to guess which of the following groff options are required for running the input under groff: -e, -g, -G, -j, -J, -p, -R, -s, -t. -man, -mdoc, -mdoc-old, -me, -mm, -mom, and -ms. The guessed groff command including those options and the found filespec parameters is put on the standard output. It is possible to specify arbitrary groff options on the command line. These are passed on the output without change, except for the -marg options. The groff program has trouble when the wrong -marg option or several of these options are specified. In these cases, grog will print an error message and exit with an error code. It is better to specify no -marg option. Because such an option is only accepted and passed when grog does not find any of these options or the same option is found. If several different -marg options are found by grog an error message is produced and the program is terminated with an error code. But the output is written with the wrong options nevertheless. Remember that it is not necessary to determine a macro package. A roff file can also be written in the groff language without any macro package. grog will produce an output without an -marg option. As groff also works with pure text files without any roff requests, grog cannot be used to identify a file to be a roff file. The groffer(1) program heavily depends on a working grog. The grog source contains two files written in different programming languages: is the Perl version, while is a shell script using awk(1). During the run of make(1), it is determined whether the system contains a suitable version of perl(1). If so, is transformed into grog; otherwise is used instead. EXAMPLES
* Calling grog results in groff -me So grog recognized that the file is written with the -me macro package. * On the other hand, grog outputs groff -p -t -e -ms Besides determining the macro package -ms, grog recognized that the file additionally needs -pte, the combination of -p for pic, -t for tbl, and -e for eqn. * If both of the former example files are combined by the command grog an error message is sent to standard error because groff cannot work with two different macro packages: grog: error: there are several macro packages: -me -ms Additionally the corresponding output with the wrong options is printed to standard output: groff -pte -me -ms But the program is terminated with an error code. * The call of grog -ksS -Tdvi grnexmpl.g contains several groff options that are just passed on the output without any interface to grog. These are the option cluster -ksS con- sisting of -k, -s, and -S; and the option -T with argument dvi. The output is groff -k -s -S -Tdvi grnexmpl.g so no additional option was added by grog. As no option -marg was found by grog this file does not use a macro package. SEE ALSO
groff(1), groffer(1) troff(1), tbl(1), pic(1), chem(1), eqn(1), refer(1), grn(1), grap(1), soelim(1) Man-pages of section 1 can be viewed with either $ man name for text mode or $ groffer name for graphical mode (default is PDF mode). groff_me(7), groff_ms(7), groff_mm(7), groff_mom(7), groff_man(7) Man-pages of section 7 can be viewed with either with $ man 7 name for text mode or $ groffer 7 name for graphical mode (default is PDF mode). COPYING
Copyright (C) 1989-2014 Free Software Foundation, Inc. This file is part of grog, which is part of groff, a free software project. You can redistribute it and/or modify it under the terms of the GNU General Public License version 2 (GPL2) as published by the Free Software Foundation. groff is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. The text for GPL2 is available in the internet at GNU copyleft site <>. AUTHORS
Written by James Clark. Maintained by Werner Lemberg <>. Rewritten and put under GPL by Bernd Warken <>. Groff Version 1.22.3 10 February 2018 GROG(1)