[ { "path": ".devcontainer/devcontainer.json", "content": "// https://aka.ms/devcontainer.json\n{\n \"name\": \"txt2regex dev\",\n \"image\": \"ghcr.io/aureliojargas/devcontainer\",\n //\n // https://aka.ms/vscode-remote/containers/non-root\n \"remoteUser\": \"vscode\",\n //\n // https://github.com/devcontainers/features/tree/main/src\n \"features\": {\n \"github-cli\": \"latest\",\n // Some Makefile commands are run inside a Docker container\n \"docker-in-docker\": \"latest\"\n }\n}\n" }, { "path": ".github/workflows/check.yml", "content": "# https://docs.github.com/en/actions/reference\n\nname: Check\non:\n push:\n pull_request:\njobs:\n\n lint:\n runs-on: ubuntu-22.04\n steps:\n - uses: actions/checkout@v2\n - run: sudo snap install shfmt\n - run: make lint\n\n test:\n runs-on: ubuntu-22.04\n steps:\n - uses: actions/checkout@v2\n # See https://github.com/aureliojargas/txt2regex/pull/9 on why we're\n # using env in the next command\n - run: env --default-signal=PIPE make test\n - run: make test-bash\n - run: make test-regex\n\n - name: The repository must remain unchanged after the checks\n run: |\n git diff\n git diff-index --exit-code HEAD\n" }, { "path": "CHANGELOG.md", "content": "# Changelog for txt2regex\n\nAll notable changes to this project will be documented in this file.\n\nThe format is based on [Keep a Changelog].\n\n[Keep a Changelog]: https://keepachangelog.com/en/1.0.0/\n\n[Unreleased]: https://github.com/aureliojargas/txt2regex/compare/v0.9...HEAD\n[Version 0.9]: https://github.com/aureliojargas/txt2regex/releases/tag/v0.9\n[Version 0.8]: https://github.com/aureliojargas/txt2regex/releases/tag/v0.8\n[Version 0.7]: https://github.com/aureliojargas/txt2regex/releases/tag/v0.7\n[Version 0.6]: https://github.com/aureliojargas/txt2regex/releases/tag/v0.6\n[Version 0.5]: https://github.com/aureliojargas/txt2regex/releases/tag/v0.5\n[Version 0.4]: https://github.com/aureliojargas/txt2regex/releases/tag/v0.4\n[Version 0.3.1]: https://github.com/aureliojargas/txt2regex/releases/tag/v0.3.1\n[Version 0.3]: https://github.com/aureliojargas/txt2regex/releases/tag/v0.3\n[Version 0.2]: https://github.com/aureliojargas/txt2regex/releases/tag/v0.2\n[Version 0.1]: https://github.com/aureliojargas/txt2regex/releases/tag/v0.1\n\n[#12]: https://github.com/aureliojargas/txt2regex/pull/12\n[#9]: https://github.com/aureliojargas/txt2regex/pull/9\n[#7]: https://github.com/aureliojargas/txt2regex/pull/7\n[#6]: https://github.com/aureliojargas/txt2regex/pull/6\n[#5]: https://github.com/aureliojargas/txt2regex/pull/5\n[#3]: https://github.com/aureliojargas/txt2regex/pull/3\n\n[307ae9a]: https://github.com/aureliojargas/txt2regex/commit/307ae9a\n[d0c6254]: https://github.com/aureliojargas/txt2regex/commit/d0c6254\n[bee846a]: https://github.com/aureliojargas/txt2regex/commit/bee846a\n[dbcd055]: https://github.com/aureliojargas/txt2regex/commit/dbcd055\n[f1d80c9]: https://github.com/aureliojargas/txt2regex/commit/f1d80c9\n[0a7127a]: https://github.com/aureliojargas/txt2regex/commit/0a7127a\n[1660d83]: https://github.com/aureliojargas/txt2regex/commit/1660d83\n[61abe24]: https://github.com/aureliojargas/txt2regex/commit/61abe24\n[3a3fd24]: https://github.com/aureliojargas/txt2regex/commit/3a3fd24\n[8e1f6ea]: https://github.com/aureliojargas/txt2regex/commit/8e1f6ea\n[4b98e2b]: https://github.com/aureliojargas/txt2regex/commit/4b98e2b\n[f5d0125]: https://github.com/aureliojargas/txt2regex/commit/f5d0125\n[d7850d2]: https://github.com/aureliojargas/txt2regex/commit/d7850d2\n[f323926]: https://github.com/aureliojargas/txt2regex/commit/f323926\n[190906c]: https://github.com/aureliojargas/txt2regex/commit/190906c\n[2768584]: https://github.com/aureliojargas/txt2regex/commit/2768584\n[4b41298]: https://github.com/aureliojargas/txt2regex/commit/4b41298\n[7a1b0cb]: https://github.com/aureliojargas/txt2regex/commit/7a1b0cb\n[674d7bb]: https://github.com/aureliojargas/txt2regex/commit/674d7bb\n[bee220c]: https://github.com/aureliojargas/txt2regex/commit/bee220c\n[a3f7fef]: https://github.com/aureliojargas/txt2regex/commit/a3f7fef\n[c084ed8]: https://github.com/aureliojargas/txt2regex/commit/c084ed8\n\n\n## [Unreleased]\n\n### Added\n\n- CI: Now also run the tests for Bash version 5.1 [307ae9a]\n\n### Changed\n\n- CI: Moved from Travis CI to GitHub Actions [#9]\n\n### Fixed\n\n- Fixed to work properly in Bash 5.2 (thanks Nick Rosbrook) [#12]\n\n\n## [Version 0.9] released in 2020-05-21\n\n### Added\n\n- Added CHICKEN Scheme regexes (thanks Mario Domenech Goulart)\n [dbcd055], [f1d80c9]\n- New tests for all the command line options (`tests/cmdline.md`)\n- New tests for txt2regex features (`tests/features.md`) [#5]\n- New regex tester that runs the supported programs in a Docker\n container. Using specially crafted regexes, it verifies how the\n programs behave in \"real life\". This avoids manual testing or reading\n the program documentation to get regex-related information\n (`tests/regex-tester.sh`) [#6]\n- New automatic testing in all Bash versions from 3.0 to 5.0, to make\n sure txt2regex works in all of them (`make test-bash`)\n- Now using Travis CI to run all the tests at every push to the GitHub\n repository\n- New Makefile targets to perform common tasks: `check`, `fmt`,\n `install-bin`, `install-mo`, `lint`, `test`, `test-bash`,\n `test-regex`, `test-regex-build`, `test-regex-shell`\n- Added short options `-h` (for `--help`) and `-V` (for `--version`)\n [0a7127a], [1660d83]\n\n### Removed\n\n- Removed Lisp regexes (choose Emacs and/or CHICKEN Scheme instead)\n- Removed OpenOffice.org regexes (not supported by the new regex tester)\n- Removed VBScript regexes (not supported by the new regex tester)\n- Removed the old regex tester `test-suite/*`\n- Removed `tools/bashdump-rmdup.sh` since `msguniq` has the same\n functionality\n- Removed the NEWS file for not adding too much value over the changelog\n\n### Changed\n\n- Bumped minimal required Bash version from 2.04 to 3.0 [d0c6254]\n- Bumped the versions for all the supported programs [#7]\n- Validated and updated the regex data for all the supported programs,\n thanks to the new regex tester. Some programs now support new\n metacharacters, while others got updates on the escaping rules and\n POSIX character classes support [#7]\n- JavaScript regexes: now using Node.js instead of Netscape [61abe24]\n- lex regexes: now using GNU flex [3a3fd24]\n- PHP regexes: switch from old `ereg` to `preg` (PCRE) [8e1f6ea]\n- Changed the default programs: +egrep +grep +emacs -perl -php -postgres\n- Remove repeated characters inside a list `[]` (if the user has typed\n `abbbca`, make it `[abc]`) [4b98e2b]\n- Now `--showmeta` also shows the version for each program [d7850d2]\n- Now the \"!! not supported\" legend only appears when there are\n unsupported metacharacters in the current regex [f323926]\n- Converted everything (code, docs, translations) to UTF-8\n- Improved the source code quality (`shellcheck`) and formatting\n (`shfmt`)\n- Unset `$PATH` in the top of the script to make sure only Bash builtin\n commands are used [bee846a]\n- Simplified the man page contents [f5d0125]\n- i18n: Improve some translatable strings to make them shorter and\n easier to translate\n- Moved the project hosting from SourceForge to GitHub\n- Converted this changelog to the [Keep a Changelog] format\n\n### Fixed\n\n- Fixed to work properly in bash5 (thanks Yanmarshus Bachtiar) [190906c]\n- Fixed `eval` bug when running in bash3 or newer (thanks Marcus\n Habermehl) [2768584]\n- Fixed incorrect metacharacters for `?` and `+` showing up for `vi` in\n `--showmeta` and `--showinfo` [c084ed8]\n- Fixed the escaping of the `}` character to be matched as a literal\n- Fixed the escaping of the `\\` character to be matched as a literal,\n for programs that use `\\\\` for escaping: before: `\\\\\\`, now: `\\\\\\\\`\n [4b41298]\n- Fixed the escaping of the `\\` character when inside a list `[]`\n [a3f7fef]\n- Fixed the handling of the `[` character when inside a list `[]`: it is\n not special at all and should not be handled [7a1b0cb]\n- Fixed the handling of the `^` character when inside a list `[]`: only\n move it to the end when it is in the first position [674d7bb]\n- Fixed the handling of the `-` character when inside a list `[]`: do\n not move it to the end when it is in the first position, since it is\n not special there [bee220c]\n\n### Translations\n\n- Added Turkish translations provided by erayalakese [#3]\n- Added Catalan translations provided by Carles (ChAoS)\n- Added French translations provided by wwp\n\n## [Version 0.8] released in 2004-09-28\n\n### Added\n\n- Added OpenOffice.org regexes support\n\n### Changed\n\n- Documentation updated: cleaner README and new man page contents\n\n### Fixed\n\n- Fixed bash version test, now works on bash 3.0 and newer (thanks Rene\n Engelhard)\n- Fixed sed script bug on `procmail-re-test` (thanks JulioB @ caltech)\n\n### Translations\n\n- Added Romanian translations provided by Robert Claudiu Gheorghe\n- Added Spanish translations provided by Diego Moya Velázquez\n- Added Italian translations provided by Daniele Pizzolli and\n revised by Marco Pagnanini\n\n## [Version 0.7] released in 2002-03-04\n\n### Added\n\n- Groups are now quantifiable, i.e. `(foo|bar){1,5}`\n- New option `--prog` to choose which programs to show the regexes for\n- New option `--make` to automatically compose regexes for common\n patterns: date, hour, number\n- New option `--version` to show the txt2regex version\n- Added the \"Really quit?\" confirmation (thanks Martin Butterwecki)\n- Added man page (thanks Martin Butterwecki)\n\n### Fixed\n\n- Fixed Makefile bug on `DESTDIR` (thanks Martin Butterwecki)\n\n### Translations\n\n- Added Japanese translations provided by Hajime Dei\n\n## [Version 0.6] released in 2001-09-05\n\n- Added (group|and|alternation) support\n- Added groups balance check -> `(((3)))`\n- Added MySQL regexes support\n- Option `--history` now supports all the txt2regex features\n- Added German translations provided by Jan Parthey\n\n## [Version 0.5] released in 2001-08-28\n\n- New option `--showmeta` to print a complete metacharacters table\n- New option `--showinfo` to print regex-related information about a\n program\n\n## [Version 0.4] released in 2001-08-02\n\n- Added JavaScript regexes support\n- Added PostgreSQL regexes support\n- Added procmail regexes support\n- Added VBScript regexes support\n- New `procmail-re-test` utility to test the procmail regexes from the\n command line\n- Test-suite improved and now included on the tarball\n- Updated Polish translations\n\n## [Version 0.3.1] released in 2001-06-26\n\n- Now using a custom `sek()` function instead of the `seq` command, thus\n removing the last external (non-bash-builtin) command from txt2regex\n- Updated Indonesian translation\n- Updated Polish translation\n\n## [Version 0.3] released in 2001-06-13\n\n- Added support for localized POSIX character classes `[[:abc:]]`\n- Added support for special user combinations inside lists `[]`\n- New option `--whitebg` to adjust the colors for white background\n terminals\n- Improve the final human sentence with more detailed data\n- Remove the usage of the `clear` and `stty` commands, because they are\n not Bash builtin commands (and txt2regex strives to be 100% Bash\n builtins powered)\n- The project is now hosted at SourceForge\n- Added Polish translations provided by Chris Piechowicz\n\n## [Version 0.2] released in 2001-04-24\n\n- Changed project name from txt2regexp to txt2regex\n- New option `--history` to \"replay\" from history data a regex\n previously composed in txt2regex\n- New option `--nocolor` to not use colors in the interface\n- New dynamic history for user input:\n `.oO(history)(¤user_input1¤userinput2¤...)`\n- Added Indonesian (Bahasa) translations provided by Muhamad Faizal\n\n## [Version 0.1] released in 2001-02-23\n\n- Initial release (as txt2regexp)\n" }, { "path": "CONTRIBUTING.md", "content": "# Contributing to txt2regex\n\nPlease follow the usual GitHub workflow to contribute to this project:\n\n- Use [GitHub issues](https://github.com/aureliojargas/txt2regex/issues) for bug reports and feature requests.\n\n- Use GitHub pull requests to submit code and translations.\n\n## Guidelines\n\nThe following guidelines are reminders for the future me (the author), because I cannot hold all of that information in my head. You, as a contributor, are not required to follow them (but thanks if you do).\n\n- Keep the current code style (even if you find it odd)\n\n- Keep the code formatted (`make fmt`) and validated (`make lint`)\n\n- Do not use any system command, this is a Bash builtins script\n\n- Do not use any Bash feature that is not supported by the old minimal version txt2regex supports (see https://mywiki.wooledge.org/BashFAQ/061)\n\n- Do not use `echo`, use `printf`\n\n- Always use `[` instead of `test` in `txt2regex.sh`\n\n- Use `-eq` and `-ne` instead of `==` and `!=` for numeric tests\n\n- Use `-n` and `-z` when testing variables for emptiness\n\n- Always use `$\"...\"` for strings that the user will see (i18n)\n\n- Think about translations, keep strings short and direct\n\n- Update the man page when there are relevant changes\n\n- Update the Changelog when there are relevant changes\n\n- New files should always be UTF-8\n\n## Testing\n\nAll tests must always be successful. The CI will refuse changes that break tests.\n\n- Add/update tests in `tests/*.md` when adding/updating features\n\n- Make sure all the tests are passing: `make test`\n\n- Make sure it's working in all the supported Bash versions: `make test-bash`\n\n- When touching the regex tester, run it (`make test-regex`) and check the `regex-tester.txt` contents for changes\n\n- Do some manual testing to make sure the interactive usage is ok\n\n## Releasing\n\n- Make sure all the tests are passing (see previous topic)\n\n- Make sure the manual page contents is up-to-date with the current code and regenerate it with `make doc`\n\n- Make sure the Changelog is up-to-date, containing all the relevant changes since the last released version\n\n- In the `TODO` file, is there anything to be added/removed?\n\n- In the `README.md` file, is there anything to be added/removed?\n\n- Update the `po/*.{po,pot}` files to match the current code: run `make po` and commit\n\n- Create the official release commit:\n\n - Update the version number in `txt2regex.sh` and `Makefile`\n - Update the version number in `tests/cmdline.md`\n - Update the version number and creation date in the potfile: `make pot`\n - Update the man page date to the release date and regenerate it: `make doc`\n - Update the changelog with the version number and release date\n - Remember to update the \"compare\" links at the top\n - Rerun the tests, just in case: `make check`\n - Commit\n - Tag this commit with the version number\n - Example: https://github.com/aureliojargas/txt2regex/commit/be3e0fa\n\n- Publish the release: `git push && git push --tags`\n\n- Get back to the development version:\n - Update the version number in `txt2regex.sh` and `Makefile`\n - Use `version+1` and add the `b` suffix (for beta)\n - Example: https://github.com/aureliojargas/txt2regex/commit/193c011\n\n## History rewrite\n\nIn 2020-05-19 the whole Git history for this repository was rewritten. It was necessary to set the correct date for the initial commits, so they reflect the official release date for the releases.\n\nBefore:\n\n 699db55 2012-12-21 adding txt2regex version 0.1 (2001-02-23)\n fb48115 2012-12-21 Revert \"adding txt2regex version 0.1 (2001-02-23)\"\n 1a45c22 2012-12-21 add txt2regex version 0.1 (2001-02-23)\n 961f8fa 2012-12-21 Program renamed from txt2regexp to txt2regex\n f4ac6e7 2012-12-21 Add txt2regex version 0.2 (2001-04-24)\n 4c037d1 2012-12-21 Renamed file: id.po => id_ID.po\n 7c4de30 2012-12-21 Add txt2regex version 0.3 (2001-06-13)\n 5d56afd 2012-12-21 Add txt2regex version 0.3.1 (2001-06-26)\n 92c7677 2012-12-21 Add txt2regex version 0.4 (2001-08-02)\n cd23c57 2012-12-21 Add txt2regex version 0.5 (2001-08-28)\n 4b572b5 2012-12-21 Add txt2regex version 0.6 (2001-09-05)\n 20ac0f5 2012-12-21 Add txt2regex version 0.7 (2002-03-04)\n 6fe0ae8 2012-12-21 Add txt2regex version 0.8 (2004-09-28)\n 3bbfa3b 2012-12-21 Add txt2regex version 0.9 beta (unreleased)\n\nAfter:\n\n f17f458 2001-02-22 Initial commit\n 2f066eb 2001-02-22 Remove empty README\n eff18e0 2001-02-23 Add txt2regex version 0.1 (2001-02-23)\n 5f685c5 2001-04-24 Program renamed from txt2regexp to txt2regex\n da3e729 2001-04-24 Add txt2regex version 0.2 (2001-04-24)\n db8a71e 2001-06-13 Renamed file: id.po => id_ID.po\n 6fa7545 2001-06-13 Add txt2regex version 0.3 (2001-06-13)\n 98c60e8 2001-06-26 Add txt2regex version 0.3.1 (2001-06-26)\n f2acfd3 2001-08-02 Add txt2regex version 0.4 (2001-08-02)\n bdd05d1 2001-08-28 Add txt2regex version 0.5 (2001-08-28)\n 7e9159f 2001-09-05 Add txt2regex version 0.6 (2001-09-05)\n b8b618a 2002-03-04 Add txt2regex version 0.7 (2002-03-04)\n 8d96c9a 2004-09-28 Add txt2regex version 0.8 (2004-09-28)\n 2768584 2012-12-21 Add txt2regex version 0.9 beta (unreleased)\n\nNote that the initial commit was also fixed, instead of the old weird revert.\n\nAll of the existing Git tags (`v0.1`, `v0.2`, ...) were updated to point to the new commits.\n\nAnother change in this rewrite was the removal (not the revert) of the commit that added the `releases/` folder with all the `.tgz` files from all the releases (until v0.8):\n\n 2a113fe 2013-09-22 Add new 'releases' folder with TGZ files\n\nThat was a bad idea. GitHub already provides automatic `.zip` and `.tar.gz` files for every tagged commit. Since all of those first commits were created by expanding the tarballs from the official releases, the GitHub ones should be equal.\n\nThe old `master` branch was saved as the `master-until-2020-05-19` branch.\n\nAll the pull requests until number 7 are now referencing not the `master` commits, but those in the `master-until-2020-05-19` branch.\n\nI know this is a total mess. I'm sorry for that. But I think having the official dates for the commits of the old versions is important. Now the \"Releases\" listing in GitHub has the correct dates.\n" }, { "path": "COPYRIGHT", "content": " GNU GENERAL PUBLIC LICENSE\n Version 2, June 1991\n\n Copyright (C) 1989, 1991 Free Software Foundation, Inc.,\n 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA\n Everyone is permitted to copy and distribute verbatim copies\n of this license document, but changing it is not allowed.\n\n Preamble\n\n The licenses for most software are designed to take away your\nfreedom to share and change it. By contrast, the GNU General Public\nLicense is intended to guarantee your freedom to share and change free\nsoftware--to make sure the software is free for all its users. This\nGeneral Public License applies to most of the Free Software\nFoundation's software and to any other program whose authors commit to\nusing it. (Some other Free Software Foundation software is covered by\nthe GNU Lesser General Public License instead.) You can apply it to\nyour programs, too.\n\n When we speak of free software, we are referring to freedom, not\nprice. Our General Public Licenses are designed to make sure that you\nhave the freedom to distribute copies of free software (and charge for\nthis service if you wish), that you receive source code or can get it\nif you want it, that you can change the software or use pieces of it\nin new free programs; and that you know you can do these things.\n\n To protect your rights, we need to make restrictions that forbid\nanyone to deny you these rights or to ask you to surrender the rights.\nThese restrictions translate to certain responsibilities for you if you\ndistribute copies of the software, or if you modify it.\n\n For example, if you distribute copies of such a program, whether\ngratis or for a fee, you must give the recipients all the rights that\nyou have. You must make sure that they, too, receive or can get the\nsource code. And you must show them these terms so they know their\nrights.\n\n We protect your rights with two steps: (1) copyright the software, and\n(2) offer you this license which gives you legal permission to copy,\ndistribute and/or modify the software.\n\n Also, for each author's protection and ours, we want to make certain\nthat everyone understands that there is no warranty for this free\nsoftware. If the software is modified by someone else and passed on, we\nwant its recipients to know that what they have is not the original, so\nthat any problems introduced by others will not reflect on the original\nauthors' reputations.\n\n Finally, any free program is threatened constantly by software\npatents. We wish to avoid the danger that redistributors of a free\nprogram will individually obtain patent licenses, in effect making the\nprogram proprietary. To prevent this, we have made it clear that any\npatent must be licensed for everyone's free use or not licensed at all.\n\n The precise terms and conditions for copying, distribution and\nmodification follow.\n\n GNU GENERAL PUBLIC LICENSE\n TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION\n\n 0. This License applies to any program or other work which contains\na notice placed by the copyright holder saying it may be distributed\nunder the terms of this General Public License. The \"Program\", below,\nrefers to any such program or work, and a \"work based on the Program\"\nmeans either the Program or any derivative work under copyright law:\nthat is to say, a work containing the Program or a portion of it,\neither verbatim or with modifications and/or translated into another\nlanguage. (Hereinafter, translation is included without limitation in\nthe term \"modification\".) Each licensee is addressed as \"you\".\n\nActivities other than copying, distribution and modification are not\ncovered by this License; they are outside its scope. The act of\nrunning the Program is not restricted, and the output from the Program\nis covered only if its contents constitute a work based on the\nProgram (independent of having been made by running the Program).\nWhether that is true depends on what the Program does.\n\n 1. You may copy and distribute verbatim copies of the Program's\nsource code as you receive it, in any medium, provided that you\nconspicuously and appropriately publish on each copy an appropriate\ncopyright notice and disclaimer of warranty; keep intact all the\nnotices that refer to this License and to the absence of any warranty;\nand give any other recipients of the Program a copy of this License\nalong with the Program.\n\nYou may charge a fee for the physical act of transferring a copy, and\nyou may at your option offer warranty protection in exchange for a fee.\n\n 2. You may modify your copy or copies of the Program or any portion\nof it, thus forming a work based on the Program, and copy and\ndistribute such modifications or work under the terms of Section 1\nabove, provided that you also meet all of these conditions:\n\n a) You must cause the modified files to carry prominent notices\n stating that you changed the files and the date of any change.\n\n b) You must cause any work that you distribute or publish, that in\n whole or in part contains or is derived from the Program or any\n part thereof, to be licensed as a whole at no charge to all third\n parties under the terms of this License.\n\n c) If the modified program normally reads commands interactively\n when run, you must cause it, when started running for such\n interactive use in the most ordinary way, to print or display an\n announcement including an appropriate copyright notice and a\n notice that there is no warranty (or else, saying that you provide\n a warranty) and that users may redistribute the program under\n these conditions, and telling the user how to view a copy of this\n License. (Exception: if the Program itself is interactive but\n does not normally print such an announcement, your work based on\n the Program is not required to print an announcement.)\n\nThese requirements apply to the modified work as a whole. If\nidentifiable sections of that work are not derived from the Program,\nand can be reasonably considered independent and separate works in\nthemselves, then this License, and its terms, do not apply to those\nsections when you distribute them as separate works. But when you\ndistribute the same sections as part of a whole which is a work based\non the Program, the distribution of the whole must be on the terms of\nthis License, whose permissions for other licensees extend to the\nentire whole, and thus to each and every part regardless of who wrote it.\n\nThus, it is not the intent of this section to claim rights or contest\nyour rights to work written entirely by you; rather, the intent is to\nexercise the right to control the distribution of derivative or\ncollective works based on the Program.\n\nIn addition, mere aggregation of another work not based on the Program\nwith the Program (or with a work based on the Program) on a volume of\na storage or distribution medium does not bring the other work under\nthe scope of this License.\n\n 3. You may copy and distribute the Program (or a work based on it,\nunder Section 2) in object code or executable form under the terms of\nSections 1 and 2 above provided that you also do one of the following:\n\n a) Accompany it with the complete corresponding machine-readable\n source code, which must be distributed under the terms of Sections\n 1 and 2 above on a medium customarily used for software interchange; or,\n\n b) Accompany it with a written offer, valid for at least three\n years, to give any third party, for a charge no more than your\n cost of physically performing source distribution, a complete\n machine-readable copy of the corresponding source code, to be\n distributed under the terms of Sections 1 and 2 above on a medium\n customarily used for software interchange; or,\n\n c) Accompany it with the information you received as to the offer\n to distribute corresponding source code. (This alternative is\n allowed only for noncommercial distribution and only if you\n received the program in object code or executable form with such\n an offer, in accord with Subsection b above.)\n\nThe source code for a work means the preferred form of the work for\nmaking modifications to it. For an executable work, complete source\ncode means all the source code for all modules it contains, plus any\nassociated interface definition files, plus the scripts used to\ncontrol compilation and installation of the executable. However, as a\nspecial exception, the source code distributed need not include\nanything that is normally distributed (in either source or binary\nform) with the major components (compiler, kernel, and so on) of the\noperating system on which the executable runs, unless that component\nitself accompanies the executable.\n\nIf distribution of executable or object code is made by offering\naccess to copy from a designated place, then offering equivalent\naccess to copy the source code from the same place counts as\ndistribution of the source code, even though third parties are not\ncompelled to copy the source along with the object code.\n\n 4. You may not copy, modify, sublicense, or distribute the Program\nexcept as expressly provided under this License. Any attempt\notherwise to copy, modify, sublicense or distribute the Program is\nvoid, and will automatically terminate your rights under this License.\nHowever, parties who have received copies, or rights, from you under\nthis License will not have their licenses terminated so long as such\nparties remain in full compliance.\n\n 5. You are not required to accept this License, since you have not\nsigned it. However, nothing else grants you permission to modify or\ndistribute the Program or its derivative works. These actions are\nprohibited by law if you do not accept this License. Therefore, by\nmodifying or distributing the Program (or any work based on the\nProgram), you indicate your acceptance of this License to do so, and\nall its terms and conditions for copying, distributing or modifying\nthe Program or works based on it.\n\n 6. Each time you redistribute the Program (or any work based on the\nProgram), the recipient automatically receives a license from the\noriginal licensor to copy, distribute or modify the Program subject to\nthese terms and conditions. You may not impose any further\nrestrictions on the recipients' exercise of the rights granted herein.\nYou are not responsible for enforcing compliance by third parties to\nthis License.\n\n 7. If, as a consequence of a court judgment or allegation of patent\ninfringement or for any other reason (not limited to patent issues),\nconditions are imposed on you (whether by court order, agreement or\notherwise) that contradict the conditions of this License, they do not\nexcuse you from the conditions of this License. If you cannot\ndistribute so as to satisfy simultaneously your obligations under this\nLicense and any other pertinent obligations, then as a consequence you\nmay not distribute the Program at all. For example, if a patent\nlicense would not permit royalty-free redistribution of the Program by\nall those who receive copies directly or indirectly through you, then\nthe only way you could satisfy both it and this License would be to\nrefrain entirely from distribution of the Program.\n\nIf any portion of this section is held invalid or unenforceable under\nany particular circumstance, the balance of the section is intended to\napply and the section as a whole is intended to apply in other\ncircumstances.\n\nIt is not the purpose of this section to induce you to infringe any\npatents or other property right claims or to contest validity of any\nsuch claims; this section has the sole purpose of protecting the\nintegrity of the free software distribution system, which is\nimplemented by public license practices. Many people have made\ngenerous contributions to the wide range of software distributed\nthrough that system in reliance on consistent application of that\nsystem; it is up to the author/donor to decide if he or she is willing\nto distribute software through any other system and a licensee cannot\nimpose that choice.\n\nThis section is intended to make thoroughly clear what is believed to\nbe a consequence of the rest of this License.\n\n 8. If the distribution and/or use of the Program is restricted in\ncertain countries either by patents or by copyrighted interfaces, the\noriginal copyright holder who places the Program under this License\nmay add an explicit geographical distribution limitation excluding\nthose countries, so that distribution is permitted only in or among\ncountries not thus excluded. In such case, this License incorporates\nthe limitation as if written in the body of this License.\n\n 9. The Free Software Foundation may publish revised and/or new versions\nof the General Public License from time to time. Such new versions will\nbe similar in spirit to the present version, but may differ in detail to\naddress new problems or concerns.\n\nEach version is given a distinguishing version number. If the Program\nspecifies a version number of this License which applies to it and \"any\nlater version\", you have the option of following the terms and conditions\neither of that version or of any later version published by the Free\nSoftware Foundation. If the Program does not specify a version number of\nthis License, you may choose any version ever published by the Free Software\nFoundation.\n\n 10. If you wish to incorporate parts of the Program into other free\nprograms whose distribution conditions are different, write to the author\nto ask for permission. For software which is copyrighted by the Free\nSoftware Foundation, write to the Free Software Foundation; we sometimes\nmake exceptions for this. Our decision will be guided by the two goals\nof preserving the free status of all derivatives of our free software and\nof promoting the sharing and reuse of software generally.\n\n NO WARRANTY\n\n 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY\nFOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN\nOTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES\nPROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED\nOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF\nMERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS\nTO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE\nPROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,\nREPAIR OR CORRECTION.\n\n 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING\nWILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR\nREDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,\nINCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING\nOUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED\nTO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY\nYOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER\nPROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE\nPOSSIBILITY OF SUCH DAMAGES.\n\n END OF TERMS AND CONDITIONS\n\n How to Apply These Terms to Your New Programs\n\n If you develop a new program, and you want it to be of the greatest\npossible use to the public, the best way to achieve this is to make it\nfree software which everyone can redistribute and change under these terms.\n\n To do so, attach the following notices to the program. It is safest\nto attach them to the start of each source file to most effectively\nconvey the exclusion of warranty; and each file should have at least\nthe \"copyright\" line and a pointer to where the full notice is found.\n\n \n Copyright (C) \n\n This program is free software; you can redistribute it and/or modify\n it under the terms of the GNU General Public License as published by\n the Free Software Foundation; either version 2 of the License, or\n (at your option) any later version.\n\n This program is distributed in the hope that it will be useful,\n but WITHOUT ANY WARRANTY; without even the implied warranty of\n MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n GNU General Public License for more details.\n\n You should have received a copy of the GNU General Public License along\n with this program; if not, write to the Free Software Foundation, Inc.,\n 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.\n\nAlso add information on how to contact you by electronic and paper mail.\n\nIf the program is interactive, make it output a short notice like this\nwhen it starts in an interactive mode:\n\n Gnomovision version 69, Copyright (C) year name of author\n Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.\n This is free software, and you are welcome to redistribute it\n under certain conditions; type `show c' for details.\n\nThe hypothetical commands `show w' and `show c' should show the appropriate\nparts of the General Public License. Of course, the commands you use may\nbe called something other than `show w' and `show c'; they could even be\nmouse-clicks or menu items--whatever suits your program.\n\nYou should also get your employer (if you work as a programmer) or your\nschool, if any, to sign a \"copyright disclaimer\" for the program, if\nnecessary. Here is a sample; alter the names:\n\n Yoyodyne, Inc., hereby disclaims all copyright interest in the program\n `Gnomovision' (which makes passes at compilers) written by James Hacker.\n\n , 1 April 1989\n Ty Coon, President of Vice\n\nThis General Public License does not permit incorporating your program into\nproprietary programs. If your program is a subroutine library, you may\nconsider it more useful to permit linking proprietary applications with the\nlibrary. If this is what you want to do, use the GNU Lesser General\nPublic License instead of this License.\n" }, { "path": "Makefile", "content": "NAME = txt2regex\nVERSION = 0.10b\nBASHVERSIONS = 3.0 3.1 3.2 4.0 4.1 4.2 4.3 4.4 5.0 5.1\nREGEXTESTERIMAGE = aureliojargas/regex-tester:2020-05-09\n\nSCRIPT = $(NAME).sh\nPODIR = po\nPOTFILE = $(PODIR)/$(NAME).pot\n\nDESTDIR =\nBINDIR = $(DESTDIR)/usr/bin\nLOCALEDIR = $(DESTDIR)/usr/share/locale\nMANDIR = $(DESTDIR)/usr/share/man/man1\n\n.PHONY: check check-po clean doc fmt install install-bin \\\n install-mo lint mo po pot test test-bash test-regex \\\n test-regex-build test-regex-shell\n\n#-----------------------------------------------------------------------\n# Dev\n\ncheck: lint test\n\nfmt:\n\tshfmt -w -i 4 -ci -sr $(SCRIPT) tests/regex-tester.sh\n\nlint:\n\tshellcheck $(SCRIPT) tests/regex-tester.sh\n\tshfmt -d -i 4 -ci -sr $(SCRIPT) tests/regex-tester.sh\n\ntest: clitest.sh\n\tsh clitest.sh --progress none README.md tests/*.md\n\n# Run the tests in multiple Bash versions, using the official Docker\n# image https://hub.docker.com/_/bash (each image is ~10MB).\n# Early exit the loop in the first error, otherwise only the last loop\n# iteration would count as the exit state for this target.\ntest-bash: clitest.sh\n\t@for v in $(BASHVERSIONS); do \\\n\t\tprintf '\\nTesting in Bash version %s\\n' $$v; \\\n\t\tdocker run --rm -v $$PWD:/code -w /code bash:$$v \\\n\t\t\tsh clitest.sh --progress none tests/*.md || exit 1; \\\n\tdone\n\n# Run regex tests for the supported programs, inside a Docker container\ntest-regex:\n\t# Explicit pull to make sure all the log messages from the pulling\n\t# process appear here, and not when executing the next \"docker run\",\n\t# whose output goes directly to the .txt file.\n\tdocker image inspect $(REGEXTESTERIMAGE) >/dev/null 2>&1 || \\\n\tdocker pull $(REGEXTESTERIMAGE)\n\n\t# Test all programs except \"vi\"\n\tdocker run --rm -v \"$$PWD\":/code -w /code $(REGEXTESTERIMAGE) \\\n\t\ttests/regex-tester.sh --skip vi > tests/regex-tester.txt 2>&1\n\n\t# vi: no stderr redirect to avoid \"inappropriate ioctl for device\"\n\t# vi: docker run -t adds a trailing \\r to every line :/\n\tdocker run --rm -v \"$$PWD\":/code -w /code -t $(REGEXTESTERIMAGE) \\\n\t\ttests/regex-tester.sh vi | tr -d '\\r' >> tests/regex-tester.txt\n\ntest-regex-shell:\n\tdocker run --rm -v \"$$PWD\":/code -w /code -it $(REGEXTESTERIMAGE)\n\ntest-regex-build:\n\tdocker build -t $(REGEXTESTERIMAGE) tests/\n\nclean:\n\trm -f $(NAME) clitest.sh txt2tags.py messages.mo tmp.lex.*\n\trm -f $(PODIR)/messages $(PODIR)/*.mo $(PODIR)/*.tmp $(PODIR)/*~\n\trm -rf $(PODIR)/??/ $(PODIR)/??_??/\n\ndoc: txt2tags.py\n\tpython3 ./txt2tags.py -t man man/txt2regex.t2t\n\tpython3 ./txt2tags.py -t html man/txt2regex.t2t\n\nclitest.sh:\n\tcurl -s -L -o $@ \\\n\thttps://raw.githubusercontent.com/aureliojargas/clitest/master/clitest\n\ntxt2tags.py:\n\tcurl -s -L -o $@ \\\n\thttps://raw.githubusercontent.com/aureliojargas/txt2tags/3.4/txt2tags.py\n\n#-----------------------------------------------------------------------\n# Translation files\n#\n# Learn more: http://pology.nedohodnik.net/doc/user/en_US/ch-poformat.html\n# Example potfile: http://git.savannah.gnu.org/cgit/gawk.git/tree/po/gawk.pot\n\npot:\n\t@date=`date '+%Y-%m-%d %H:%M %Z'`; \\\n\t( \\\n\t\tprintf '%s\\n' '#, fuzzy'; \\\n\t\tprintf '%s\\n' 'msgid \"\"'; \\\n\t\tprintf '%s\\n' 'msgstr \"\"'; \\\n\t\tprintf '\"%s\"\\n' 'Project-Id-Version: $(NAME) $(VERSION)\\n'; \\\n\t\tprintf '\"%s\"\\n' \"POT-Creation-Date: $$date\\n\"; \\\n\t\tprintf '\"%s\"\\n' 'PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\\n'; \\\n\t\tprintf '\"%s\"\\n' 'Last-Translator: FULL NAME \\n'; \\\n\t\tprintf '\"%s\"\\n' 'MIME-Version: 1.0\\n'; \\\n\t\tprintf '\"%s\"\\n' 'Content-Type: text/plain; charset=UTF-8\\n'; \\\n\t\tprintf '\"%s\"\\n' 'Content-Transfer-Encoding: 8bit\\n'; \\\n\t\tbash --dump-po-strings $(SCRIPT); \\\n\t) | msguniq --no-wrap --sort-by-file -o $(POTFILE); \\\n\tprintf '%s was generated\\n' $(POTFILE)\n\npo: pot\n\t@for pofile in $(PODIR)/*.po; do \\\n\t\tprintf 'Merging %s...' $$pofile; \\\n\t\tmsgmerge --update --sort-by-file --no-wrap --previous \\\n\t\t\t$$pofile $(POTFILE); \\\n\tdone; \\\n\tprintf 'Remember to grep for the fuzzy messages in all .po files\\n'\n\nmo:\n\t@for pofile in $(PODIR)/*.po; do \\\n\t\tprintf 'Compiling %s... ' $$pofile; \\\n\t\tmsgfmt -o $${pofile%.po}.mo $$pofile && \\\n\t\techo ok; \\\n\tdone\n\ncheck-po:\n\t@for pofile in $(PODIR)/*.po; do \\\n\t\tprintf 'Checking %s...' $$pofile; \\\n\t\tmsgfmt --verbose $$pofile || exit 1; \\\n\tdone\n\n#-----------------------------------------------------------------------\n# Release\n\ninstall: install-mo install-bin\n\ninstall-mo: mo\n\ttest -d $(LOCALEDIR) || mkdir -p $(LOCALEDIR); \\\n\tfor mofile in $(PODIR)/*.mo; do \\\n\t\tmoinstalldir=$(LOCALEDIR)/`basename $$mofile .mo`/LC_MESSAGES; \\\n\t\ttest -d $$moinstalldir || mkdir -p $$moinstalldir; \\\n\t\tinstall -m644 $$mofile $$moinstalldir/$(NAME).mo; \\\n\tdone\n\ninstall-bin:\n\ttest -d $(BINDIR) || mkdir -p $(BINDIR); \\\n\tsed -e '/^TEXTDOMAINDIR=/s,=.*,=$(LOCALEDIR),' \\\n\t\t$(SCRIPT) > $(BINDIR)/$(NAME) && \\\n\tchmod +x $(BINDIR)/$(NAME) && \\\n\tprintf '\\nProgram \"%s\" installed. Just run %s\\n' \\\n\t\t$(NAME) $(BINDIR)/$(NAME)\n" }, { "path": "README.md", "content": "## txt2regex — Regular expression wizard for the command line\n\n![](https://aurelio.net/projects/txt2regex/img/demo.gif)\n\n- Author: [Aurelio Jargas](https://aurelio.net/about.html)\n- License: GPLv2\n- First release: 2001-02-23 ([all releases](https://github.com/aureliojargas/txt2regex/releases))\n- Requires: Bash >= 3.0\n- Website: https://aurelio.net/projects/txt2regex/\n\nTxt2regex is a regular expression wizard for the command line.\n\nUsers with little or no knowledge of regular expressions can quickly\ncreate hairy regexes by answering questions in a simple text-based\ninteractive interface.\n\nTxt2regex is aware of the particular notation and caveats of many\ndifferent regular expression flavors, generating valid regexes for more\nthan 20 targets, including grep, sed, Vim, Emacs, JavaScript, Python,\nPHP, PostgreSQL.\n\nTxt2regex is a one-file shell script made 100% with Bash builtin\ncommands. The only requirement is Bash itself, since no grep, find, sed\nor any other system command is used.\n\n\n## Command line options\n\nSee [tests/cmdline.md](tests/cmdline.md) for a list of all the\navailable command line options and examples on using them.\n\n\n## Features\n\nSee [tests/features.md](tests/features.md) for some of the special\nfeatures txt2regex has to handle user input and compose proper regexes.\n\n\n## Running\n\nTxt2regex is a stand-alone Bash script, it doesn't need to be installed.\nJust run it:\n\n bash txt2regex.sh\n\nMaking it an executable file, you can run it directly:\n\n chmod +x txt2regex.sh\n ./txt2regex.sh\n\nIf you want it in [another language][pos] besides English:\n\n make install BINDIR=. LOCALEDIR=po\n LANG=es_ES ./txt2regex\n\n\n## Supported flavors\n\n```console\n$ bash txt2regex.sh --showmeta\n\nawk + ? | () awk version 20121220\nchicken + ? {} | () CHICKEN 4.12.0\ned \\+ \\? \\{\\} \\| \\(\\) GNU Ed 1.10\negrep + ? {} | () grep (GNU grep) 3.1\nemacs + ? \\\\{\\\\} \\\\| \\\\(\\\\) GNU Emacs 25.2.2\nexpect + ? {} | () expect version 5.45.4\nfind + ? {} | () find (GNU findutils) 4.7.0-git\ngawk + ? {} | () GNU Awk 4.1.4\ngrep \\+ \\? \\{\\} \\| \\(\\) grep (GNU grep) 3.1\njavascript + ? {} | () node v8.10.0\nlex + ? {} | () flex 2.6.4\nmawk + ? | () mawk 1.3.3 Nov 1996\nmysql + ? {} | () mysql Ver 14.14 Distrib 5.7.29\nperl + ? {} | () perl v5.26.1\nphp + ? {} | () PHP 7.2.24-0ubuntu0.18.04.4\npostgres + ? {} | () psql (PostgreSQL) 10.12\nprocmail + ? | () procmail v3.23pre 2001/09/13\npython + ? {} | () Python 3.6.9\nsed \\+ \\? \\{\\} \\| \\(\\) sed (GNU sed) 4.4\ntcl + ? {} | () tcl 8.6\nvi \\{\\} \\(\\) nvi 1.81.6-13\nvim \\+ \\= \\{} \\| \\(\\) VIM - Vi IMproved 8.0 (2016 Sep 12)\n\nNOTE: . [] [^] and * are the same on all programs.\n\n$\n```\n\n\n## Regex tester to gather \"real life\" data\n\nTxt2regex needs to know regex-related information for each flavor it\nsupports. For example:\n\n- Which metacharacters are supported?\n- How to escape a metacharacter to match it literally?\n- Are POSIX character classes supported?\n\nInstead of relying in documentation to get that information, the\n[tests/regex-tester.sh](tests/regex-tester.sh) script calls the real\nprograms with specially crafted regexes and sample texts, verifying how\nthose programs behave in \"real life\".\n\nTo have a trackable and public record, the output of this tester is also\nsaved to this repository, in a readable and grepable plain text file:\n[tests/regex-tester.txt](tests/regex-tester.txt). Future changes in\nbehavior can be easily detected.\n\n\n## Testing\n\n- `make test` — to run all the tests in the current Bash version on your\n machine.\n\n- `make test-bash` — to run all the tests in all the released Bash\n versions since 3.0 (requires Docker).\n\n- `make test-regex` — to run the regex tester (requires Docker).\n\nCheck the [Makefile](Makefile) for the details on what gets executed.\n\n\n## Translators\n\n ca Catalan Carles (ChAoS)\n de_DE German Jan Parthey\n es_ES Spanish Diego Moya\n fr_FR French wwp\n id_ID Indonesian Muhamad Faizal\n it_IT Italian Daniele Pizzolli\n ja Japanese Hajime Dei\n pl_PL Polish Chris Piechowicz\n pt_BR Portuguese Aurelio Jargas\n ro_RO Romanian Robert Claudiu Gheorghe\n tr Turkish erayalakese\n\nTo translate txt2regex to your language:\n\n- translate the [po/txt2regex.pot][potfile] file (in the `msgstr` lines)\n- save it as `po/XX.po` (where XX is the [two-letter code][iso639] for\n your language)\n- submit this new `.po` file in a pull request\n\nCheck the [current translations][pos] for reference.\n\n[potfile]: https://github.com/aureliojargas/txt2regex/blob/master/po/txt2regex.pot\n[iso639]: https://en.wikipedia.org/wiki/List_of_ISO_639-1_codes\n[pos]: https://github.com/aureliojargas/txt2regex/tree/master/po\n\n\n## FAQ\n\n### Why?\n\n- To try to make simple regexes less painful for beginners.\n- To have a reliable source for the specific regex syntax and rules from\n different flavors.\n- To have coding fun :)\n\n### What is that `` that appears in the regex?\n\nThat `` represents a literal tab character. When using the regex in\nthe desired external program, remember to change that to a literal tab.\nThis is required by programs that do not support using `\\t` as a\nshortcut for the tab character.\n\n### Why my terminal size (lines/columns) is not detected?\n\nTxt2regex uses the environment variables `$LINES` and `$COLUMNS` to get\nthe current terminal size. Make sure you have them exported, otherwise\nthe default 80x25 size will be assumed.\n\nTo check if the variables are exported, run:\n\n```bash\nbash -c 'echo $COLUMNS $LINES'\n```\n\nIf no numbers are shown in the output, a quick fix is running:\n\n```bash\nexport COLUMNS LINES\n```\n\nAs a permanent fix, add the previous `export` command to a Bash\nconfiguration file, such as `~/.bashrc`.\n" }, { "path": "TODO", "content": "txt2regex TODO:\n\n - new programs: expr, oawk, nawk, MKS awk, ruby, bash, java, html5, lua\n - add support for \\\n - support for user defined ranges as 0-5, a-f, etc\n - allow combinations as [A-Z0-9_.#]\n - more ready-to-use regexes! (ip, email, url)\n - ~/.txt2regexrc: remember programs, last histories, name REs\n - negated POSIX|special combination (Choice hack)\n - empty | check, for things like ^| or (|)\n - how to capture blanks on Get* (via menu)?\n\nUser requests:\n\n - undo last step (Bence Fejervari @ .hu)\n - std{in,out} mode to use it with a frontend (Robert-Claudiu Gheorghe @ .com)\n - interface to feed the programs with the RegEx (Chris Piechowicz @ .au)\n - on the fly regex test (zentara @ .com)\n - add other versions of the same program (julioB @ .edu)\n - escape special chars when **applying** the regex (julioB @ .edu)\n\nExtra TODO:\n\n - grep TODO txt2regex.sh\n" }, { "path": "man/txt2regex.html", "content": "\n\n\nTXT2REGEX\n\n\n\n\n
\n
\n

TXT2REGEX

\n

May 21, 2020

\n
\n
\n
\n\n
\n\n
\n

NAME

\n\n

\ntxt2regex -- console regular expression wizard\n

\n\n
\n
\n

SYNOPSIS

\n\n

\ntxt2regex [--nocolor|--whitebg] [--all|--prog programs]\n

\n

\ntxt2regex --showmeta\n

\n

\ntxt2regex --showinfo program [--nocolor]\n

\n

\ntxt2regex --history value [--all|--prog programs]\n

\n

\ntxt2regex --make label [--all|--prog programs]\n

\n\n
\n
\n

DESCRIPTION

\n\n

\ntxt2regex is a regular expression wizard that converts human\nsentences to regexes.\n

\n

\nIn a simple interactive console interface, the user answer questions and\ntxt2regex builds the regexes for more than 20 programs.\n

\n

\nhttps://aurelio.net/projects/txt2regex/\n

\n\n
\n
\n

OPTIONS

\n\n
\n
--all
\nSelect all the available programs. Be aware that the list of available\nprograms is long. You will need a terminal window with more than 40\nlines for the user interface to fit. Also make sure that the $LINES\nshell variable is exported, so txt2regex can detect the current\nnumber of available lines.\n

\n
\n
-h, --help
\nPrint the help message and quit.\n

\n
\n
--history <value>
\nPrint a regex from the given history data. The history value is shown in\nthe last screen of the wizard, when you quit.\n

\n
\n
--make <label>
\nPrint a ready regex for the specified label. Inform an empty label to\nsee the list of available labels.\n

\n
\n
--nocolor
\nDo not use colors.\n

\n
\n
--prog <program1,program2,...>
\nSpecify which programs to use, separated by commas. Use --showmeta\nto see the complete list of available programs.\n

\n
\n
--showinfo <program>
\nPrint regex-related info about the specified program. Use --nocolor\nto have a text-only output (no control characters).\n

\n
\n
--showmeta
\nPrint a metacharacters table featuring all the programs.\n

\n
\n
-V, --version
\nPrint the program version and quit.\n

\n
\n
--whitebg
\nAdjust colors for white background terminals.\n
\n
\n\n
\n
\n

EXAMPLES

\n\n
\n
Using it as a wizard (interactive interface):
\n

\n
\ntxt2regex\n
\n\n

\n
\n
Specify a custom selection of programs for the wizard:
\n

\n
\ntxt2regex --prog perl,python,php,javascript\n
\n\n

\n
\n
Getting an extensive metacharacters table:
\n

\n
\ntxt2regex --showmeta\n
\n\n

\n
\n
Getting regex-related information about sed:
\n

\n
\ntxt2regex --showinfo sed\n
\n\n

\n
\n
Replay a regex by using history data:
\n

\n
\ntxt2regex --history '16421¤:01¤:'\n
\n\n

\n
\n
Getting handy ready-to-use regexes for common patterns:
\n

\n
\ntxt2regex --make hour\ntxt2regex --make number3 --prog perl\ntxt2regex --make date2 --all\n
\n\n
\n
\n\n
\n
\n

WIZARD INTERFACE

\n\n
\n+---------------------------------------+\n| Top menu                              |\n| Group menu                            |\n|                                       |\n| Regexes of the selected programs      |\n| ...                                   |\n| ...                                   |\n|                                       |\n| History                               |\n| Prompt                                |\n|                                       |\n| The question                          |\n| The answers                           |\n| ...                                   |\n| ...                                   |\n+---------------------------------------+\n
\n\n
\n
\n

WIZARD COMMANDS

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
.Quit the program (with confirmation)
0Reset the regular expression
1-9Answers the questions
*Toggles color ON/OFF
/Add/remove programs
|Insert an alternation (where allowed)
(Open a new group (where allowed)
)Close the opened group (if any)
\n\n
\n
\n

BUGS

\n\n

\nhttps://github.com/aureliojargas/txt2regex/issues\n

\n\n
\n
\n

AUTHOR

\n\n

\nAurelio Jargas <<verde (a) aurelio net>>\n

\n\n
\n
\n

COPYRIGHT

\n\n

\nCopyright © 2001-2020 Aurelio Jargas, GNU GPL v2\n

\n
\n
\n\n\n\n
\n" }, { "path": "man/txt2regex.man", "content": ".TH \"TXT2REGEX\" 1 \"May 21, 2020\" \"\"\n\n.SH NAME\n.P\n\\fBtxt2regex\\fR \\-\\- console regular expression wizard\n.SH SYNOPSIS\n.P\n\\fBtxt2regex\\fR [\\fB\\-\\-nocolor\\fR|\\fB\\-\\-whitebg\\fR] [\\fB\\-\\-all\\fR|\\fB\\-\\-prog\\fR \\fIprograms\\fR]\n.P\n\\fBtxt2regex\\fR \\fB\\-\\-showmeta\\fR\n.P\n\\fBtxt2regex\\fR \\fB\\-\\-showinfo\\fR \\fIprogram\\fR [\\fB\\-\\-nocolor\\fR]\n.P\n\\fBtxt2regex\\fR \\fB\\-\\-history\\fR \\fIvalue\\fR [\\fB\\-\\-all\\fR|\\fB\\-\\-prog\\fR \\fIprograms\\fR]\n.P\n\\fBtxt2regex\\fR \\fB\\-\\-make\\fR \\fIlabel\\fR [\\fB\\-\\-all\\fR|\\fB\\-\\-prog\\fR \\fIprograms\\fR]\n.SH DESCRIPTION\n.P\n\\fBtxt2regex\\fR is a regular expression wizard that converts human\nsentences to regexes.\n.P\nIn a simple interactive console interface, the user answer questions and\n\\fBtxt2regex\\fR builds the regexes for more than 20 programs.\n.P\n\\fIhttps://aurelio.net/projects/txt2regex/\\fR\n.SH OPTIONS\n\n.TP\n\\fB\\-\\-all\\fR\nSelect all the available programs. Be aware that the list of available\nprograms is long. You will need a terminal window with more than 40\nlines for the user interface to fit. Also make sure that the \\fB$LINES\\fR\nshell variable is exported, so \\fBtxt2regex\\fR can detect the current\nnumber of available lines.\n\n.TP\n\\fB\\-h\\fR, \\fB\\-\\-help\\fR\nPrint the help message and quit.\n\n.TP\n\\fB\\-\\-history \\fR\nPrint a regex from the given history data. The history value is shown in\nthe last screen of the wizard, when you quit.\n\n.TP\n\\fB\\-\\-make