GNU nano - Patches: patch #6771, syntax highlighting for PPD
You are not allowed to post comments on this tracker with your current authentication level.
patch #6771: syntax highlighting for PPD
Submitter: | Dave Lemonby <dreamlax> | ||
Submitted: | Mon 09 Mar 2009 02:59:25 AM UTC | ||
Priority: | 3 - Low | Status: | Wont Do |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | Release: | None |
Thu 26 Apr 2018 07:40:49 AM UTC, comment #3: |
Benno Schulenberg <bens>![]() |
Wed 25 Apr 2018 11:38:39 PM UTC, comment #2: I know this issue is ancient, but it's perhaps worth pointing out that vim includes syntax highlighting for PPD files. I gather the two editors tend to cater for different demographics but a few extra kilobytes never hurt anyone ;) |
Dave Lemonby <dreamlax> |
Sat 25 Apr 2015 03:54:29 PM UTC, comment #1: Printer Description files are something I think very few users will want to edit or even look at, so I don't think it's very useful to include the syntax file into nano's tarball. Thanks for sharing, though. |
Benno Schulenberg <bens>![]() |
Mon 09 Mar 2009 02:59:25 AM UTC, original submission:
A file for PPD colour syntax highlighting. Does not handle multi-line strings (because I cannot figure out the correct combination of regular expressions), e.g.
|
Dave Lemonby <dreamlax> |
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 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2018-04-25 | bens | Summary | PPD syntax highlighting | ![]() |
syntax highlighting for PPD |
2015-04-25 | bens | Priority | 5 - Normal | ![]() |
3 - Low |
Status | None | ![]() |
Wont Do | ||
Summary | PPD colour syntax highlighting file | ![]() |
PPD syntax highlighting | ||
2009-03-09 | dreamlax | Attached File | - | ![]() |
Added ppd.nanorc, #17623 |
The thing is, nano fully loads all syntaxes at startup (if the user has not edited /etc/nanorc to pick only those syntaxes that he/she needs). With every syntax I add, the load time increases. This is not a good idea for a small editor like nano. We will first have to devise a system so that nano only loads the syntax that it needs at that moment. But even then, it will have to load upfront all the recognition regexes, so that it can know what syntax to load for which file. These changes are not trivial.
So, although I would like to add as many syntaxes as possible that are somehow useful, currently I try to add only things that are useful to a good number of users.