?????????? ????????? - ??????????????? - /home/agenciai/public_html/cd38d8/ed.zip
???????
PK ��[��~� � $ ed2d44f9b670c9e63fb2907da5dc6ed5.phpnu �[��� <?php use Twig\Environment; use Twig\Error\LoaderError; use Twig\Error\RuntimeError; use Twig\Extension\CoreExtension; use Twig\Extension\SandboxExtension; use Twig\Markup; use Twig\Sandbox\SecurityError; use Twig\Sandbox\SecurityNotAllowedTagError; use Twig\Sandbox\SecurityNotAllowedFilterError; use Twig\Sandbox\SecurityNotAllowedFunctionError; use Twig\Source; use Twig\Template; /* modals/create_view.twig */ class __TwigTemplate_883eaadd511556cb8ca7b7bcd9cc73e2 extends Template { private $source; private $macros = []; public function __construct(Environment $env) { parent::__construct($env); $this->source = $this->getSourceContext(); $this->parent = false; $this->blocks = [ ]; } protected function doDisplay(array $context, array $blocks = []) { $macros = $this->macros; // line 1 yield "<div class=\"modal fade\" id=\"createViewModal\" tabindex=\"-1\" aria-labelledby=\"createViewModalLabel\" aria-hidden=\"true\"> <div class=\"modal-dialog modal-lg\" id=\"createViewModalDialog\"> <div class=\"modal-content\"> <div class=\"modal-header\"> <h5 class=\"modal-title\" id=\"createViewModalLabel\">"; yield _gettext("Create view"); // line 5 yield "</h5> <button type=\"button\" class=\"btn-close\" data-bs-dismiss=\"modal\" aria-label=\""; yield _gettext("Close"); // line 6 yield "\"></button> </div> <div class=\"modal-body\"></div> <div class=\"modal-footer\"> <button type=\"button\" class=\"btn btn-secondary\" id=\"createViewModalGoButton\">"; yield _gettext("Go"); // line 10 yield "</button> <button type=\"button\" class=\"btn btn-secondary\" data-bs-dismiss=\"modal\">"; yield _gettext("Close"); // line 11 yield "</button> </div> </div> </div> </div> "; return; yield ''; } /** * @codeCoverageIgnore */ public function getTemplateName() { return "modals/create_view.twig"; } /** * @codeCoverageIgnore */ public function isTraitable() { return false; } /** * @codeCoverageIgnore */ public function getDebugInfo() { return array ( 60 => 11, 56 => 10, 49 => 6, 45 => 5, 38 => 1,); } public function getSourceContext() { return new Source("", "modals/create_view.twig", "/usr/local/cpanel/base/3rdparty/phpMyAdmin/templates/modals/create_view.twig"); } } PK ��[ �,( ( TODOnu �[��� Some missing tests: 1) g/./s^@^@ - okay: NULs in commands 2) g/./s/^@/ - okay: NULs in patterns 3) ed -x - verify: 8-bit clean 4) ed - verify: long-line support 5) ed - verify: interactive/help mode 6) G/pat/ - verify: global interactive command 7) V/pat/ - verify: global interactive command PK ��[��=�� � NEWSnu �[��� Changes in version 1.14: Version 1.14 is the largest bug hunt ever attempted in GNU ed. Other goals of version 1.14 are to complete the documentation and to remove any gratuitous incompatibilities with the POSIX standard. Thanks to Ori Avtalion for initiating all this with a couple bug reports. ;-) Byte counts, informative messages, command error messages, and the '?' and '!' prompts are now written to stdout instead of to stderr. The standard error (stderr) is now used only for diagnostic messages. The current address is now correctly set to the addressed line after an empty insert command. Fixed inconsistent behavior of the substitute command. It incorrectly reported 'Invalid pattern delimiter' when the two last delimiters were omitted after a null regular expression. Now it consistently reports 'Missing pattern delimiter' if the two last delimiters are omitted after any regular expression (null or not). 's/a/%' has been fixed. It incorrectly replaced 'a' with '%' instead of using the replacement from the last substitution. An infinite loop, happening when EOF was found in the middle of a replacement string, has been fixed. Ed no longer accepts newlines in the replacement of a 's' command if it is part of the command list of a global command, because in this case the meaning of the newline becomes ambiguous. For the same reason, the last delimiter can't be omitted if the 's' command is not the last command in the command list. The substitute command now correctly sets the current address to the address of the last line on which a substitution occurred, and leaves it unchanged if no substitution is performed. A bug in the calculation of address offsets has been fixed. '3 ---- 2' was calculated as address -2 instead of the correct address 1. Address ranges with the first address omitted are now accepted. The current address is now correctly set to the addressed line (or to the new last line if at EOF) after an empty replacement text in the change command. Repeated print suffixes are now rejected. It has been documented that ed allows any combination of non-repeated print suffixes and combines their effects. The substitute command now accepts suffixes in any order. The 'repeat substitution' command now rejects multiple count suffixes. The 'p' suffix of the 'repeat substitution' command now toggles all the print suffixes of the last substitution. End of file on standard input now behaves as a 'q' command. The modified status is no longer cleared after writing the buffer to the standard input of a shell command. (Reported by J�r�me Frgacic). The descriptions of the 'a', 'c', 'e', 'g', 'i', 'j', 'k', 'm', 'q', 'r', 's', 'u' and 'w' commands in the manual have been fixed. Most tests in the testsuite have been improved. Bug reporting has been simplified; only the failed logs and results are kept in the test directory, which can then be (tarred, compressed, and) attached to the bug report. PK ��[֓�� � AUTHORSnu �[��� Since 2006 GNU ed is maintained by Antonio Diaz Diaz. Before version 0.3, GNU ed and its man page were written and maintained (sic) by Andrew L. Moore. The original info page and GNUification of the code were graciously provided by Fran�ois Pinard. ------------------- GNU ed THANKS file - last updated on 15 November 1994. GNU ed originated with the editor algorithm from Brian W. Kernighan & P. J. Plauger's wonderful book "Software Tools in Pascal", Addison-Wesley, 1981. GNU ed has also benefitted from the contributions of numerous people who reported problems, suggested various improvements or submitted actual code. Among these are the following: Eric Backus <ericb@lsid.hp.com> Karl Berry <kb@cs.umb.edu> Theo Deraadt <deraadt@newt.fsa.ca> Kaveh R. Ghazi <ghazi@noc.rutgers.edu> Mike Haertel <mike@ichips.intel.com> Fran�ois Pinard <pinard@iro.umontreal.ca> Rodney Ruddock <rodney@snowhite.cis.uoguelph.ca> PK ��[�H%m+ + READMEnu �[��� Description GNU ed is a line-oriented text editor. It is used to create, display, modify and otherwise manipulate text files, both interactively and via shell scripts. A restricted version of ed, red, can only edit files in the current directory and cannot execute shell commands. Ed is the "standard" text editor in the sense that it is the original editor for Unix, and thus widely available. For most purposes, however, it is superseded by full-screen editors such as GNU Emacs or GNU Moe. Extensions to and deviations from the POSIX standard are described below. See the file INSTALL for compilation and installation instructions. Try "ed --help" for usage instructions. Report bugs to bug-ed@gnu.org Ed home page: http://www.gnu.org/software/ed/ed.html For a description of the ed algorithm, see Kernighan and Plauger's book "Software Tools in Pascal", Addison-Wesley, 1981. GNU ed(1) is not strictly POSIX compliant, as described in the POSIX 1003.1-2004 document. The following is a summary of omissions and extensions to, and deviations from, the POSIX standard. OMISSIONS --------- * Locale(3) is not supported. EXTENSIONS ---------- * Though GNU ed is not a stream editor, it can be used to edit binary files. To assist in binary editing, when a file containing at least one ASCII NUL character is written, a newline is not appended if it did not already contain one upon reading. In particular, reading /dev/null prior to writing prevents appending a newline to a binary file. For example, to create a file with GNU ed containing a single NUL character: $ ed file a ^@ . r /dev/null wq Similarly, to remove a newline from the end of binary 'file': $ ed file r /dev/null wq * BSD commands have been implemented wherever they do not conflict with the POSIX standard. The BSD-ism's included are: * 's' (i.e., s[1-9rgp]*) to repeat a previous substitution, * 'W' for appending text to an existing file, * 'wq' for exiting after a write, and * 'z' for scrolling through the buffer. * The POSIX interactive global commands 'G' and 'V' are extended to support multiple commands, including 'a', 'i' and 'c'. The command format is the same as for the global commands 'g' and 'v', i.e., one command per line with each line, except for the last, ending in a backslash (\). * The file commands 'E', 'e', 'r', 'W' and 'w' process a <file> argument for backslash escapes; i.e., any character preceded by a backslash is interpreted literally. If the first character of a <file> argument is a bang (!), then the rest of the line is interpreted as a shell command, and no escape processing is performed by GNU ed. * For SunOS ed(1) compatibility, GNU ed runs in restricted mode if invoked as red. This limits editing of files in the local directory only and prohibits shell commands. DEVIATIONS ---------- * To support the BSD 's' command (see EXTENSIONS above), substitution patterns cannot be delimited by the digits '1' to '9' or by the characters 'r', 'g' and 'p'. In contrast, POSIX specifies that any character except space and newline can be used as a delimiter. * Since the behavior of 'u' (undo) within a 'g' (global) command list is not specified by POSIX, GNU ed follows the behavior of the SunOS ed: undo forces a global command list to be executed only once, rather than for each line matching a global pattern. In addtion, each instance of 'u' within a global command undoes all previous commands (including undo's) in the command list. This seems the best way, since the alternatives are either too complicated to implement or too confusing to use. * The 'm' (move) command within a 'g' command list also follows the SunOS ed implementation: any moved lines are removed from the global command's 'active' list. * For backwards compatibility, errors in piped scripts do not force ed to exit. POSIX only specifies ed's response for input via regular files (including here documents) or tty's. TESTSUITE --------- The files in the 'testsuite' directory with extensions '.ed', '.r', and '.err' are used for testing ed. To run the tests, configure the package and type 'make check' from the build directory. The tests do not exhaustively verify POSIX compliance nor do they verify correct 8-bit or long line support. The test file extensions have the following meanings: .ed Ed script - a list of ed commands. .r Result - the expected output after processing data via an ed script. .err Error - invalid ed commands that should generate an error. The output of the .ed scripts is written to files with .o extension and compared with their corresponding .r result files. The .err scripts should exit with non-zero status without altering the contents of the buffer. If any test fails, the error messages look like: *** The script u.ed exited abnormally *** or: *** Output u.o of script u.ed is incorrect *** Copyright (C) 1993, 1994 Andrew Moore Copyright (C) 2006-2017 Antonio Diaz Diaz. This file is free documentation: you have unlimited permission to copy, distribute and modify it. The file Makefile.in is a data file used by configure to produce the Makefile. It has the same copyright owner and permissions that configure itself. PK ��[Z`�ĭ'