MORE(1P)

📦 version 2017a, in alpine 3.22, alpine 3.23, alpine 3.24, arch rolling, nixpkgs unstable, opensuse-leap 16.0

✨ MORE(1P) — the POSIX Programmer's Manual glow-up ✨

okay bestie, welcome to the more page, and yes it's from the POSIX Programmer's Manual. buckle up, this one's a whole saga (four parts, no cap) 💖

🌸 PROLOG 🌸

so like, real talk: this manual page is part of the POSIX Programmer's Manual. the Linux implementation of this interface may differ (consult the corresponding Linux manual page for details of Linux behavior), or the interface may not be implemented on Linux at all 🙈. iykyk.

👑 NAME 👑

more — display files on a page-by-page basis. literally just that. main character behaviour fr fr 💅

🦋 SYNOPSIS 🦋

more [-ceisu] [-n number] [-p command] [-t tagstring] [file...]

🌈 DESCRIPTION 🌈

okay so here's the tea. the more utility shall read files and either write them to the terminal on a page-by-page basis or filter them to standard output. two moods, one tool ✨

if standard output is not a terminal device, all input files shall be copied to standard output in their entirety, without modification, except as specified for the -s option. (so it just dumps everything through, no pausing, no drama.)

if standard output is a terminal device, the files shall be written a number of lines (one screenful) at a time under the control of user commands. see the EXTENDED DESCRIPTION section 👀

🎀 the block-mode terminal situation 🎀

certain block-mode terminals do not have all the capabilities necessary to support the complete more definition; they are incapable of accepting commands that are not terminated with a <newline>. 😭 implementations that support such terminals shall provide an operating mode to more in which all commands can be terminated with a <newline> on those terminals. this mode:

  • shall be documented in the system documentation
  • shall, at invocation, inform the user of the terminal deficiency that requires the <newline> usage and provide instructions on how this warning can be suppressed in future invocations
  • shall not be required for implementations supporting only fully capable terminals
  • shall not affect commands already requiring <newline> characters
  • shall not affect users on the capable terminals from using more as described in this volume of POSIX.1‐2017

💅 OPTIONS 💅

the more utility shall conform to the Base Definitions volume of POSIX.1‐2017, Section 12.2, Utility Syntax Guidelines, except that '+' may be recognized as an option delimiter as well as '-'. (yes queen, two delimiters, she contains multitudes ✨)

the following options shall be supported:

  • -c — if a screen is to be written that has no lines in common with the current screen, or more is writing its first screen, more shall not scroll the screen, but instead shall redraw each line of the screen in turn, from the top of the screen to the bottom. in addition, if more is writing its first screen, the screen shall be cleared. this option may be silently ignored on devices with insufficient terminal capabilities 🙈
  • -e — exit immediately after writing the last line of the last file in the argument list; see the EXTENDED DESCRIPTION section
  • -i — perform pattern matching in searches without regard to case; see the Base Definitions volume of POSIX.1‐2017, Section 9.2, Regular Expression General Requirements
  • -n number — specify the number of lines per screenful. the number argument is a positive decimal integer. the -n option shall override any values obtained from any other source. she's the boss, periodt 👑
  • -p command — each time a screen from a new file is displayed or redisplayed (including as a result of more commands; for example, :p), execute the more command(s) in the command arguments in the order specified, as if entered by the user after the first screen has been displayed. no intermediate results shall be displayed (that is, if the command is a movement to a screen different from the normal first screen, only the screen resulting from the command shall be displayed.) if any of the commands fail for any reason, an informational message to this effect shall be written, and no further commands specified using the -p option shall be executed for this file
  • -s — behave as if consecutive empty lines were a single empty line. (compressing the emptiness, we love an efficient queen 💅)
  • -t tagstring — write the screenful of the file containing the tag named by the tagstring argument. see the ctags utility. the tags feature represented by -t tagstring and the :t command is optional. it shall be provided on any system that also provides a conforming implementation of ctags; otherwise, the use of -t produces undefined results 😭
    • the filename resulting from the -t option shall be logically added as a prefix to the list of command line files, as if specified by the user. if the tag named by the tagstring argument is not found, it shall be an error, and more shall take no further action.
    • if the tag specifies a line number, the first line of the display shall contain the beginning of that line. if the tag specifies a pattern, the first line of the display shall contain the beginning of the matching text from the first line of the file that contains that pattern. if the line does not exist in the file or matching text is not found, an informational message to this effect shall be displayed, and more shall display the default screen as if -t had not been specified.
    • if both the -t tagstring and -p command options are given, the -t tagstring shall be processed first; that is, the file and starting line for the display shall be as specified by -t, and then the -p more command shall be executed. if the line (matching text) specified by the -t command does not exist (is not found), no -p more command shall be executed for this file at any time.
  • -u — treat a <backspace> as a printable control character, displayed as an implementation-defined character sequence (see the EXTENDED DESCRIPTION section), suppressing backspacing and the special handling that produces underlined or standout mode text on some terminal types. also, do not ignore a <carriage-return> at the end of a line.

