synce-registry(1) [debian man page]
SYNCE-REGISTRY(1) http://synce.sourceforge.net/ SYNCE-REGISTRY(1) NAME
synce-registry - read or modify the registry on a PDA SYNOPSIS
synce-registry [-d LEVEL] [-p DEVNAME] [-h] [-r] PARENTKEY KEY VALUE -w [-t TYPE] PARENTKEY KEY VALUE NEWVALUE -l PARENTKEY KEY -n PARENTKEY NEWKEY -x PARENTKEY KEY VALUE (not supported) -X PARENTKEY KEY (not supported) DESCRIPTION
synce-registry manipulates the registry on a device connected through SynCE. It can read and write values, add new keys and values, and list the values of a key. Forward slashes ('/') in key names specified on the command line are converted to backward slashes (''). This tool must be run as the same user as the dccmd daemon. OPTIONS
-d LEVEL Set debug log level: 0 - No logging (default) 1 - Errors only 2 - Errors and warnings 3 - Everything -p DEVNAME Use the device with the given name, instead of the default. -h Display help message. [-r] PARENTKEY KEY VALUE Read a value. This is the default. -w [-t TYPE] PARENTKEY KEY VALUE NEWVALUE Write a value. If TYPE is supplied, that type of value will be written; otherwise a string. The following options are valid for TYPE: sz - String dword - Double-word (4 bytes) dword_bige - Double word (4 bytes), big-endian expand_sz - String with path expansion multi_sz - Multiple strings (not supported) binary - Binary data (not supported) -l PARENTKEY KEY List the names of values and subkeys in the given KEY. -n PARENTKEY KEY Create a new key. -x PARENTKEY KEY VALUE Delete the given VALUE from the given KEY. (not implemented) -X PARENTKEY KEY Delete the given KEY. (not implemented) PARENTKEY The top-level key (sometimes called the hive). The only valid options are HKEY_CLASSES_ROOT (abbreviated HKCR), HKEY_CURRENT_USER (HKCU), HKEY_LOCAL_MACHINE (HKLM), and HKEY_USERS (HKU). KEY The key to operate on. A key can contain zero or more values and subkeys. VALUE The value to operate on. NEWVALUE The new value to set VALUE to in a write operation. AUTHOR
David Eriksson <twogood@users.sourceforge.net>, Scott Gifford <gifford@umich.edu>. SEE ALSO
synce(1) pstatus(1) The SynCE project March 2006 SYNCE-REGISTRY(1)
Check Out this Related Man Page
Jifty::Request::Mapper(3pm) User Contributed Perl Documentation Jifty::Request::Mapper(3pm) NAME
Jifty::Request::Mapper - Maps response values into arbitrary query parameters DESCRIPTION
"Jifty::Request::Mapper" is used to insert values into parameters that you can't know when you originally constructed the request. The prime example of this is a Create action to a View page -- where you can't know what ID to supply to the View page until after the Create action has run. This problem can be fixed by establishing a mapping between some part of the Jifty::Result of the Create action, and the ID query parameter. METHODS
query_parameters HASH Extended syntax for generating query parameters. This is used by Jifty::Web::Form::Clickable for its "parameters" argument, as well as for "results" of continuations. Possible formats for each key => value pair in the "HASH" are: "KEY => STRING" The simplest form -- the "KEY" will have the literal value of the "STRING" supplied "KEY => { result => ACTION }" The "KEY" will take on the value of the content named "KEY" from the result of the "ACTION". "ACTION" may either be a Jifty::Action object, or a moniker thereof. "KEY => { result => ACTION, name => STRING }" The "KEY" will take on the value of the content named "STRING" from the result of the "ACTION". "ACTION" may either be a Jifty::Action object, or a moniker thereof. "KEY => { request_argument => STRING }" The "KEY" will take on the value of the argument named "STRING" from the request. "KEY => { argument => ACTION }" The "KEY" will take on the value of the argument named "KEY" from the "ACTION". "ACTION" may either be a Jifty::Action object, or a moniker thereof. "KEY => { argument => ACTION. name => STRING }" The "KEY" will take on the value of the argument named "STRING" from the "ACTION". "ACTION" may either be a Jifty::Action object, or a moniker thereof. "result_of" and "argument_to" are valid synonyms for "result" and "argument", above. map PARAMHASH Responsible for doing the actual mapping that "query_parameters" above sets up. That is, takes magical query parameters and extracts the values they were meant to have. destination The "key" from a query parameter source The "value" of a query parameter request The Jifty::Request object to pull action arguments from. Defaults to the current request. response The Jifty::Response object to pull results from. Defaults to the current response. Returns a key => value pair. perl v5.14.2 2010-12-08 Jifty::Request::Mapper(3pm)