Line Range Extractor
Extract inclusive one-based hard-line ranges with original separators included for selected lines.
Description
Extract inclusive one-based hard-line ranges with original separators included for selected lines.
Extracting a line range uses one-based editor-style line numbers while retaining the original newline sequences. The returned span identifies exactly which source portion was copied.
When to use this tool
Extract inclusive one-based hard-line ranges with original separators included for selected lines.
- Prepare the supplied text, firstLine, lastLine fields for this operation.
- Compare the complete example with the representation used by your own input before carrying the result into another step.
How to use the tool and how it works
- Enter text, firstLine, lastLine. Use the exact text syntax, units and index conventions explained below.
- Run the tool. If input validation fails, correct the supplied fields before interpreting any result.
- Read result.text, result.start, result.end. Interpret false, null and empty lists using the distinctions below; they can be valid outputs.
Require firstLine and lastLine within parsed lines with lastLine at least firstLine. Concatenate that inclusive range with each original line ending and return source start/end offsets covering the same text.1
| Input field | Meaning and representation | Accepted input |
|---|---|---|
| text | text. | Text; at most 8,192 UTF-16 code units, subject to the grammar above |
| firstLine | first line. | Integer from 1 to a.length inclusive |
| lastLine | last line. | Integer from firstLine to a.length inclusive |
| Output field | Interpretation |
|---|---|
| result | Object containing the named outputs below. |
| result.text | The text value under the stated formula or text convention. |
| result.start | The start value under the stated formula or text convention. |
| result.end | The end value under the stated formula or text convention. |
{
"input": {
"text": "a\nb\nc",
"firstLine": 2,
"lastLine": 2
},
"output": {
"result": {
"text": "b\n",
"start": 2,
"end": 4
}
}
}Limitations and assumptions
- The final selected line's newline is included if present. Empty final lines remain selectable; the tool does not normalize line endings or accept a range beyond the actual line count.
- Text offsets and lengths use UTF-16 code units unless explicitly described as bytes or code points. CRLF, CR and LF are recognized as line endings; a terminal newline creates a final empty line in the shared line model.
- Every declared top-level field is required and unexpected fields are rejected. Numeric inputs must be finite; ordinary text fields are bounded to 8,192 UTF-16 code units, with tighter operation-specific limits where stated.
- Ordinary string lists have at most 128 entries of at most 128 code units each; numeric lists and matrices have separate bounded size checks. Nonfinite results and excessively large serialized outputs are rejected.
- Indexes are zero-based and spans have an exclusive end unless explicitly stated otherwise. A valid false, null or empty-list result is distinct from malformed input.
Alternative or Complementary methods
Use a parser or language-aware editor when quoting, syntax or nested constructs matter. For plain text transforms, keep UTF-16 offsets, Unicode code points, grapheme clusters and UTF-8 byte offsets distinct; apply changes to the same source version used to calculate spans.
References
Similar or alternative tools
- Consecutive Duplicate Line Collapser
Collapse only consecutive identical line contents, retaining each kept line separator; nonadjacent duplicates remain.
- Line and Column to UTF-16 Offset
Map one-based logical line/UTF-16 content column to offset; columns inside separators are intentionally not accepted.