[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: @verb issues
From: |
Werner LEMBERG |
Subject: |
Re: @verb issues |
Date: |
Sun, 04 Dec 2022 15:08:36 +0000 (UTC) |
>> I disagree, since this means that two input characters map to the
>> same output character, which is against the term 'verbatim', isn't
>> it? Additionally, you get the wrong values if you do a
>> cut-and-paste operation.
>
> Is there a reason you can't use @set txicodequote*?
Of course I can, and I do, but I think that `@verb` should always
exactly reflect the input characters (with the exception of `\n`).
> As I said before, I'm open to the idea of turning on @set
> txicodequote* by default.
This is a good idea IMHO.
Werner
- Re: @verb issues, (continued)
- Re: @verb issues, Gavin Smith, 2022/12/07
- Re: @verb issues, Werner LEMBERG, 2022/12/07
- Re: @verb issues, Gavin Smith, 2022/12/10
- Re: @verb issues, Werner LEMBERG, 2022/12/10
- w-nolinebreak-text class in HTML output, Gavin Smith, 2022/12/10
- Re: w-nolinebreak-text class in HTML output, Patrice Dumas, 2022/12/10
- Re: @verb issues, Gavin Smith, 2022/12/04
Re: @verb issues, Werner LEMBERG, 2022/12/04