> I don't disagree with this I am referring about your update external > feature, that is the reason for you to retain the original file path, and > that is what me and other don't want to. > All the disagreement for my part comes from your proposal to keep the > original file path.
To unbundle, you have to know the original path, right? If you do not want to see these path when editing in embed mode, this can certainly be done (easily). > You have recognized that the update of an embedded file should be a rare > case. I defend that this should be outside of lyx design. I am saying also > that this can be done simple in an external layer (no pun intended), the > python library that I have referred. If you are talking about 'update from external file' of an embedded inset, this is done after lyx gets started, and I do not see a reason to call python for this simple task. Please note that embedded files will be used when they are embedded, and external files are ignored. If you move your .lyx file to another system with different external files, lyx should *not* produce different results. This is the whole point of embedding. I want to be produce a .lyx file that can be opened *directly* by anyone on *any OS*, without any change to his lyx/latex system (no installation of .layout and .cls), and produce *identical* output when compiled. Bo
