GNU nano - Bugs: bug #41313, too greedy Python docstring...
You are not allowed to post comments on this tracker with your current authentication level.
bug #41313: too greedy Python docstring highlighting
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Wed 22 Jan 2014 08:44:44 PM UTC | ||
Severity: | 3 - Normal | Status: | Duplicate |
Assigned to: | bens | Open/Closed: | Closed |
Jump to the original submission
Sat 18 Jul 2015 07:39:22 AM UTC, comment #12: |
Benno Schulenberg <bens> |
Sat 11 Jul 2015 06:56:55 AM UTC, comment #11: The underlying issue has been re-reported as bug #45525. See the patch there for a fix. If you could test that patch, that would be great. |
Benno Schulenberg <bens> |
Tue 21 Apr 2015 04:57:49 PM UTC, comment #10: Hello
|
Cem Aydin <rebootl> |
Wed 25 Mar 2015 03:44:41 PM UTC, comment #9: "Misolorations"? Oh dear, that is fishy. :)
|
Benno Schulenberg <bens> |
Mon 23 Mar 2015 12:51:43 PM UTC, comment #8: The misolorations are inherent problem of multiline regexes where the start and stop strings are the same (or very nearly the same). For a more detailed discussion see bug #26762. |
Benno Schulenberg <bens> |
Mon 23 Mar 2015 12:22:30 PM UTC, comment #7: Well, there is a patch for that, but it is costly: it reevaluates the multiline regexes for the whole file for every single edit. On a large file this will probably cause some slowdown. (With src/text.c, 3480 lines, I /think/ to notice a small delay.)
|
Benno Schulenberg <bens> |
Sun 22 Mar 2015 09:32:11 PM UTC, comment #6: Attached example for faulty Syntax highlighting (mesed_up.py) |
Anonymous |
Thu 22 Jan 2015 05:18:36 AM UTC, comment #5: After a bit more investigation it seems to be nanorc dependent.
|
Cody A. Taylor <code_m> |
Wed 21 Jan 2015 09:11:35 PM UTC, comment #4: Do you mean you don't see the problem with 2.2.6 with its native python.nanorc? And with 2.3.99 with *its*native pyhton.nanorc? Or do you use the same nanorc for running both version of nano? If not, could you try? And try running 2.2.6 with the pyhton.nanorc from 2.3.99, and the other way around? |
Benno Schulenberg <bens> |
Tue 20 Jan 2015 05:51:31 PM UTC, comment #3: I've been having this trouble with the latest svn version (2.3.99pre1-svn revision 5104).
|
Cody A. Taylor <code_m> |
Wed 26 Feb 2014 01:10:30 PM UTC, comment #2: Currently the regexes for triple-quoted strings are like this:
|
Benno Schulenberg <bens> |
Tue 25 Feb 2014 02:23:04 AM UTC, comment #1: This can never be implemented properly with nano's current syntax highlighting engine. I've written nanorc files for a few dozen languages already, and this was the only case where I concluded that no highlighting at all was better than a workaround. Not to be dismissive of nano, but the real fix is to use an editor that does full lexical analysis instead of regex matching. |
Anonymous |
Wed 22 Jan 2014 08:44:44 PM UTC, original submission:
When a Python file contains at least two docstrings, things
|
Benno Schulenberg <bens> |
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 |
---|---|---|---|---|---|
2015-12-07 | bens | Open/Closed | Open | Closed | |
2015-07-11 | bens | Status | Need Info | Duplicate | |
2015-03-25 | bens | Status | None | Need Info | |
2015-03-23 | bens | Attached File | - | Added recolor-on-every-edit.patch, #33430 | |
2015-03-22 | None | Attached File | - | Added messed_up.py, #33425 | |
2014-02-26 | bens | Assigned to | None | bens | |
2014-01-22 | bens | Attached File | - | Added whoops.py, #30350 |
Powered by Savane 3.13-f8d8.
Corresponding source code
The basic issue has been fixed in SVN, r5307. The fix should appear in nano-2.4.3.
If with that version you still have any problems with multiline-regex highlighting, please report another bug.