| Summary: | ASTERISK-10232: Config parser eats blank lines for dinner | ||
| Reporter: | Jared Smith (jsmith) | Labels: | |
| Date Opened: | 2007-09-04 14:02:20 | Date Closed: | 2007-09-12 15:32:06 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/ManagerInterface |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | The Asterisk config parser (that is used by AMI for GetConfig/UpdateConfig, etc.) eats blank lines in the configuration files, which makes it harder for people to read the configuration file after it's been edited by Asterisk. I've talked with murf about this, and he asked me to open a bug and assign it to him. | ||
| Comments: | By: Brandon Kruse (bkruse) 2007-09-04 15:34:44 Does this mean that when I am using updateconfig and getconfig that I can possibly start sending comments also? Also, will it be a lot of overhead to receive/send those ;comments and blank lines? Please keep me updated to see if I need to change the API. Now we just have comment => whatever for context's in the dialplan, and they get parsed. However, I could make the GUI clean up the code, and make it MUCH more editable and readable. This could possibly lead to a perfect integration of creating things in the GUI, and the user being able to edit them, as where now it its kind of convoluted and obfuscated at points. I like it. -bk By: Digium Subversion (svnbot) 2007-09-12 15:32:06 Repository: asterisk Revision: 82288 ------------------------------------------------------------------------ r82288 | murf | 2007-09-12 15:32:05 -0500 (Wed, 12 Sep 2007) | 1 line This fix closes issue ASTERISK-10232 -- it's not perfect, but should retain most blank lines in config files, via read/write cycles. ------------------------------------------------------------------------ | ||