xfree86: Handle config files ending without newline
The config parser expects to find a newline at the end of each line, so files ending without one would confuse it. A newline is inserted at the end of the buffer in these situations. Additionally, switching to the next config file is moved to the higher level to allow parsing of the last line of the previous file to complete before shifting the index and resetting the line number. Signed-off-by: Dan Nicholson <dbn.lists@gmail.com> Tested-by: Stephan Raue<stephan.raue@gmx.net> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
This commit is contained in:
parent
67bc278a51
commit
8b1a685f00
|
@ -227,14 +227,16 @@ xf86getNextLine(void)
|
|||
configFiles[curFileIndex].file);
|
||||
|
||||
if (!ret) {
|
||||
/* stop if there are no more files */
|
||||
if (++curFileIndex >= numFiles) {
|
||||
curFileIndex = 0;
|
||||
/*
|
||||
* if the file doesn't end in a newline, add one
|
||||
* and trigger another read
|
||||
*/
|
||||
if (pos != 0) {
|
||||
strcpy(&configBuf[pos], "\n");
|
||||
ret = configBuf;
|
||||
} else
|
||||
break;
|
||||
}
|
||||
configLineNo = 0;
|
||||
continue;
|
||||
}
|
||||
|
||||
/* search for EOL in the new block of chars */
|
||||
|
||||
|
@ -338,6 +340,16 @@ again:
|
|||
}
|
||||
if (ret == NULL)
|
||||
{
|
||||
/*
|
||||
* if necessary, move to the next file and
|
||||
* read the first line
|
||||
*/
|
||||
if (curFileIndex + 1 < numFiles) {
|
||||
curFileIndex++;
|
||||
configLineNo = 0;
|
||||
goto again;
|
||||
}
|
||||
else
|
||||
return (pushToken = EOF_TOKEN);
|
||||
}
|
||||
configLineNo++;
|
||||
|
|
Loading…
Reference in New Issue