Sponsored Content
Operating Systems OS X (Apple) Apple scripts and "get from list Post 302553904 by ab52 on Friday 9th of September 2011 06:47:24 AM
Old 09-09-2011
Apple scripts and "get from list

i have this code that i want to run but it is not working

i.e if the user slected say production it will then run the command for production

any ideas what i need to change

Code:
set question to choose from list {"production"}
set answer to question
if answer question is "Production: then 
   tell application "iCal"
       getURL" http:///intranet/prod"
  end tell
end if

 

9 More Discussions You Might Find Interesting

1. News, Links, Events and Announcements

Open Group suing Apple over "Unix"

Our Admin, Neo, has some experience with the subject of this news item: http://news.com.com/2100-1016-1015814.html It appears that The Open Group is suing Apple for using the term Unix without licensing from The Open Group. (3 Replies)
Discussion started by: auswipe
3 Replies

2. UNIX for Dummies Questions & Answers

UNIX Scripts "Load Error" with MicroFocus COBOL subprograms

When running our UNIX job scripts we randomly get the following 198 error below. When we restart the job it works fine. I haven't been able to recreate the problem in test, so I'm wondering if it has something to do with Cron or possibly a memory error or memory leak. I don't see anything... (5 Replies)
Discussion started by: rthiele
5 Replies

3. Shell Programming and Scripting

Joining 3 AWK scripts to avoid use "temp" files

Hi everyone, Looking for a suggestion to improve the below script in which I´ve been working. The thing is I have 3 separated AWK scripts that I need to apply over the inputfile, and for scripts (2) and (3) I have to use a "temp" file as their inputfile (inputfile_temp and inputfile_temp1... (2 Replies)
Discussion started by: cgkmal
2 Replies

4. Shell Programming and Scripting

list all scripts in crontab which contains the string "sqlplus"

Hi folks I use a Solaris 10 box with Bash shell. I have here a script (it works!) to list all scripts in crontab which contains the string "sqlplus": for i in $(ls `crontab -l | grep -v '#' | awk '{ print $6 }' | grep -v '^$'`); do grep -l 'sqlplus' "$i"; done Is there a more elegant... (1 Reply)
Discussion started by: slashdotweenie
1 Replies

5. Ubuntu

Ubuntu Server 10.04 LTS - Regular crontab "caches old scripts"

Hi, I'm using a Ubuntu Server 10.04 LTS and it works like a charm, except for the regular crontab. Onde day a user had some problems with crontab, i analyse it and i see no problemns, all my stuff is working right. Cron is running smoth... I only noticed it when i altered a script already... (2 Replies)
Discussion started by: grafman
2 Replies

6. UNIX for Dummies Questions & Answers

Scripts exists but crontab says "File not found"

Hi All, We have an archiving script on our applications box. It is scheduled to run at 36th minute every hour. 36 * * * * /archive_7.sh But it throws an error saying "sh: /archive_7.sh: not found". I am not able to understand why. # ls -l /archive_7.sh ; file /archive_7.sh -rwxr-xr-x ... (4 Replies)
Discussion started by: satish51392111
4 Replies

7. Shell Programming and Scripting

Read from "list1" and list matches in "list2"

I want to print any matching IP addresse in List1 with List 2; List 1 List of IP addresses; 161.85.58.210 250.57.15.129 217.23.162.249 74.76.129.101 30.221.177.237 3.147.200.59 170.58.142.64 127.65.109.33 150.167.242.146 223.3.20.186 25.181.180.99 2.55.199.32 (3 Replies)
Discussion started by: lewk
3 Replies

8. UNIX for Dummies Questions & Answers

Meaning of "exec 9<name" in scripts

I have found code like exec 9<filename a number of times when looking over commonly used scripts here. What all does this do? Sometimes the filename is simply a list, but seems to always have read/write/execute attributes for all. I think the "<" means to accept this as input, but don't know... (3 Replies)
Discussion started by: wbport
3 Replies

9. Shell Programming and Scripting

Scheduling scripts with "at" command

Hi All , I need to create a scheduling capability on one of Linux boxes so that i could some 6 scripts back to back after a gap a given time difference . To run script1 :-- my test1.sh for 3 hrs , followed by 2nd script ,mytest2.sh for 10 hrs , then mystest3.sh for 2 hrs , then... (3 Replies)
Discussion started by: Anamica
3 Replies
GROG(1)                                                       General Commands Manual                                                      GROG(1)

NAME
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: grog.pl is the Perl version, while grog.sh 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, grog.pl is transformed into grog; otherwise grog.sh is used instead. EXAMPLES
* Calling grog meintro.me results in groff -me meintro.me So grog recognized that the file meintro.me is written with the -me macro package. * On the other hand, grog pic.ms outputs groff -p -t -e -ms pic.ms Besides determining the macro package -ms, grog recognized that the file pic.ms 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 meintro.me pic.ms 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 meintro.me pic.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 <http://www.gnu.org/licenses/gpl-2.0.txt>. AUTHORS
Written by James Clark. Maintained by Werner Lemberg <wl@gnu.org>. Rewritten and put under GPL by Bernd Warken <groff-bernd.warken-72@web.de>. Groff Version 1.22.3 10 February 2018 GROG(1)
All times are GMT -4. The time now is 01:04 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy