Joseph Wright
Joseph Wright
Sounds good to me - and perhaps we could add `\exp_after:w` as an alias for `\exp_after:wN` at the same time (i.e. no deprecation but allow people to choose - I'd...
> [@josephwright](https://github.com/josephwright) you argued `N` was right once:-) https://tex.stackexchange.com/questions/493129/why-is-exp-afterwn-named-exp-afterwn Yeah, but we are trying always to improve :) > I may be wrong but I have a feeling it was...
@blefloch , @Skillmon One of you want to write a PR?
As pointed out, we special-cases `\exp_after:wN` as the `w` is 'almost-`N`' and it's a very important function - I think on the grounds the proposed `\exp_after:nwN` would make most sense.
See also comments in `l3backend` about which primitives are needed to 'track' annotations.
I've spotted some issues - to raise with the team.,
@davidcarlisle Has a suggestion that deals with my concern ...
> But the major deficiency is not explaining why such structures are needed at the l3 level? Rather than providing only user-level commands and/or environments. How else does one implement...
I just remembered that I had the same issue when implementing `xbox` in the trial area. There I went for `parbox_to_wd`, etc. - may be worth taking another look before...
It's quite tricky to know if a function starts a line, and particularly at the code level the performance hit here doesn't feel great. I also think there's a danger...