🍓 OPERANDS 🍓

the following operand shall be supported:

  • file — a pathname of an input file. if no file operands are specified, the standard input shall be used. if a file is '-', the standard input shall be read at that point in the sequence.

🧚 STDIN 🧚

the standard input shall be used only if no file operands are specified, or if a file operand is '-'. no stray reads, she's polite like that 🫶

💜 INPUT FILES 💜

the input files being examined shall be text files. if standard output is a terminal, standard error shall be used to read commands from the user. if standard output is a terminal, standard error is not readable, and command input is needed, more may attempt to obtain user commands from the controlling terminal (for example, /dev/tty); otherwise, more shall terminate with an error indicating that it was unable to read user commands. if standard output is not a terminal, no error shall result if standard error cannot be opened for reading. ✨

⭐ ENVIRONMENT VARIABLES ⭐

the following environment variables shall affect the execution of more:

  • COLUMNS — override the system-selected horizontal display line size. see the Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables for valid values and results when it is unset or null.
  • EDITOR — used by the v command to select an editor. see the EXTENDED DESCRIPTION section.
  • LANG — provide a default value for the internationalization variables that are unset or null. (see the Base Definitions volume of POSIX.1‐2017, Section 8.2, Internationalization Variables for the precedence of internationalization variables used to determine the values of locale categories.)
  • LC_ALL — if set to a non-empty string value, override the values of all the other internationalization variables.
  • LC_COLLATE — determine the locale for the behavior of ranges, equivalence classes, and multi-character collating elements within regular expressions.
  • LC_CTYPE — determine the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multi-byte characters in arguments and input files) and the behavior of character classes within regular expressions.
  • LC_MESSAGES — determine the locale that should be used to affect the format and contents of diagnostic messages written to standard error and informative messages written to standard output.
  • NLSPATH — determine the location of message catalogs for the processing of LC_MESSAGES.
  • LINES — override the system-selected vertical screen size, used as the number of lines in a screenful. see the Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables for valid values and results when it is unset or null. the -n option shall take precedence over the LINES variable for determining the number of lines in a screenful.
  • MORE — determine a string containing options described in the OPTIONS section preceded with <hyphen-minus> characters and <blank>-separated as on the command line. any command line options shall be processed after those in the MORE variable, as if the command line were:
more $MORE options operands

the MORE variable shall take precedence over the TERM and LINES variables for determining the number of lines in a screenful.

  • TERM — determine the name of the terminal type. if this variable is unset or null, an unspecified default terminal type is used.

🔥 ASYNCHRONOUS EVENTS 🔥

