On 04/20/2016 01:20 PM, GNU Support wrote: > Hello, > > Now I understand it, it is not something to be handled by LyX, in that case > it is not a "bug".
It is very unexpected, though, I'll agree. One might wonder whether the space in LyX itself should not be handled as a space in this case. But the truth is that it would be almost impossible to make this work correctlyA. s we often say: When we use TeX code, you are kind of on our own; we can't expect LyX to help us, since it has no idea of knowing what the stuff in TeX code means. Richard > Thank you much for helping me understand that. It bothered me already for > years. > > Jean Louis > > On Wed, Apr 20, 2016 at 06:58:08PM +0100, Jean-Pierre Chrétien wrote: >> Le 20/04/2016 17:10, GNU Support a écrit : >>> Hello >>> >>> You have suggested me to simply cope with it by another method, to >>> include the space in the TeX command instead of using visible available >>> space in LyX. It is not an option. >>> >> Try to export in LaTeX and add as many spaces and even newlines, you will >> never get a space after a (La)TeX command: TeX was build like that, so I >> guess LyX won't go against it and introduce a specific behaviour when >> exporting to LaTeX. >> One space is like 50 in that case, LyX just allows to type in only one, >> that's all. >> >> So adding an unbreakable space in LyX or a space in the command (or an >> \xspace, as suggested by William) is the only way to get what you want. >> >> -- >> Jean-Pierre >> >>
