\belowexskip, \aboveglftskip, and \belowglpreambleskip appear to add ~1\parskip even when set to 0pt

[jonorthwash]

Some spacing lengths (\belowexskip, \aboveglftskip, \belowglpreambleskip, and \interpartskip) appear to add approximately one \parskip of length even when set to 0pt.

Some users have reported confusion with this, and others have reported that they use workarounds to solve this: https://tex.stackexchange.com/questions/153373/aboveglftskip-in-expex-linguistic-glosses

One workaround is to set these lengths to -0.5ex, but for me this still results in extra space. Instead, I find that -\parskip works well (at least in my case, where \parskip is 6pt).

[frampton]

Thanks, I will take a look. I always have had \parskip=0pt, so I never noticed the problem.

How about setting parskip to 0pt inside \ex…\xe and \pex..\xe? Temporarily it could be done with the Everyex parameter. More permanently, it could be initialized inside \ex@setup, which is executed immediately whenever \ex or \pex is called.

Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

---

From: Jonathan Washington notifications@github.com Sent: Sunday, March 10, 2019 5:51:14 PM To: frampton/ExPex Cc: Subscribed Subject: [frampton/ExPex] \belowexskip, \aboveglftskip, and \belowglpreambleskip appear to add ~1\parskip even when set to 0pt (#8)

Some spacing lengths (\belowexskip, \aboveglftskip, and \belowglpreambleskip) appear to add approximately one \parskip of length even when set to 0pt.

Some users have reported confusion with this, and others have reported that they use workarounds to solve this: https://tex.stackexchange.com/questions/153373/aboveglftskip-in-expex-linguistic-glosseshttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftex.stackexchange.com%2Fquestions%2F153373%2Faboveglftskip-in-expex-linguistic-glosses&data=02%7C01%7Cj.frampton%40northeastern.edu%7C62693cd896534f2c511e08d6a5a284e5%7Ca8eec281aaa34daeac9b9a398b9215e7%7C0%7C0%7C636878514777162487&sdata=pfx2tZIeeVNugIWuz5hZz9hdxPf3ne%2FghWz9ei8K%2BPQ%3D&reserved=0

One workaround is to set these lengths to -0.5ex, but for me this still results in extra space. Instead, I find that -\parskip works well (at least in my case, where \parskip is 6pt).

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fframpton%2FExPex%2Fissues%2F8&data=02%7C01%7Cj.frampton%40northeastern.edu%7C62693cd896534f2c511e08d6a5a284e5%7Ca8eec281aaa34daeac9b9a398b9215e7%7C0%7C0%7C636878514777162487&sdata=R4Xjh9MHR%2FWHkWNPBJIk4Qx5Fn0SOSqIyOX%2FnW2K6bg%3D&reserved=0, or mute the threadhttps://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA29RAPoAHpQWuiTRda5qjTixdrFgfRbks5vVX5SgaJpZM4bnhsS&data=02%7C01%7Cj.frampton%40northeastern.edu%7C62693cd896534f2c511e08d6a5a284e5%7Ca8eec281aaa34daeac9b9a398b9215e7%7C0%7C0%7C636878514777172492&sdata=W7YRQmYOkqD4SoH%2FftnhKWmghvhYiWD6qtK%2BDgDzJss%3D&reserved=0.

[jonorthwash]

I can confirm that \lingset{Everyex={\parskip=0pt}} does indeed function as a more ideal short-term work-around.

[jonorthwash]

I updated the stackexchange issue with a demonstration of this working.