GNU nano - Bugs: bug #56443, [Wish] allow using \t in a string...
You are not allowed to post comments on this tracker with your current authentication level.
bug #56443: [Wish] allow using \t in a string or regex, to represent a tab
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Wed 05 Jun 2019 05:20:42 PM UTC | ||
Severity: | 1 - Wish | Status: | Wont Fix |
Assigned to: | None | Open/Closed: | Closed |
Sun 28 Aug 2022 07:23:43 AM UTC, comment #1: |
Benno Schulenberg <bens> |
Wed 05 Jun 2019 05:20:42 PM UTC, original submission:
Having to type M-V ^I to insert an actual tab character into a regex is akward and the result doesn't look good. It would be nice if nano allowed the use of \t inside regex strings. |
Benno Schulenberg <bens> |
Attached Files
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2022-09-14 | bens | Open/Closed | Open | Closed | |
2022-09-01 | bens | Open/Closed | Closed | Open | |
2022-08-28 | bens | Open/Closed | Open | Closed | |
2022-08-28 | bens | Attached File | - | Added change-backslash-t-in-regex-to-a-tab.patch, #53611 | |
Status | None | Wont Fix | |||
2022-03-14 | bens | Summary | [Request] allow using \t in a string or regex, to represent a tab | [Wish] allow using \t in a string or regex, to represent a tab |
Powered by Savane 3.13-4448.
Corresponding source code
Attached patch interprets \t for regex strings in a nanorc. This would have to be factored out into a function and then called also from parse_next_word() and parse_argument().
But I'm not going to implement that. It would basically mean that everything in a nanorc would get passed over twice, and in the vast majority of cases in vain. That is too much of a waste. Also, no user actually asked for this feature, so... closing.
(file #53611)