-
Notifications
You must be signed in to change notification settings - Fork 769
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
\pnums in effects/returns/etc. are confusing #821
Comments
I disagree that it's not possible to tell, because as far as I'm aware they're always part of that clause. (Unless you have examples where that isn't the case?) |
We have some paragraphs that come first, before any of the Effects: or Returns: elements, e.g. to introduce variables that are used in the elements that follow e.g. [tuple.creation] p2. But they're unambiguous, they're not part of the Effects: or anything else, because they come before them. But if all paragraphs that come after one of the named elements are part of the previous element, then that's also unambiguous, and I see no need to change anything. |
@burblebee: Do you have specific examples where @jwakely's assertion is false? Please state them for inspection. |
Closing for lack of specific examples that need work. |
When a \pnum is used within an effects/returns/etc. clause, it's not possible to tell if the new paragraph is part of that clause, or is a new paragraph that happens to follow the clause.
For example, where do the effects end in the following? :
This makes it clear:
bla bla bla. This paragraph is part of the effects.
It would be good to have a way to fix the issue above. If not by replacing \pnums with \pars, then how?
Note: This was originally part of issue #781, but we could not come up with a resolution for it, so it was separated out into its own issue so that the rest of #781 can be resolved and closed. See the discussions in #781.
The text was updated successfully, but these errors were encountered: