>> As can be seen in the attached output, there is no hyphen in the
>> split word. I consider this a bug, since there is zero reason for
>> such a surprising (and undocumented) behaviour.
>
> A hyphen could be confusing as it may be treated as a literal part
> of the code. I doubt this has come up much before as people will
> rarely use @- inside @code. Given that people are only putting in
> @- deliberately then it may be harmless to make it print a hyphen.
Exactly my point of view: If the user intentionally inserts `@-`, a
hyphen should be printed.
> However, line breaks at _ and - are allowed inside @code, without
> any extra hyphen being printed. How can the user distinguish
> between hyphens that are taken literally and those that are only for
> word continuation?
I think it is not necessary to distinguish those cases. `@-` is an
explicit user command that Texinfo should simply obey. Additionally,
`@code` isn't a real verbatim environment anyway.
The main reason for me to use `@code` is that it listens to
`txicodequoteundirected` and `txicodequotebacktick`, which `@t` does
not.
>> BTW, you get exactly the same output if you replace `@code` with
>> `@t` – and *this* is definitely a bug :-)
>
> We should test both in any changes we make.
Yep.
Werner
