command-wrapper | A generic wrapper command that delegates to another command
kandi X-RAY | command-wrapper Summary
kandi X-RAY | command-wrapper Summary
command-wrapper is a C library. command-wrapper has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.
The intended use is to reduce the PATH pollution, so that you can quarantine off large applications to their separate "jails" (directories) and only expose the individual command(s) you use on the path. It works by you making a copy of the wrapper executable and giving it the name of a command you’d like to have on the PATH. When you launch the renamed wrapper command it will look for a configuration entry in the file $(HOME)/.command_wrapper (or %HOME%/.command_wrapper on Windows) for an entry with the same name as you gave the copy of the wrapper, read what actual command to call and optionally add any environment variables you may have specified for this specific wrapper.
The intended use is to reduce the PATH pollution, so that you can quarantine off large applications to their separate "jails" (directories) and only expose the individual command(s) you use on the path. It works by you making a copy of the wrapper executable and giving it the name of a command you’d like to have on the PATH. When you launch the renamed wrapper command it will look for a configuration entry in the file $(HOME)/.command_wrapper (or %HOME%/.command_wrapper on Windows) for an entry with the same name as you gave the copy of the wrapper, read what actual command to call and optionally add any environment variables you may have specified for this specific wrapper.
Support
Quality
Security
License
Reuse
Support
command-wrapper has a low active ecosystem.
It has 3 star(s) with 0 fork(s). There are 1 watchers for this library.
It had no major release in the last 6 months.
command-wrapper has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of command-wrapper is current.
Quality
command-wrapper has no bugs reported.
Security
command-wrapper has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
command-wrapper does not have a standard license declared.
Check the repository for any license declaration and review the terms closely.
Without a license, all rights are reserved, and you cannot use the library in your applications.
Reuse
command-wrapper releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of command-wrapper
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of command-wrapper
command-wrapper Key Features
No Key Features are available at this moment for command-wrapper.
command-wrapper Examples and Code Snippets
No Code Snippets are available at this moment for command-wrapper.
Community Discussions
No Community Discussions are available at this moment for command-wrapper.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install command-wrapper
You need to create the file $(HOME)/.command_wrapper and populate it with an entry (a line) for each wrapper name you want to use. The configuration line has the following syntax:. Each environment variable is delimited by a pipe (|) character. If you don’t want to set any environment variables, you don’t specify any pipes either. The pipe delimiter denotes the start of an environment variable, so the rule is to have as many pipe characters as environment variables (to keep it simple).
NAME is the basename of the command you want to wrap (without extension or directory)
ACTUAL_COMMAND is the absolute path (complete file name) for the command the wrapper should launch when invoked.
ENV is zero or more environment variables that you want set before the launching the actual command.
NAME is the basename of the command you want to wrap (without extension or directory)
ACTUAL_COMMAND is the absolute path (complete file name) for the command the wrapper should launch when invoked.
ENV is zero or more environment variables that you want set before the launching the actual command.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page