GNU nano - Bugs: bug #55435, [Request] allow quotestr to be...
You are not allowed to post comments on this tracker with your current authentication level.
bug #55435: [Request] allow quotestr to be changed per syntax definition
Submitter: | David Griffith <dgriffi> | ||
Submitted: | Thu 10 Jan 2019 10:52:34 AM UTC | ||
Severity: | 1 - Wish | Status: | Wont Fix |
Assigned to: | None | Open/Closed: | Closed |
Jump to the original submission
Fri 15 Mar 2019 06:14:37 PM UTC, comment #11: |
Benno Schulenberg <bens> |
Thu 24 Jan 2019 06:58:50 AM UTC, comment #10: Works for me. Thanks for accepting the changes. |
David Griffith <dgriffi> |
Wed 23 Jan 2019 07:06:41 PM UTC, comment #9: Thanks for the patches. I have, however, opted for a much conciser wording. See commit 2eb19605. |
Benno Schulenberg <bens> |
Wed 23 Jan 2019 04:30:21 PM UTC, comment #8: Another patch to clean up the blurbs. Please add both patches and then squash/fixup as you see fit. |
David Griffith <dgriffi> |
Wed 23 Jan 2019 04:11:46 PM UTC, comment #7: In the patch I uploaded, I didn't notice that you already changed the default regex. I was operating under the assumption that none of those changes would be made, that I would just add commentary on how useful quotestr is to rejustifying blocks of line comments. I'll upload a new patch to clean up that mess. |
David Griffith <dgriffi> |
Wed 23 Jan 2019 04:05:09 PM UTC, comment #6: Patch attached. |
David Griffith <dgriffi> |
Tue 22 Jan 2019 07:16:33 PM UTC, comment #5: The proposed expansion of the quoting regex has been pushed to master, commit c5a72103.
|
Benno Schulenberg <bens> |
Tue 15 Jan 2019 05:12:54 PM UTC, comment #4: After doing:
|
Benno Schulenberg <bens> |
Mon 14 Jan 2019 07:45:28 PM UTC, comment #3: Setting the quotestr per syntax is not needed, and a patch for that will not be accepted. But you are welcome to submit a patch describing how quotestr can be used to enable rewrapping a block of comment lines. |
Benno Schulenberg <bens> |
Fri 11 Jan 2019 11:03:53 PM UTC, comment #2: Not the double-slash comments, but hashmarks. Whenever I needed a block of comments in a language that used those, I used the begin/end type of comments (ie, "/*" and "*/".
|
David Griffith <dgriffi> |
Fri 11 Jan 2019 06:43:32 PM UTC, comment #1: Comment blocks that start with "//" (double slash) have become justifiable only last June, so when you're saying you've been doing this for a long time, this makes me wonder.
|
Benno Schulenberg <bens> |
Thu 10 Jan 2019 10:52:34 AM UTC, original submission:
It would be nice be able to do "set quotestr" or some equivalent within a syntax definition.
|
David Griffith <dgriffi> |
Depends on the following items: None found
Items that depend on this one: None found
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 7 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-03-15 | bens | Open/Closed | Open | Closed | |
2019-01-23 | dgriffi | Attached File | - | Added quotestr-2.patch, #46079 | |
2019-01-23 | dgriffi | Attached File | - | Added quotestr.patch, #46078 | |
2019-01-14 | bens | Status | None | Wont Fix | |
Summary | {Request] allow quotestr to be changed per syntax definition | [Request] allow quotestr to be changed per syntax definition | |||
2019-01-11 | bens | Severity | 3 - Normal | 1 - Wish | |
Summary | Allow quotestr to be changed per syntax definition | {Request] allow quotestr to be changed per syntax definition |
Powered by Savane 3.13-f8d8.
Corresponding source code
Closing, as the default quoting regex has been extended, and the documentation has been changed to mention what it can be used for.