Sponsored Content
Top Forums Shell Programming and Scripting how to get the value of a registry using csh script. Post 302813311 by Rashid Khan on Monday 27th of May 2013 04:21:04 AM
Old 05-27-2013
how to get the value of a registry using csh script.

hi,

how to get the value of a registry using csh script.

thanks.
 

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How to change the MTU in Unix registry?

Does anyone know how to or know of a web page where I can find how to change the MTU speed in Unix registry? Any info. would be greatly appreciated. Thanks, Techie (2 Replies)
Discussion started by: Techie_girl
2 Replies

2. UNIX for Dummies Questions & Answers

Comparable registry file in UNIX

Hi all, I am totally new to UNIX. I am currently using converting an existing software package from MFC C++ to wxwindow which allows the software to run under Windows and UNIX. My problem is my existing software package writes to and from the registry. How is this accomplished in UNIX? ... (2 Replies)
Discussion started by: DavidCountry
2 Replies

3. UNIX for Dummies Questions & Answers

about registry and sed command

can someone please explain the sed command and its purpose and an example of its use. Also can you explain the registry thing with an example also. thanks (3 Replies)
Discussion started by: djeung
3 Replies

4. Solaris

Registry analogous in Solaris

Hi, May seem to be an absurd question, still. As we have registry in Windows which keeps track of what is installed and where, what is its analogous thing in Solaris. Is this same in all Unix flavours or different. (4 Replies)
Discussion started by: vibhor_agarwali
4 Replies

5. UNIX for Dummies Questions & Answers

Registry

what Unix systems have for registry? windows have registry. Unix have ??? (1 Reply)
Discussion started by: cs05pp2
1 Replies

6. Shell Programming and Scripting

csh failing to call an 2 embedded csh script

I have an extraordinary problem with a csh script.....(feel free to berate the use of this but I'm modifying an existing bunch of them) Anyway, I have a master csh script which in turn calls a second csh script. This second csh script is below. Within this second script are two compiled C++... (1 Reply)
Discussion started by: pollsizer
1 Replies

7. AIX

How to see a Registry on AIX??

Hi Folks, Could you please help me with the command to find the Registry on AIX machine? For ex in windows we can see a products registry using the REGEDIT....In similar do we have any command for AIX? (1 Reply)
Discussion started by: nvindraneel
1 Replies

8. UNIX for Advanced & Expert Users

Read/update windows registry using UNIX script

Hi, I have a requirement where in to read the registry value of a windows NT based system from a AIX server which should be automatic. For eg. the script should connect to the Win NT system, read the registry as specified on the input and display the output on the AIX screen? Eg. <script... (3 Replies)
Discussion started by: sathish57
3 Replies

9. Shell Programming and Scripting

Why execution is different from orginal bash registry$database?

Hi all, here's my script #!/bin/ksh if then export DB_CREATE_PATH=`pwd` fi echo echo "********************--Menu--*****************************" echo "*** " echo "*** 1. Pre-Upgrade Steps "... (3 Replies)
Discussion started by: jediwannabe
3 Replies
vim-registry(5) 						    vim addons							   vim-registry(5)

NAME
vim-registry - syntax for vim-addons registry files SYNOPSIS
PACKAGE-NAME.yaml DESCRIPTION
A registry file is a multi-document YAML file (i.e. it can be composed by several different YAML documents separated by "---" lines). Each YAML document represents a registry entry, that is the information describing a single addon. Ideally, the registry directory contains one file per package shipping addons; with a filename obeying to the convention PACKAGE-NAME.yaml. Hence a single package can contribute to the registry with multiple entries described in a single YAML file. For example, the "vim-scripts" package should ship a single /usr/share/vim/registry/vim-scripts.yaml file, containing one YAML document per shipped addon. The first lines of such file can look like the following: addon: alternate description: "alternate pairing files (e.g. .c/.h) with short ex-commands" basedir: /usr/share/vim-scripts/ disabledby: "let loaded_alternateFile = 1" files: - plugin/a.vim - doc/alternate.txt --- addon: whatdomain description: "query the meaning of a Top Level Domain" basedir: /usr/share/vim-scripts/ disabledby: "let loaded_whatdomain = 1" files: - plugin/whatdomain.vim --- Each registry entry may contain the following fields, to be typeset according to the YAML specification: addon (Required) Name of the addon. description (Required) Human understandable textual description of the addon. files (Required) List of the files which compose the addon and are required to be present in a component of the Vim runtime path for the addon to be enabled. Each file is specified relative to a component of the Vim runtime path. basedir (Optional) Directory where the files shipped by the addon (i.e., where the symlinks of the user/sysadm should point to) reside on the filesys- tem. Default is /usr/share/vim/addons. disabledby (Optional) Vim script command that can be used (usually by adding it to ~/.vimrc) to prevent the addon from being used even when it is installed. The intended usage of this field is to "blacklist" an undesired addon whose files are available, and hence automatically loaded by Vim, in a component of the Vim runtime path. AUTHOR
James Vega <jamessan@debian.org> SEE ALSO
vim-addons(1), YAML specification <http://www.yaml.org/> COPYRIGHT
Copyright (C) 2010 James Vega This program is free software, you can redistribute it and/or modify it under the terms of the GNU General Public License version 3 as pub- lished by the Free Software Foundation; either version 3 of the License, or (at your option) any later version. Debian Project January 2010 vim-registry(5)
All times are GMT -4. The time now is 07:56 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy