Geany does not find some rather obvious brace pairs. I edited my .bashrc file. Its recognized filetype is "Config file" (I do not know, why.)
For testing, paste this text into an empty file, and issue a "Set Filetype"/Miscellaneous/"Config file" command.
The matching pair sometimes is found, sometimes isn't:
-------- aa {} good aa [] good aa () good aa {:} bad aa [:] bad aa (:) bad {:} good [:] good (:) good {:} bad [:] good (:) bad --------
Le 03/03/2015 18:36, Péter a écrit :
Geany does not find some rather obvious brace pairs. I edited my .bashrc file. Its recognized filetype is "Config file" (I do not know, why.)
For testing, paste this text into an empty file, and issue a "Set Filetype"/Miscellaneous/"Config file" command.
The matching pair sometimes is found, sometimes isn't:
[…]
Braces are only considered matching if they share the same style (which might or might not be displayed differently).
The problem you have is that the "Config file" filetype considers most of your colons as separators between what it thinks is the "key" and the value. This filetype is supposed to handle files like this:
[header] key = value key: value
and it recognizes both `:` and `=` as value separators.
So it's not a bug, you're just using a file type for which "matching braces" is more or less meaningless -- especially as your data doesn't conform to the file type's expectancies.
Just set the filetype to "Shell script" and all should be good.
Regards, Colomban
Le 03/03/2015 20:50, Péter a écrit :
Colomban Wendling:
Just set the filetype to "Shell script" and all should be good.
How to do that? (Permanently)
add .bashrc (or whichever pattern you want) to filetype_extensions.conf's Sh= list (see http://www.geany.org/manual/#filetype-extensions)
And https://github.com/geany/geany/pull/291 BTW, which IIUC only needs a little cleanup before getting merged.
Regards, Colomban
PS: BTW, .bashrc is currently recognized as Config file because of the patter "*rc".