GNU nano - Bugs: bug #47391, an include file allows 'bind' and...
You are not allowed to post comments on this tracker with your current authentication level.
bug #47391: an include file allows 'bind' and 'unbind'
Submitter: | Benno Schulenberg <bens> | ||
Submitted: | Fri 11 Mar 2016 04:59:02 PM UTC | ||
Severity: | 2 - Minor | Status: | Fixed |
Assigned to: | bens | Open/Closed: | Closed |
Wed 27 Apr 2016 08:18:51 AM UTC, comment #1: |
Benno Schulenberg <bens> |
Fri 11 Mar 2016 04:59:02 PM UTC, original submission:
When the include-file mechanism was made, the intention was to only allow syntax definitions in such a file. At that time that ecompassed the commands syntax, color, and icolor. Meanwhile the repertoire has grown with header, magic, linter, and formatter.
|
Benno Schulenberg <bens> |
No files currently attached
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 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-06-20 | bens | Open/Closed | Open | Closed | |
2016-04-27 | bens | Status | None | Fixed |
Powered by Savane 3.13-758e.
Corresponding source code
Fixed in git, 9330aa6.
To avoid a fivefold repetition of the test on permissibility, the new code will just say about any command that is not allowed that it is not allowed in an included file, also about commands that don't exist. If you put for example "foop twelve" in an include file, it will say that Command 'foop' is not allowed in an included file. I think that is good enough.