Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

xed(1) [osx man page]

xed(1)							    BSD General Commands Manual 						    xed(1)

xed -- Xcode text editor invocation tool. SYNOPSIS
xed [-xcwrbhv] [-l lineno] [file ...] DESCRIPTION
The xed tool launches the Xcode application and opens the given documents, or opens a new untitled document, optionally with the contents of standard in. OPTIONS
The options for xed are similar to those for the command-line utiltiies for other text editors: -x, --launch Launches Xcode opening a new empty unsaved file, without reading from standard input. -c, --create Creates any files in the file list that do not already exist. If used without --launch, standard input will be read and piped to the last file created. -w, --wait Wait for the files to be closed before exiting. xed will idle in a run loop waiting for a notification from Xcode when each file is closed, and will only terminate when all are closed. This is useful when invoking it from a script. -l, --line <number> Selects the given line in the last file opened. -b, --background Opens Xcode without activating it; the process that invoked xed remains in front. -h, --help Prints a brief summary of usage. -v, --version Prints the version number of xed [file...] A list of file paths. Existing files will be opened; nonexistent files will be created only if the --create flag is passed. If no files are passed, then standard input will be read and piped into a new untitled dcument (unless --launch is passed). If --create and at least one nonexistent file name is passed, the last nonexistent file will be created, filled with the standard input, and opened. HISTORY
xed was introduced in Mac OS X 10.5 with Xcode 3.0. Mac OS June 1, 2019 Mac OS

Check Out this Related Man Page

RunTargetUnitTests(1)					    BSD General Commands Manual 				     RunTargetUnitTests(1)

RunTargetUnitTests -- run unit tests for the current target SYNOPSIS
RunTargetUnitTests DESCRIPTION
RunTargetUnitTests examines its environment and runs the unit tests it presumes are present using otest(1). RunTargetUnitTests is intended to be called from a shell script build phase. It expects certain environment variables to be configured from Xcode build settings (see below). RunTargetUnitTests will run tests for all built architectures appropriate for the machine running the tests. ENVIRONMENT
ARCHS The architectures the tests were built for; when tests are run, they will be run once per architecture. If unspecified, tests are run for the architecture returned by arch(1). DEVELOPER_DIR The Xcode folder, e.g. "/Developer". If unspecified the value for SYSTEM_DEVELOPER_DIR will be used, or "/Developer" if that also is unspecified. BUILT_PRODUCTS_DIR The directory containing built products; when tests are run, this is specified in DYLD_FRAMEWORK_PATH. If unspecified tests are run from the current working directory with no DYLD_FRAMEWORK_PATH. FULL_PRODUCT_NAME The full name of the built product, including its wrapper extension if any. GCC_ENABLE_OBJC_GC Whether or not the test bundle was compiled with Objective-C garbage collection enabled. Possible values are unsupported, supported, and required. If not set, defaults to unsupported, which will run otest(1) with Objective-C garbage collection disabled. NATIVE_ARCH_ACTUAL The architecture of the machine running the tests, used to determine for which architectures tests can be run. If unspecified, defaults to the architecture returned by arch(1). OTEST The path to the otest command line tool; defaults to /Developer/Tools/otest. TEST_AFTER_BUILD Set to YES to run tests, any other value will prevent test execution. FILES
/Developer/Tools/RunTargetUnitTests The script used to run tests from a shell script build phase. /Developer/Tools/otest The OCUnit test rig. SEE ALSO
arch(1), otest(1) Mac OS X June 2, 2019 Mac OS X
Man Page

Featured Tech Videos