As much as I would like to help, you lost me. I can't possibly imagine what you want to achieve, coming from where.
Pls post directory structure (as you want that looong path included), algorithms to calculate the varns, an input file sample, and from that concoction the desired output.
EDIT: This may fulfill part of your requirements:
EDIT 2: put sub (/[^\/]*$/, ",&",FILENAME); in front of the print FILENAME.
I need help with a problem that I have not been able to figure out.
I have a file that is about 650K lines. Records are seperated by
blank lines, fields seperated by new lines. I was trying to make
a report that would add up 2 fields and associate them with a CP.
example output would be... (11 Replies)
I have a log file that has many SQL statements/queries/blocks and their resultant output (success or failure) added to each of them. I need to pick up all the statements which caused errors and write them to a separate file.
On most cases, the SQL statement is a single line, like DROP . And if... (1 Reply)
I don't know if this is a big issue or not, but I'm having difficulties. I apoligize for the upcoming essay :o.
I'm writing a script, similar to a paint program that edits images, but in the form of ANSI block characters. The program so far is working. I managed to save the image into a file,... (14 Replies)
hello,
i have a complex awk problem...
i have two tables, one with a value (0 to 1) and it's corresponding p-value, like this:
1. table:
______________________________
value p-value
... ...
0.254 0.003
0.245 0.005
0.233 0.006
... ...
______________________________
and a... (6 Replies)
I have a awk script that parses many millions of lines so performance is critical. At one point I am extracting some variables from a space delimited string.
alarm = $11; len = split(alarm,a," "); ent = a; chem = a; for (i = 5; i<= len; i++) {chem = chem " " a}It works but is slow. Adding the... (7 Replies)
Hello fellow unix geeks,
I am having a small dilemna trying to parse a log file I have. Below is a sample of what it will look like:
MY_TOKEN1(group) TOKEN(other)|SSID1
MY_TOKEN2(group, group2)|SSID2
What I need to do is only keep the MY_TOKEN pieces and where there are multiple... (7 Replies)
Discussion started by: dagamier
7 Replies
LEARN ABOUT OSX
info
INFO(1) User Commands INFO(1)NAME
info - read Info documents
SYNOPSIS
info [OPTION]... [MENU-ITEM...]
DESCRIPTION
Read documentation in Info format.
OPTIONS --apropos=STRING
look up STRING in all indices of all manuals.
-d, --directory=DIR
add DIR to INFOPATH.
--dribble=FILENAME
remember user keystrokes in FILENAME.
-f, --file=FILENAME
specify Info file to visit.
-h, --help
display this help and exit.
--index-search=STRING
go to node pointed by index entry STRING.
-n, --node=NODENAME
specify nodes in first visited Info file.
-o, --output=FILENAME
output selected nodes to FILENAME.
-R, --raw-escapes
output "raw" ANSI escapes (default).
--no-raw-escapes
output escapes as literal text.
--restore=FILENAME
read initial keystrokes from FILENAME.
-O, --show-options, --usage
go to command-line options node.
--subnodes
recursively output menu items.
-w, --where, --location
print physical location of Info file.
--vi-keys
use vi-like and less-like key bindings.
--version
display version information and exit.
The first non-option argument, if present, is the menu entry to start from; it is searched for in all `dir' files along INFOPATH. If it is
not present, info merges all `dir' files and shows the result. Any remaining arguments are treated as the names of menu items relative to
the initial node visited.
EXAMPLES
info show top-level dir menu
info emacs
start at emacs node from top-level dir
info emacs buffers
start at buffers node within emacs manual
info --show-options emacs
start at node with emacs' command line options
info -f ./foo.info
show file ./foo.info, not searching dir
REPORTING BUGS
Email bug reports to bug-texinfo@gnu.org, general questions and discussion to help-texinfo@gnu.org. Texinfo home page:
http://www.gnu.org/software/texinfo/
COPYRIGHT
Copyright (C) 2004 Free Software Foundation, Inc. There is NO warranty. You may redistribute this software under the terms of the GNU
General Public License. For more information about these matters, see the files named COPYING.
info 4.8 December 2004 INFO(1)