Is your /acutecomb/ glyph itself a composite of the /acute/ glyph? I am not seeing the behaviour you describe in any of my fonts.
I figured out what happened and an answer is stupidly simple ) I checked a FontLab settings > Open fonts section, and there were two checkboxes active: "Detect composites" and "Detect nonspacing components". So the exported font file itself is ok and all that changes happens on the fly when I open it again.
Sorry for misleading in my previous comment and thank you for the explanations about composites and subroutines!
I am not a font designer but a graphic designer. I don't make fonts but I use them.
There is an open source desktop publishing application called Scribus, it is very restrictive in which fonts it allows to be used in it's documents. It does extensive checking on the installed fonts (and any new ones you install later on) and only allows the fonts which pass all it's checks.
This means that any font which Scribus allows will work on most systems and in most applications, also they will not cause any problems for print shops and publishers.
Comments
I checked a FontLab settings > Open fonts section, and there were two checkboxes active: "Detect composites" and "Detect nonspacing components".
So the exported font file itself is ok and all that changes happens on the fly when I open it again.
Sorry for misleading in my previous comment and thank you for the explanations about composites and subroutines!