diff options
author | Norbert Preining <norbert@preining.info> | 2019-09-02 13:46:59 +0900 |
---|---|---|
committer | Norbert Preining <norbert@preining.info> | 2019-09-02 13:46:59 +0900 |
commit | e0c6872cf40896c7be36b11dcc744620f10adf1d (patch) | |
tree | 60335e10d2f4354b0674ec22d7b53f0f8abee672 /info/challenges/aro-bend/answer.013 |
Initial commit
Diffstat (limited to 'info/challenges/aro-bend/answer.013')
-rw-r--r-- | info/challenges/aro-bend/answer.013 | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/info/challenges/aro-bend/answer.013 b/info/challenges/aro-bend/answer.013 new file mode 100644 index 0000000000..f88645d7e6 --- /dev/null +++ b/info/challenges/aro-bend/answer.013 @@ -0,0 +1,24 @@ +[This was included as a self-decoding answer in the posting of Exercise +#13; see exercise.013] + +Answers to Around the Bend #13: + +(a) No. (b) No. In other words, a blank line will produce a \par if +and only if endline characters are present and have catcode 5. It is +interesting to note that two consecutive endline characters are not +translated simply to \par, but to <space>\par. (The space will +disappear in some circumstances, e.g., after a control word, according +to TeX's normal scanning rules.) This is the reason (or at least one +reason) that a \par operation must perform an implicit \unskip +operation. There was also a recent post to comp.text.tex by Donald +Arseneau to point out the problem with someone's delimited-argument +macro definition: + + \def\something#1.\par{<do something with #1>} + +The delimiter string ".\par" did not match the actual text + + ... some text. + <blank line> + +because of the space token following the period.. |