Default. (yeah that's it, that's the whole section, she's lowkey iconic for the brevity 💅)

🌸 STDOUT 🌸

the standard output shall be used to write the contents of the input files.

okay so that's part 1 and bestie we are SO not done yet — there's more more coming (pun fully intended) 💖

💖 STDERR 💖

okay so standard error is the drama channel, bestie. It gets diagnostic messages and user commands (peep the INPUT FILES section), and if standard output is a terminal device, it's also where the prompting string goes. That prompt? It shows up on the screen line below the last line of the file displayed in the current screenful. The prompt has to contain the name of the file currently being examined, and when you're prompting at end-of-file, it also has an end-of-file indication and the name of the next file, if any. If an error or informational message pops up, it's unspecified whether it's inside the prompt. If it's not in the prompt, it gets displayed, then the user is prompted for a continuation character, and at that point another message or the user prompt may show. The prompt is otherwise unspecified. Also unspecified whether informational messages are written for other user commands. 💅

🎀 OUTPUT FILES 🎀

None. Literally none. No output files, bestie. 💀

🌈 EXTENDED DESCRIPTION 🌈

So this whole section? It's about how more acts when standard output is a terminal device. But if standard output is not a terminal device, then no options other than -s do anything, and all input files get copied to standard output otherwise unmodified. After that, more exits without further action. Periodt.

How many lines fit per screen? That's decided by the -n option if it's there, or by checking values in the environment (see the ENVIRONMENT VARIABLES section). If neither gives you a number, then an unspecified number of lines is used. Vibe check failed, basically.

The max lines written is one less than that number, because the screen line after the last written line is reserved for the user prompt and user input. If the screen has fewer than two lines? Results are undefined. And it's unspecified whether user input can be longer than whatever's left of the single line where the prompt got written.

Columns per line? Determined by checking values in the environment (again, ENVIRONMENT VARIABLES), with a default value as described in the Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables.

Lines longer than the display get folded. Where exactly folding happens? Unspecified, but it should be appropriate for the output device. Folding may happen between glyphs of single characters that take up multiple display columns. So like, mid-character, rude but allowed. ✨

When standard output is a terminal and -u is not specified, more shall treat <backspace> and <carriage-return> characters specially:

  • A character, followed first by a sequence of n <backspace> characters (where n is the same as the number of column positions that the character occupies), then by n <underscore> characters ('_'), shall cause that character to be written as underlined text, if the terminal type supports that. The n <underscore> characters, followed first by n <backspace> characters, then any character with n column positions, shall also cause that character to be written as underlined text, if the terminal type supports that. Slay.
  • A sequence of n <backspace> characters (where n is the same as the number of column positions that the previous character occupies) that appears between two identical printable characters shall cause the first of those two characters to be written as emboldened text (that is, visually brighter, standout mode, or inverse-video mode), if the terminal type supports that, and the second to be discarded. Immediately subsequent occurrences of <backspace>/character pairs for that same character shall also be discarded. (For example, the sequence "a\ba\ba\ba" is interpreted as a single emboldened 'a'.)
  • The more utility shall logically discard all other <backspace> characters from the line as well as the character which precedes them, if any.
  • A <carriage-return> at the end of a line shall be ignored, rather than being written as a non-printable character, as described in the next paragraph.

It is implementation-defined how other non-printable characters are written. Implementations should use the same format that they use for the ex print command; see the OPTIONS section within the ed utility. It is unspecified whether a multi-column character shall be separated if it crosses a display line boundary; it shall not be discarded. The behavior is unspecified if the number of columns on the display is less than the number of columns any single character in the line being displayed would occupy.

When each new file is displayed (or redisplayed), more shall write the first screen of the file. Once the initial screen has been written, more shall prompt for a user command. If the execution of the user command results in a screen that has lines in common with the current screen, and the device has sufficient terminal capabilities, more shall scroll the screen; otherwise, it is unspecified whether the screen is scrolled or redrawn.

For all files but the last (including standard input if no file was specified, and for the last file as well, if the -e option was not specified), when more has written the last line in the file, more shall prompt for a user command. This prompt shall contain the name of the next file as well as an indication that more has reached end-of-file. If the user command is f, <control>-F, <space>, j, <newline>, d, <control>-D, or s, more shall display the next file. Otherwise, if displaying the last file, more shall exit. Otherwise, more shall execute the user command specified.

Several of the commands described in this section display a previous screen from the input stream. In the case that text is being taken from a non-rewindable stream, such as a pipe, it is implementation-defined how much backwards motion is supported. If a command cannot be executed because of a limitation on backwards motion, an error message to this effect shall be displayed, the current screen shall not change, and the user shall be prompted for another command.

If a command cannot be performed because there are insufficient lines to display, more shall alert the terminal. If a command cannot be performed because there are insufficient lines to display or a / command fails: if the input is the standard input, the last screen in the file may be displayed; otherwise, the current file and screen shall not change, and the user shall be prompted for another command.

The interactive commands in the following sections shall be supported. Some commands can be preceded by a decimal integer, called count in the following descriptions. If not specified with the command, count shall default to 1. In the following descriptions, pattern is a basic regular expression, as described in the Base Definitions volume of POSIX.1‐2017, Section 9.3, Basic Regular Expressions. The term examine is historical usage meaning open the file for viewing; for example, more foo would be expressed as examining file foo.

In the following descriptions, unless otherwise specified, line is a line in the more display, not a line from the file being examined.

In the following descriptions, the current position refers to two things:

  1. The position of the current line on the screen
  2. The line number (in the file) of the current line on the screen

Usually, the line on the screen corresponding to the current position is the third line on the screen. If this is not possible (there are fewer than three lines to display or this is the first page of the file, or it is the last page of the file), then the current position is either the first or last line on the screen as described later.

💖 Help 💖

Synopsis:

h

Write a summary of these commands and other implementation-defined commands. The behavior shall be as if the more utility were executed with the -e option on a file that contained the summary information. The user shall be prompted as described earlier in this section when end-of-file is reached. If the user command is one of those specified to continue to the next file, more shall return to the file and screen state from which the h command was executed.

💖 Scroll Forward One Screenful 💖

Synopsis:

[count]f
[count]<control>-F

Scroll forward count lines, with a default of one screenful. If count is more than the screen size, only the final screenful shall be written.

💖 Scroll Backward One Screenful 💖

Synopsis:

[count]b
[count]<control>-B

Scroll backward count lines, with a default of one screenful (see the -n option). If count is more than the screen size, only the final screenful shall be written.

💖 Scroll Forward One Line 💖

Synopsis:

[count]<space>
[count]j
[count]<newline>

Scroll forward count lines. The default count for the <space> shall be one screenful; for j and <newline>, one line. The entire count lines shall be written, even if count is more than the screen size.

💖 Scroll Backward One Line 💖

Synopsis:

[count]k

Scroll backward count lines. The entire count lines shall be written, even if count is more than the screen size.

💖 Scroll Forward One Half Screenful 💖

Synopsis:

[count]d
[count]<control>-D

Scroll forward count lines, with a default of one half of the screen size. If count is specified, it shall become the new default for subsequent d, <control>-D, and u commands.

💖 Skip Forward One Line 💖

Synopsis:

[count]s

Display the screenful beginning with the line count lines after the last line on the current screen. If count would cause the current position to be such that less than one screenful would be written, the last screenful in the file shall be written.

💖 Scroll Backward One Half Screenful 💖

Synopsis:

[count]u
[count]<control>-U

Scroll backward count lines, with a default of one half of the screen size. If count is specified, it shall become the new default for subsequent d, <control>-D, u, and <control>-U commands. The entire count lines shall be written, even if count is more than the screen size.

💖 Go to Beginning of File 💖

Synopsis:

[count]g

Display the screenful beginning with line count.

💖 Go to End-of-File 💖

Synopsis:

[count]G

If count is specified, display the screenful beginning with the line count. Otherwise, display the last screenful of the file.

💖 Refresh the Screen 💖

Synopsis:

r
<control>-L

Refresh the screen.

💖 Discard and Refresh 💖

Synopsis:

R

okay so this one refreshes the screen and tosses out any buffered input you had chillin' there. 💅 BUT — and this is the plot twist — if the current file is non-seekable, that buffered input does not get discarded, and R is literally just equivalent to the r command. no cap. 🫶

🎀 Mark Position 🎀

Synopsis:

mletter

Mark the current position with the letter named by letter, where letter is one of the lowercase letters of the portable character set. heads up tho: when a new file is examined, all your marks may just vanish into the void. 💀

✨ Return to Mark ✨

Synopsis:

'letter

Return to the position you previously marked with the letter named by letter, and make that line the current position. it's giving time travel fr fr 🦋

🦋 Return to Previous Position 🦋

Synopsis:

''

Return to the position from which the last large movement command was executed — and yes, "large movement" is defined as any movement of more than a screenful of lines. 😭 If no such movements have been made, it returns to the beginning of the file. iconic behavior, honestly.

🔥 Search Forward for Pattern 🔥

Synopsis:

[count]/[!]pattern<newline>

Display the screenful beginning with the countth line containing the pattern. The search starts after the first line currently displayed. The null regular expression (/ followed by a <newline>) repeats the search using the previous regular expression, with a default count. If the ! character is included, the matching lines are the ones that do not contain the pattern. And if no match is found for the pattern, a message to that effect gets displayed. we've all been there bestie 🙈

🌸 Search Backward for Pattern 🌸

Synopsis:

[count]?[!]pattern<newline>

Display the screenful beginning with the countth previous line containing the pattern. The search starts on the last line before the first line currently displayed. The null regular expression (? followed by a <newline>) repeats the search using the previous regular expression, with a default count. If the ! character is included, matching lines are the ones that do not contain the pattern. If no match is found for the pattern, a message to that effect gets displayed. 🫶

Synopsis:

[count]n

Repeat the previous search for the *count*th line containing the last pattern — or not containing the last pattern, if the previous search was /! or ?!. she remembers everything, main character energy 👑

🧚 Repeat Search in Reverse 🧚

Synopsis:

[count]N

Repeat the search in the opposite direction of the previous search, for the *count*th line containing the last pattern — or not containing the last pattern, if the previous search was /! or ?!. same energy, opposite direction 💫

🍓 Examine New File 🍓

Synopsis:

:e [filename]<newline>

Examine a new file. If the filename argument is not specified, the current file (see the :n and :p commands below) gets re-examined. The filename is subjected to the process of shell word expansions (see Section 2.6, Word Expansions); if more than a single pathname results, the effects are unspecified — so like, don't do that. 😭 If filename is a <number-sign> (#), the previously examined file gets re-examined. If filename is not accessible for any reason (including that it is a non-seekable file), an error message to this effect gets displayed and the current file and screen shall not change. slay, stability. 🛡️

⭐ Examine Next File ⭐

Synopsis:

[count]:n

Examine the next file. If a number count is specified, the countth next file gets examined. If filename refers to a non-seekable file, the results are unspecified. just so you know 🙈

🌈 Examine Previous File 🌈

Synopsis:

[count]:p

Examine the previous file. If a number count is specified, the countth previous file gets examined. If filename refers to a non-seekable file, the results are unspecified. same warning, other direction 🎀

💖 Go to Tag 💖

Synopsis:

:t tagstring<newline>

If the file containing the tag named by the tagstring argument is not the current file, examine that file, exactly as if the :e command had been executed with that file as the argument. Otherwise, or in addition, display the screenful beginning with the tag, as described for the -t option (see the OPTIONS section). And if the ctags utility is not supported by the system, using :t produces undefined results. 💀

🦋 Invoke Editor 🦋

Synopsis:

v

Invoke an editor to edit the current file being examined. If standard input is being examined, the results are unspecified. The name of the editor is taken from the environment variable EDITOR, or defaults to vi. If the last pathname component in EDITOR is either vi or ex, the editor gets invoked with a -c linenumber command line argument, where linenumber is the line number of the file line containing the display line currently displayed as the first line of the screen. It is implementation-defined whether line-setting options are passed to editors other than vi and ex. iykyk 💅

When the editor exits, more resumes with the same file and screen as when the editor was invoked. no notes, flawless comeback ✨

🎀 Display Position 🎀

Synopsis:

=
<control>-G

Write a message for which the information references the first byte of the line after the last line of the file on the screen. This message includes the name of the file currently being examined, its number relative to the total number of files there are to examine, the line number in the file, the byte number and the total bytes in the file, and what percentage of the file precedes the current position. If more is reading from standard input, or the file is shorter than a single screen, then the line number, the byte number, the total bytes, and the percentage need not be written. 💜

👑 Quit 👑

Synopsis:

q
:q
ZZ

Exit more. that's it, that's the command. periodt. 💅✨

💀 EXIT STATUS 💀

The following exit values shall be returned:

  • 0 — Successful completion. we ate, no crumbs 🍓
  • >0 — An error occurred. oop- 😭

🙈 CONSEQUENCES OF ERRORS 🙈

If an error is encountered accessing a file when using the :n command, more shall attempt to examine the next file in the argument list, but the final exit status shall be affected. If an error is encountered accessing a file via the :p command, more shall attempt to examine the previous file in the argument list, but the final exit status shall be affected. If an error is encountered accessing a file via the :e command, more shall remain in the current file and the final exit status shall not be affected. lowkey the most forgiving one of the three 🫶

The following sections are informative.

🌸 APPLICATION USAGE 🌸

When standard output is not a terminal, only the -s filter-modification option is effective. This is based on historical practice. For example, a typical implementation of man pipes its output through more -s to squeeze excess white space for terminal users. When man is piped to lp, however, it is undesirable for this squeezing to happen. context: immaculate ✨

⭐ EXAMPLES ⭐

The -p option allows arbitrary commands to be executed at the start of each file. Examples are:

  • more -p G file1 file2 — examine each file starting with its last screenful. 👑
  • more -p 100 file1 file2 — examine each file starting with line 100 in the current position (usually the third line, so line 98 would be the first line written). 🔢
  • more -p /100 file1 file2 — examine each file starting with the first line containing the string "100" in the current position 🔍

🎀 RATIONALE 🎀

okay so why is more like this? The more utility, available in BSD and BSD-derived systems, was chosen as the prototype for the POSIX file display program since it is more widely available than either the public-domain program less or than pg, a pager provided in System V. 💅

The 4.4 BSD more is the model for the features selected; it is almost fully upwards-compatible from the 4.3 BSD version in wide use and has become more amenable for vi users. ✨

Several features originally derived from various file editors, found in both less and pg, have been added to this volume of POSIX.1‐2017 as they have proved extremely popular with users. 🫶

There are inconsistencies between more and vi that result from historical practice. For example, the single-character commands h, f, b, and <space> are screen movers in more, but cursor movers in vi. These inconsistencies were maintained because the cursor movements are not applicable to more and the powerful functionality achieved without the use of the control key justifies the differences. 😭

The tags interface has been included in a program that is not a text editor because it promotes another degree of consistent operation with vi. It is conceivable that the paging environment of more would be superior for browsing source code files in some circumstances. 🦋

The operating mode referred to for block-mode terminals effectively adds a <newline> to each Synopsis line that currently has none. So, for example, d<newline> would page one screenful. The mode could be triggered by a command line option, environment variable, or some other method. The details are not imposed by this volume of POSIX.1‐2017 because there are so few systems known to support such terminals. Nevertheless, it was considered that all systems should be able to support more given the exception cited for this small community of terminals because, in comparison to vi, the cursor movements are few and the command set relatively amenable to the optional <newline> characters. 👑

Some versions of more provide a shell escaping mechanism similar to the ex ! command. The standard developers did not consider that this was necessary in a paginator, particularly given the wide acceptance of multiple window terminals and job control features. (They chose to retain such features in the editors and mailx because the shell interaction also gives an opportunity to modify the editing buffer, which is not applicable to more.) 💀

The -p (position) option replaces the + command because of the Utility Syntax Guidelines. The +command option is no longer specified by POSIX.1‐2008 but may be present in some implementations. In early proposals, it took a pattern argument, but historical less provided the more general facility of a command. It would have been desirable to use the same -c as ex and vi, but the letter was already in use. 🌈

The text stating from a non-rewindable stream ... implementations may limit the amount of backwards motion supported would allow an implementation that permitted no backwards motion beyond text already on the screen. It was not possible to require a minimum amount of backwards motion that would be effective for all conceivable device types. The implementation should allow the user to back up as far as possible, within device and reasonable memory allocation constraints. 🧚

Historically, non-printable characters were displayed using the ARPA standard mappings, which are as follows:

  1. Printable characters are left alone. 🌸
  2. Control characters less than \177 are represented as followed by the character offset from the '@' character in the ASCII map; for example, \007 is represented as 'G'. 😭
  3. \177 is represented as followed by '?'. 💅

The display of characters having their eighth bit set was less standard. Existing implementations use hex (0x00), octal (\000), and a meta-bit display. (The latter displayed characters with their eighth bit set as the two characters "M-", followed by the seven-bit display as described previously.) The latter probably has the best claim to historical practice because it was used with the -v option of 4 BSD and 4 BSD-derived versions of the cat utility since 1980. 🔥

No specific display format is required by POSIX.1‐2008. Implementations are encouraged to conform to historic practice in the absence of any strong reason to diverge. ⭐

🦋 FUTURE DIRECTIONS 🦋

None. literally none bestie. 🎀

👑 SEE ALSO 👑

  • Chapter 2, Shell Command Language, ctags, ed, ex, vi
  • The Base Definitions volume of POSIX.1‐2017, Chapter 8, Environment Variables, Section 9.2, Regular Expression General Requirements, Section 9.3, Basic Regular Expressions, Section 12.2, Utility Syntax Guidelines

Okay legal bestie, here's the exact receipts:

Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .
Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .

source/version: IEEE/The Open Group; date: 2017; page: MORE(1P). okay bye bestie, slay your pager journey 💅✨🦋

📦 where this page comes from