We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi, I just noticed a small thing. For the command name inputmodule-control, I feel you may be able to rename the command name.
inputmodule-control
For example:
apatchctl
systemctl
/proc/sys
sysctl
So, my suggestion for a command to control Input Module is inputmodulectl or inputmodctl if you can still rename the command name.
inputmodulectl
inputmodctl
So I believe that calling "module" as "mod" is still normal from lsmod command to show the stable of modules in Linux kernel, mod_perl.
lsmod
Anyway, this is a small thing. People can add their alias command such as alias inputmodule-control=inputmodctl in their ~/.bashrc.
alias
alias inputmodule-control=inputmodctl
~/.bashrc
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I just noticed a small thing. For the command name
inputmodule-control
, I feel you may be able to rename the command name.For example:
apatchctl
systemctl
/proc/sys
:sysctl
.So, my suggestion for a command to control Input Module is
inputmodulectl
orinputmodctl
if you can still rename the command name.So I believe that calling "module" as "mod" is still normal from
lsmod
command to show the stable of modules in Linux kernel, mod_perl.Anyway, this is a small thing. People can add their
alias
command such asalias inputmodule-control=inputmodctl
in their~/.bashrc
.The text was updated successfully, but these errors were encountered: