Results 1 - 14 of about 14 results out of about 97381 pages. (0.03 seconds)

glob . . . 2 matches
...raditional shell globs use a very simple syntax, which is less expressive than a RegularExpression. Most characters in a glob are treated literally, but a {{{*}}} matches 0 or mo...

17.3k - rev: 59 (current) last modified: 2022-10-13 13:52:20

ReplacingStrings . . . 1 match
...tput of "some_command" some_command | sed 's/search/replace/g' }}} `sed` uses [[RegularExpression|regular expressions]]. Unlike the bash, "search" and "replace" would have to be ...

4.5k - rev: 4 (current) last modified: 2013-04-15 19:58:23

Quotes . . . 1 match
...otes to suppress interpretation of special syntax within [[glob|patterns]] and [[RegularExpression|regular expressions]], so that any literal or expanded string may be easily incl...

10.9k - rev: 32 (current) last modified: 2024-03-07 22:57:49

ProcessManagement . . . 1 match
...if ps -ef | grep '[f]oo'; then }}} You'll likely run into this a few times. The RegularExpression `[f]oo` matches only the literal string `foo`; it does not match the literal str...

46.6k - rev: 88 (current) last modified: 2023-08-09 06:29:52

BashProgramming/Ex01 . . . 1 match
...t string matches a given format, and if so, to extract various pieces of it: the RegularExpression. It's not ''pretty'', but it seems like a good match for this problem. Bash's ...

10.5k - rev: 2 (current) last modified: 2018-02-07 16:37:53

BashPitfalls . . . 1 match
... right-hand side of the `=~` operator cause it to become a string, rather than a RegularExpression. If you want to use a long or complicated regular expression and avoid lots of ...

86.2k - rev: 572 (current) last modified: 2024-04-04 23:09:24

BashGuide/Patterns . . . 1 match
...epth in this guide, but if you are interested in this concept, please read up on RegularExpression, or [[http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html#ta...

11.3k - rev: 34 (current) last modified: 2016-01-15 10:08:43

BashFAQ/100 . . . 1 match
...ring* ]]; then # substring will be treated as a glob pattern }}} There is also a RegularExpression capability, involving the `=~` operator. For compatibility with all versions of...

24.3k - rev: 47 (current) last modified: 2023-06-26 10:03:19

BashFAQ/079 . . . 1 match
... can't use the `|` union operator with plain `grep`. `|` is only available in [[RegularExpression|Extended Regular Expressions]].) It can also be done with {{{sed}}}, {{{awk}}},...

4.1k - rev: 37 (current) last modified: 2023-01-26 22:54:33

BashFAQ/054 . . . 1 match
...that works in legacy Bourne shells, you might prefer to use an external tool's [[RegularExpression|regular expression]] syntax. Here is a portable version (explained in detail [[...

5.6k - rev: 54 (current) last modified: 2022-08-01 10:02:57

BashFAQ/031 . . . 1 match
...) ||{{{[[ $name = a* ]] || echo "name does not start with an 'a': $name"}}} || ||RegularExpression matching ||{{{=~}}} ||(not available) ||{{{[[ $(date) =~ ^Fri\ ...\ 13 ]] && ech...

10.5k - rev: 51 (current) last modified: 2022-05-09 13:49:40

BashFAQ/021 . . . 1 match
...'s'''tream '''ed'''itor: {{{ some_command | sed 's/foo/bar/g' }}} `sed` uses [[RegularExpression|regular expressions]]. In our example, `foo` and `bar` are literal strings. If...

13.5k - rev: 83 (current) last modified: 2022-11-03 23:42:27

BashFAQ/006 . . . 1 match
... of, and to maintain. 2. The variable names must be a single line and match the RegularExpression {{{^[a-zA-Z_][a-zA-Z_0-9]*$}}} -- i.e., a variable name cannot contain arbitrary...

16.8k - rev: 63 (current) last modified: 2023-04-14 06:52:11