When and why did ^ and $ take on their meanings of “beginning of line” and “end of line?”History of Bash globbingRegex `/pattern/g` and ed `:g/pattern/`: which came first, and why `g`?What text editor was used by Thompson and Ritchie in the writing of Unix?Why do /usr and /tmp directories for Linux miss vowels in their spellings?SED change only start of line and preserve end of lineWhy does the same sed regex (after grep) fail when run in a bash script vs bash command line?When and how was the double-dash (--) introduced as an end of options delimiter in Unix/Linux?egrep regular expression - same word in the beginning and endsed backreference: get each line and append it to end of lineRegex to match beginning and end of line in Vim (quote around whole line)Why did the system call registers and order change from Intel 32bit to 64bit?When (and from which places) does the `-h` (help) command-line option come from?
I see my dog run
Why airport relocation isn't done gradually?
How to answer pointed "are you quitting" questioning when I don't want them to suspect
What to wear for invited talk in Canada
How to move the player while also allowing forces to affect it
Could a US political party gain complete control over the government by removing checks & balances?
Should the British be getting ready for a no-deal Brexit?
Is "plugging out" electronic devices an American expression?
Denied boarding due to overcrowding, Sparpreis ticket. What are my rights?
Patience, young "Padovan"
Is ipsum/ipsa/ipse a third person pronoun, or can it serve other functions?
Does it makes sense to buy a new cycle to learn riding?
Are white and non-white police officers equally likely to kill black suspects?
LWC and complex parameters
What causes the sudden spool-up sound from an F-16 when enabling afterburner?
"My colleague's body is amazing"
How did the USSR manage to innovate in an environment characterized by government censorship and high bureaucracy?
When blogging recipes, how can I support both readers who want the narrative/journey and ones who want the printer-friendly recipe?
What is the meaning of "of trouble" in the following sentence?
Are objects structures and/or vice versa?
Is there a name of the flying bionic bird?
Crop image to path created in TikZ?
Is Social Media Science Fiction?
Does bootstrapped regression allow for inference?
When and why did ^ and $ take on their meanings of “beginning of line” and “end of line?”
History of Bash globbingRegex `/pattern/g` and ed `:g/pattern/`: which came first, and why `g`?What text editor was used by Thompson and Ritchie in the writing of Unix?Why do /usr and /tmp directories for Linux miss vowels in their spellings?SED change only start of line and preserve end of lineWhy does the same sed regex (after grep) fail when run in a bash script vs bash command line?When and how was the double-dash (--) introduced as an end of options delimiter in Unix/Linux?egrep regular expression - same word in the beginning and endsed backreference: get each line and append it to end of lineRegex to match beginning and end of line in Vim (quote around whole line)Why did the system call registers and order change from Intel 32bit to 64bit?When (and from which places) does the `-h` (help) command-line option come from?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
Many command-line tools (grep
, flex
, etc.) use the ^
symbol to denote "beginning of line" and the $
symbol to denote "end of line." When did this convention arise? It seems perfectly reasonable to reserve two characters for these purposes, but it's a bit odd that on modern keyboards the $
symbol is to the left of the ^
symbol.
Is this a completely arbitrary decision? Does this come from some older keyboard layout? Is this convention used because some older tool decided to do things this way?
Regardless of the answer, are there primary sources that document this?
regular-expression history
New contributor
add a comment |
Many command-line tools (grep
, flex
, etc.) use the ^
symbol to denote "beginning of line" and the $
symbol to denote "end of line." When did this convention arise? It seems perfectly reasonable to reserve two characters for these purposes, but it's a bit odd that on modern keyboards the $
symbol is to the left of the ^
symbol.
Is this a completely arbitrary decision? Does this come from some older keyboard layout? Is this convention used because some older tool decided to do things this way?
Regardless of the answer, are there primary sources that document this?
regular-expression history
New contributor
Relating in: unix.stackexchange.com/a/136524/117549
– Jeff Schaller♦
Apr 5 at 17:36
@JeffSchaller The idea of using regular expression syntax, adapted toglob
, makes a lot of sense. Perhaps I'm mistaken, though, but doesglob
actually support^
and$
?
– templatetypedef
Apr 5 at 17:40
I did not mean to imply any connection between wildcards and regexes; I saw the date in Gilles' answer and thought it was a useful addition here.^
and$
are regular expression tokens (here), which is why I added that tag.
– Jeff Schaller♦
Apr 5 at 17:43
I’m not sure this is the origin of the symbols, and it doesn’t explain why they were chosen, but QED had them in 1970.
– Stephen Kitt
Apr 5 at 18:11
add a comment |
Many command-line tools (grep
, flex
, etc.) use the ^
symbol to denote "beginning of line" and the $
symbol to denote "end of line." When did this convention arise? It seems perfectly reasonable to reserve two characters for these purposes, but it's a bit odd that on modern keyboards the $
symbol is to the left of the ^
symbol.
Is this a completely arbitrary decision? Does this come from some older keyboard layout? Is this convention used because some older tool decided to do things this way?
Regardless of the answer, are there primary sources that document this?
regular-expression history
New contributor
Many command-line tools (grep
, flex
, etc.) use the ^
symbol to denote "beginning of line" and the $
symbol to denote "end of line." When did this convention arise? It seems perfectly reasonable to reserve two characters for these purposes, but it's a bit odd that on modern keyboards the $
symbol is to the left of the ^
symbol.
Is this a completely arbitrary decision? Does this come from some older keyboard layout? Is this convention used because some older tool decided to do things this way?
Regardless of the answer, are there primary sources that document this?
regular-expression history
regular-expression history
New contributor
New contributor
edited Apr 5 at 18:25
G-Man
13.7k93770
13.7k93770
New contributor
asked Apr 5 at 17:27
templatetypedeftemplatetypedef
1213
1213
New contributor
New contributor
Relating in: unix.stackexchange.com/a/136524/117549
– Jeff Schaller♦
Apr 5 at 17:36
@JeffSchaller The idea of using regular expression syntax, adapted toglob
, makes a lot of sense. Perhaps I'm mistaken, though, but doesglob
actually support^
and$
?
– templatetypedef
Apr 5 at 17:40
I did not mean to imply any connection between wildcards and regexes; I saw the date in Gilles' answer and thought it was a useful addition here.^
and$
are regular expression tokens (here), which is why I added that tag.
– Jeff Schaller♦
Apr 5 at 17:43
I’m not sure this is the origin of the symbols, and it doesn’t explain why they were chosen, but QED had them in 1970.
– Stephen Kitt
Apr 5 at 18:11
add a comment |
Relating in: unix.stackexchange.com/a/136524/117549
– Jeff Schaller♦
Apr 5 at 17:36
@JeffSchaller The idea of using regular expression syntax, adapted toglob
, makes a lot of sense. Perhaps I'm mistaken, though, but doesglob
actually support^
and$
?
– templatetypedef
Apr 5 at 17:40
I did not mean to imply any connection between wildcards and regexes; I saw the date in Gilles' answer and thought it was a useful addition here.^
and$
are regular expression tokens (here), which is why I added that tag.
– Jeff Schaller♦
Apr 5 at 17:43
I’m not sure this is the origin of the symbols, and it doesn’t explain why they were chosen, but QED had them in 1970.
– Stephen Kitt
Apr 5 at 18:11
Relating in: unix.stackexchange.com/a/136524/117549
– Jeff Schaller♦
Apr 5 at 17:36
Relating in: unix.stackexchange.com/a/136524/117549
– Jeff Schaller♦
Apr 5 at 17:36
@JeffSchaller The idea of using regular expression syntax, adapted to
glob
, makes a lot of sense. Perhaps I'm mistaken, though, but does glob
actually support ^
and $
?– templatetypedef
Apr 5 at 17:40
@JeffSchaller The idea of using regular expression syntax, adapted to
glob
, makes a lot of sense. Perhaps I'm mistaken, though, but does glob
actually support ^
and $
?– templatetypedef
Apr 5 at 17:40
I did not mean to imply any connection between wildcards and regexes; I saw the date in Gilles' answer and thought it was a useful addition here.
^
and $
are regular expression tokens (here), which is why I added that tag.– Jeff Schaller♦
Apr 5 at 17:43
I did not mean to imply any connection between wildcards and regexes; I saw the date in Gilles' answer and thought it was a useful addition here.
^
and $
are regular expression tokens (here), which is why I added that tag.– Jeff Schaller♦
Apr 5 at 17:43
I’m not sure this is the origin of the symbols, and it doesn’t explain why they were chosen, but QED had them in 1970.
– Stephen Kitt
Apr 5 at 18:11
I’m not sure this is the origin of the symbols, and it doesn’t explain why they were chosen, but QED had them in 1970.
– Stephen Kitt
Apr 5 at 18:11
add a comment |
2 Answers
2
active
oldest
votes
The QED editor, written in 1965 for the Berkeley Timesharing System, used $
for addressing the last line in a file, just like ed
, ex
, vi
and vim
does today. See page 2-1 in the manual. The original QED editor did not allow for the use of regular expressions though.
Ken Thompson later ("late 1960s") wrote a version of QED for Multics which was the first editor to implement regular expressions. This editor heavily influenced Ken's development of ed
in 1969 for Unix (later "finalised" by Dennis Richie in about 1971). Bill Joy, out of frustration with ed
, implemented ex
and vi
and these were part of the first BSD release in 1977 for the PDP-11.
The ^
and $
expressions, together with much of what became the POSIX regular expression syntax, with the semantics it has today, was implemented in Ken's version of QED. See page 4 in the manual.
It is not clear where the choice of these particular symbols came from, but $
already had the meaning "last" from the way it was used to address the last line.
On certain terminals, the ^
character was impossible to generate. Ken's QED editor therefore allowed '
to be used instead of ^
(see Bell Labs manual).
2
For more history, with unfortunately a myth here and there, see unix.stackexchange.com/a/115995/5132 and unix.stackexchange.com/a/332494/5132 .
– JdeBP
Apr 5 at 19:18
add a comment |
This copy of ed(I)
, dated 11/3/71, from the Unix First Edition,
confirms that ed
is based on QED,
and shows that ^
and $
had their current meanings then:
- A circumflex (
^
) at the beginning of a regular expression
matches the null character at the beginning of a line.
- A currency symbol (
$
) at the end of a regular expression
matches the null character at the end of a line.
This note and the Wikipedia page for grep
indicate that grep
was created in the early 1970s
and used the same regular expression syntax as ed
.
The concept of the regular expression
predates its use in computer utilities by nearly two decades.
The Wikipedia page for “regular expression”
and this Stack Overflow question
credit American mathematician Stephen Cole Kleene
with inventing regular expressions,
or at least describing them and coining the term.
Many histories refer to his paper,
Representation of Events in Nerve Nets and Finite Automata (PDF).
This 101-page document, dated 15 December 1951, is difficult to read,
and (as far as I can see) does not mention the ^
and $
syntax.
However, it does present *
as meaning
“zero or more of the preceding thing”
on page 49 of the paper (page 52 of the PDF file).
This is (somewhat) widely known as the “Kleene star”.
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
templatetypedef is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f510770%2fwhen-and-why-did-and-take-on-their-meanings-of-beginning-of-line-and-end%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The QED editor, written in 1965 for the Berkeley Timesharing System, used $
for addressing the last line in a file, just like ed
, ex
, vi
and vim
does today. See page 2-1 in the manual. The original QED editor did not allow for the use of regular expressions though.
Ken Thompson later ("late 1960s") wrote a version of QED for Multics which was the first editor to implement regular expressions. This editor heavily influenced Ken's development of ed
in 1969 for Unix (later "finalised" by Dennis Richie in about 1971). Bill Joy, out of frustration with ed
, implemented ex
and vi
and these were part of the first BSD release in 1977 for the PDP-11.
The ^
and $
expressions, together with much of what became the POSIX regular expression syntax, with the semantics it has today, was implemented in Ken's version of QED. See page 4 in the manual.
It is not clear where the choice of these particular symbols came from, but $
already had the meaning "last" from the way it was used to address the last line.
On certain terminals, the ^
character was impossible to generate. Ken's QED editor therefore allowed '
to be used instead of ^
(see Bell Labs manual).
2
For more history, with unfortunately a myth here and there, see unix.stackexchange.com/a/115995/5132 and unix.stackexchange.com/a/332494/5132 .
– JdeBP
Apr 5 at 19:18
add a comment |
The QED editor, written in 1965 for the Berkeley Timesharing System, used $
for addressing the last line in a file, just like ed
, ex
, vi
and vim
does today. See page 2-1 in the manual. The original QED editor did not allow for the use of regular expressions though.
Ken Thompson later ("late 1960s") wrote a version of QED for Multics which was the first editor to implement regular expressions. This editor heavily influenced Ken's development of ed
in 1969 for Unix (later "finalised" by Dennis Richie in about 1971). Bill Joy, out of frustration with ed
, implemented ex
and vi
and these were part of the first BSD release in 1977 for the PDP-11.
The ^
and $
expressions, together with much of what became the POSIX regular expression syntax, with the semantics it has today, was implemented in Ken's version of QED. See page 4 in the manual.
It is not clear where the choice of these particular symbols came from, but $
already had the meaning "last" from the way it was used to address the last line.
On certain terminals, the ^
character was impossible to generate. Ken's QED editor therefore allowed '
to be used instead of ^
(see Bell Labs manual).
2
For more history, with unfortunately a myth here and there, see unix.stackexchange.com/a/115995/5132 and unix.stackexchange.com/a/332494/5132 .
– JdeBP
Apr 5 at 19:18
add a comment |
The QED editor, written in 1965 for the Berkeley Timesharing System, used $
for addressing the last line in a file, just like ed
, ex
, vi
and vim
does today. See page 2-1 in the manual. The original QED editor did not allow for the use of regular expressions though.
Ken Thompson later ("late 1960s") wrote a version of QED for Multics which was the first editor to implement regular expressions. This editor heavily influenced Ken's development of ed
in 1969 for Unix (later "finalised" by Dennis Richie in about 1971). Bill Joy, out of frustration with ed
, implemented ex
and vi
and these were part of the first BSD release in 1977 for the PDP-11.
The ^
and $
expressions, together with much of what became the POSIX regular expression syntax, with the semantics it has today, was implemented in Ken's version of QED. See page 4 in the manual.
It is not clear where the choice of these particular symbols came from, but $
already had the meaning "last" from the way it was used to address the last line.
On certain terminals, the ^
character was impossible to generate. Ken's QED editor therefore allowed '
to be used instead of ^
(see Bell Labs manual).
The QED editor, written in 1965 for the Berkeley Timesharing System, used $
for addressing the last line in a file, just like ed
, ex
, vi
and vim
does today. See page 2-1 in the manual. The original QED editor did not allow for the use of regular expressions though.
Ken Thompson later ("late 1960s") wrote a version of QED for Multics which was the first editor to implement regular expressions. This editor heavily influenced Ken's development of ed
in 1969 for Unix (later "finalised" by Dennis Richie in about 1971). Bill Joy, out of frustration with ed
, implemented ex
and vi
and these were part of the first BSD release in 1977 for the PDP-11.
The ^
and $
expressions, together with much of what became the POSIX regular expression syntax, with the semantics it has today, was implemented in Ken's version of QED. See page 4 in the manual.
It is not clear where the choice of these particular symbols came from, but $
already had the meaning "last" from the way it was used to address the last line.
On certain terminals, the ^
character was impossible to generate. Ken's QED editor therefore allowed '
to be used instead of ^
(see Bell Labs manual).
edited 2 days ago
answered Apr 5 at 18:14
Kusalananda♦Kusalananda
140k17261435
140k17261435
2
For more history, with unfortunately a myth here and there, see unix.stackexchange.com/a/115995/5132 and unix.stackexchange.com/a/332494/5132 .
– JdeBP
Apr 5 at 19:18
add a comment |
2
For more history, with unfortunately a myth here and there, see unix.stackexchange.com/a/115995/5132 and unix.stackexchange.com/a/332494/5132 .
– JdeBP
Apr 5 at 19:18
2
2
For more history, with unfortunately a myth here and there, see unix.stackexchange.com/a/115995/5132 and unix.stackexchange.com/a/332494/5132 .
– JdeBP
Apr 5 at 19:18
For more history, with unfortunately a myth here and there, see unix.stackexchange.com/a/115995/5132 and unix.stackexchange.com/a/332494/5132 .
– JdeBP
Apr 5 at 19:18
add a comment |
This copy of ed(I)
, dated 11/3/71, from the Unix First Edition,
confirms that ed
is based on QED,
and shows that ^
and $
had their current meanings then:
- A circumflex (
^
) at the beginning of a regular expression
matches the null character at the beginning of a line.
- A currency symbol (
$
) at the end of a regular expression
matches the null character at the end of a line.
This note and the Wikipedia page for grep
indicate that grep
was created in the early 1970s
and used the same regular expression syntax as ed
.
The concept of the regular expression
predates its use in computer utilities by nearly two decades.
The Wikipedia page for “regular expression”
and this Stack Overflow question
credit American mathematician Stephen Cole Kleene
with inventing regular expressions,
or at least describing them and coining the term.
Many histories refer to his paper,
Representation of Events in Nerve Nets and Finite Automata (PDF).
This 101-page document, dated 15 December 1951, is difficult to read,
and (as far as I can see) does not mention the ^
and $
syntax.
However, it does present *
as meaning
“zero or more of the preceding thing”
on page 49 of the paper (page 52 of the PDF file).
This is (somewhat) widely known as the “Kleene star”.
add a comment |
This copy of ed(I)
, dated 11/3/71, from the Unix First Edition,
confirms that ed
is based on QED,
and shows that ^
and $
had their current meanings then:
- A circumflex (
^
) at the beginning of a regular expression
matches the null character at the beginning of a line.
- A currency symbol (
$
) at the end of a regular expression
matches the null character at the end of a line.
This note and the Wikipedia page for grep
indicate that grep
was created in the early 1970s
and used the same regular expression syntax as ed
.
The concept of the regular expression
predates its use in computer utilities by nearly two decades.
The Wikipedia page for “regular expression”
and this Stack Overflow question
credit American mathematician Stephen Cole Kleene
with inventing regular expressions,
or at least describing them and coining the term.
Many histories refer to his paper,
Representation of Events in Nerve Nets and Finite Automata (PDF).
This 101-page document, dated 15 December 1951, is difficult to read,
and (as far as I can see) does not mention the ^
and $
syntax.
However, it does present *
as meaning
“zero or more of the preceding thing”
on page 49 of the paper (page 52 of the PDF file).
This is (somewhat) widely known as the “Kleene star”.
add a comment |
This copy of ed(I)
, dated 11/3/71, from the Unix First Edition,
confirms that ed
is based on QED,
and shows that ^
and $
had their current meanings then:
- A circumflex (
^
) at the beginning of a regular expression
matches the null character at the beginning of a line.
- A currency symbol (
$
) at the end of a regular expression
matches the null character at the end of a line.
This note and the Wikipedia page for grep
indicate that grep
was created in the early 1970s
and used the same regular expression syntax as ed
.
The concept of the regular expression
predates its use in computer utilities by nearly two decades.
The Wikipedia page for “regular expression”
and this Stack Overflow question
credit American mathematician Stephen Cole Kleene
with inventing regular expressions,
or at least describing them and coining the term.
Many histories refer to his paper,
Representation of Events in Nerve Nets and Finite Automata (PDF).
This 101-page document, dated 15 December 1951, is difficult to read,
and (as far as I can see) does not mention the ^
and $
syntax.
However, it does present *
as meaning
“zero or more of the preceding thing”
on page 49 of the paper (page 52 of the PDF file).
This is (somewhat) widely known as the “Kleene star”.
This copy of ed(I)
, dated 11/3/71, from the Unix First Edition,
confirms that ed
is based on QED,
and shows that ^
and $
had their current meanings then:
- A circumflex (
^
) at the beginning of a regular expression
matches the null character at the beginning of a line.
- A currency symbol (
$
) at the end of a regular expression
matches the null character at the end of a line.
This note and the Wikipedia page for grep
indicate that grep
was created in the early 1970s
and used the same regular expression syntax as ed
.
The concept of the regular expression
predates its use in computer utilities by nearly two decades.
The Wikipedia page for “regular expression”
and this Stack Overflow question
credit American mathematician Stephen Cole Kleene
with inventing regular expressions,
or at least describing them and coining the term.
Many histories refer to his paper,
Representation of Events in Nerve Nets and Finite Automata (PDF).
This 101-page document, dated 15 December 1951, is difficult to read,
and (as far as I can see) does not mention the ^
and $
syntax.
However, it does present *
as meaning
“zero or more of the preceding thing”
on page 49 of the paper (page 52 of the PDF file).
This is (somewhat) widely known as the “Kleene star”.
edited Apr 5 at 21:17
answered Apr 5 at 18:55
G-ManG-Man
13.7k93770
13.7k93770
add a comment |
add a comment |
templatetypedef is a new contributor. Be nice, and check out our Code of Conduct.
templatetypedef is a new contributor. Be nice, and check out our Code of Conduct.
templatetypedef is a new contributor. Be nice, and check out our Code of Conduct.
templatetypedef is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f510770%2fwhen-and-why-did-and-take-on-their-meanings-of-beginning-of-line-and-end%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Relating in: unix.stackexchange.com/a/136524/117549
– Jeff Schaller♦
Apr 5 at 17:36
@JeffSchaller The idea of using regular expression syntax, adapted to
glob
, makes a lot of sense. Perhaps I'm mistaken, though, but doesglob
actually support^
and$
?– templatetypedef
Apr 5 at 17:40
I did not mean to imply any connection between wildcards and regexes; I saw the date in Gilles' answer and thought it was a useful addition here.
^
and$
are regular expression tokens (here), which is why I added that tag.– Jeff Schaller♦
Apr 5 at 17:43
I’m not sure this is the origin of the symbols, and it doesn’t explain why they were chosen, but QED had them in 1970.
– Stephen Kitt
Apr 5 at 18:11