[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #64484] [troff] .device and \X don't behave the same
From: |
G. Branden Robinson |
Subject: |
[bug #64484] [troff] .device and \X don't behave the same |
Date: |
Thu, 11 Jul 2024 01:43:52 -0400 (EDT) |
Update of bug #64484 (group groff):
Status: Need Info => Postponed
Planned Release: 1.24.0 => None
_______________________________________________________
Follow-up Comment #11:
Postponing; I don't have hope of getting this sorted out in time for _groff_
1.24.
Two differences between the `device` request and `\X` escape sequence concern
me and, at the very least, should be documented.
1. `device` reads its argument in copy mode; `\X` doesn't.
2. `\X` is accepted, and works, at the beginning of input; `device` does
not.
Here are some illustrative cases.
$ printf '\\X@tty: foo\\h#1i#bar@\n' | groff -T ascii -Z
troff:<standard input>:1: error: a horizontal motion is invalid within device
control escape sequence
x T ascii
x res 240 24 40
x init
p1
V40
H0
x font 1 R
f1
s10
V40
H0
md
DFd
x X tty: foobar
n40 0
x trailer
V2640
x stop
$ printf '.device tty: foo\\h#1i#bar\n' | groff -T ascii -Z
x T ascii
x res 240 24 40
x init
p1
x trailer
V2640
x stop
$ printf '\\c\n.device tty: foo\\h#1i#bar\n' | groff -T ascii -Z
x T ascii
x res 240 24 40
x init
p1
V40
H0
x font 1 R
f1
s10
V40
H0
md
DFd
x X tty: foo\h#1i#bar
n40 0
x trailer
V2640
x stop
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?64484>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #64484] [troff] .device and \X don't behave the same,
G. Branden Robinson <=