9 More Discussions You Might Find Interesting
1. Linux
I'm slowly hacking away at a zsh script that shows some promise as a command line tool. I want to learn more about the conventions regarding command line tool development in Unix (and/or macOS), but don't really know where to look for this information.
What is the correct way, or convention, to... (2 Replies)
Discussion started by: MonilGomes
2 Replies
2. Cybersecurity
Hey guys, not sure should I post it here or in 'What is on Your Mind?'
I'm discussing usage of DSL (domain specific language) in security tools with my colleagues. We haven't been able to reach an agreement over naming conventions.
There are many tools using DSL: splunk, sumologic,... (2 Replies)
Discussion started by: Tobby P
2 Replies
3. Web Development
I have been reading up on CSS frameworks, to see if it could be useful for an intranet that I am helping to build, but the true purpose does not become clear to me. What circumstances would the deployment of a CSS framework be useful in? What does a CSS framework do that a CMS template cannot do? (1 Reply)
Discussion started by: figaro
1 Replies
4. UNIX for Dummies Questions & Answers
is there a typographic convention that is followed in the man pages.
where could a description be found.
at this time i am in man stty and the author uses upper case in some places.
and my brain is just burning to a fizzle while studying a book on bash and trying to stay in scope of the... (1 Reply)
Discussion started by: cowLips
1 Replies
5. Web Development
<html>
<head>
<style>
div.box {width: 300px; height: 200px; padding: 30px;
font: 46 pt times new roman;}
</style>
</head>
<body>
<div class="box" style=" filter":
progid:DXImagetransform.Microsoft.Alpha
(Opacity=100,
FinishOpacity=0, Style=1, StartX=0, FinishX=0,... (0 Replies)
Discussion started by: N-Training
0 Replies
6. Programming
C calling convention we all know defines a way how the parameters are pushed onto the stack.
My question is when and how does this C calling conventions matters to a user?
When the user will have to bother about the calling conventions in his project? (5 Replies)
Discussion started by: rupeshkp728
5 Replies
7. UNIX for Dummies Questions & Answers
i was viewing the gawk's man file,checked the man faqs,didnt find anything about the char "e" meaning
.TP
.B \e`
matches the empty string at the beginning of a buffer (string).
.TP
.B \e'
matches the empty string at the end of a buffer.after convention,it should looks like thie
\` ... (2 Replies)
Discussion started by: b33713
2 Replies
8. Solaris
These are findings by me with my little experience with Solaris 10. Please correct me if wrong..
In x86 systems with ide hard disk:
c= controller
d=disk
s=slice
1.Here controller c0 means the primary ide controller ide0.
controller c1 means the secondary ide controller ide1.
... (5 Replies)
Discussion started by: saagar
5 Replies
9. UNIX for Advanced & Expert Users
Hello,
I'm wondering what is the naming conventions for *.so shared libraries in linux. For example, a library in /lib, say libcrypt-2.7.so has a symbolic link called libcrypt.so.1 pointing to it, yet libncursesw.so.5.6 has a symbolic link called libncursesw.so.5 pointing to it. What is the... (2 Replies)
Discussion started by: neked
2 Replies
phpcs(1) General Commands Manual phpcs(1)
NAME
phpcs - php code sniffer cli tool
SYNOPSIS
phpcs [-nwlsapvi] [-d key[=value]] [--report=<report>] [--report-file=<reportfile>] [--report-<report>=<reportfile>] ...
[--report-width=<reportWidth>] [--generator=<generator>] [--tab-width=<tabWidth>] [--severity=<severity>] [--error-severity=<severity>]
[--warning-severity=<severity>] [--config-set key value] [--config-delete key] [--config-show] [--standard=<standard>] [--sniffs=<sniffs>]
[--encoding=<encoding>] [--extensions=<extensions>] [--ignore=<patterns>] <file> ...
DESCRIPTION
phpcs (or PHP_CodeSniffer) is a PHP5 script that tokenises PHP, JavaScript and CSS files to detect violations of a defined coding standard.
It is an essential development tool that ensures your code remains clean and consistent. It can also help prevent some common semantic
errors made by developers.
PARAMETERS
<file>
One or more files and/or directories to check
<extensions>
A comma separated list of file extensions to check (only valid if checking a directory)
<patterns>
A comma separated list of patterns to ignore files and directories
<encoding>
The encoding of the files being checked (default is iso-8859-1)
<sniffs>
A comma separated list of sniff codes to limit the check to (all sniffs must be part of the specified standard)
<severity>
The minimum severity required to display an error or warning
<standard>
The name or path of the coding standard to use
<tabWidth>
The number of spaces each tab represents
<generator>
The name of a doc generator to use (forces doc generation instead of checking)
<report>
Print either the "full", "xml", "checkstyle", "csv", "emacs", "source", "summary", "svnblame", "gitblame" or "hgblame" report (the
"full" report is printed by default)
<reportfile>
Write the report to the specified file path
<reportWidth>
How many columns wide screen reports should be printed
OPTION
-n
Do not print warnings (shortcut for ---warning-severity=0)
-w
Print both warnings and errors (on by default)
-l
Local directory only, no recursion
-s
Show sniff codes in all reports
-a
Run interactively
-p
Show progress of the run
-v[v][v]
Print verbose output
-i
Show a list of installed coding standards
-d
Set the [key] php.ini value to [value] or [true] if -value is omitted
--help
Print the help message
--version
Print version information
phpcs(1)
