At 2020-12-20T22:44:09-0600, Dave Kemper wrote:
> On 12/20/20, G. Branden Robinson wrote:
> > At 2020-12-16T20:30:33-0600, Dave Kemper wrote:
> >> Ubuntu is a Debian-derived distro, and the concurrent "local timezone"
> >> thread here points out Debian's proclivity to customize groff in
> >> incom
On 12/20/20, G. Branden Robinson wrote:
> At 2020-12-16T20:30:33-0600, Dave Kemper wrote:
>> Ubuntu is a Debian-derived distro, and the concurrent "local timezone"
>> thread here points out Debian's proclivity to customize groff in
>> incompatible ways.
>
> I don't think that statement is quite fa
At 2020-12-16T20:30:33-0600, Dave Kemper wrote:
> On 12/15/20, Dorai Sitaram wrote:
> > Thanks Dave, for the suggestion. That doesn't seem to be the
> > problem, however, on my machine (Ubuntu 20.10). No-argument cat
> > works as expected.
>
> Then something peculiar to the Ubuntu groff seems
Thank you, Keith!
--d
On Thursday, December 17, 2020, 12:48:35 PM EST, Keith Marshall
wrote:
On 17/12/2020 14:37, Dorai Sitaram via wrote:
> Wow, this (Oliver's suggestion) actually works. ...
I don't know why I even bother!
https://lists.gnu.org/archive/html/groff/2020-12/msg00053
If you're using preprocessors and you're on Linux, then
instead of ".rd" you could try
.so /dev/tty
and terminate keyboard input with end-of-file (usually control-d)
or ".nx" on a line by itself.
Example:
echo -e '.pl 10\nFoo\n.so /dev/tty\nbar\n.so /dev/tty\nbaz' | groff -Tascii
and the
On 17/12/2020 14:37, Dorai Sitaram via wrote:
> Wow, this (Oliver's suggestion) actually works. ...
I don't know why I even bother!
https://lists.gnu.org/archive/html/groff/2020-12/msg00053.html
FWIW, .rd does work in Ubuntu 20.04
-Jim
$ echo ".rd" >/tmp/test.tr ; groff -Tascii /tmp/test.tr | cat -s
foo
bar
[^D]
foo bar
;-)
On 17/12/2020 15:37, Dorai Sitaram via wrote:
Wow, this (Oliver's suggestion) actually works. I get a bunch of diagnostics
like this:
Use of uninitialized value $file in substr at /usr/local/bin/gropdf line 615,
<__ANONIO__> line 95. Use of uninitialized value $name in concaten
Wow, this (Oliver's suggestion) actually works. I get a bunch of diagnostics
like this:
Use of uninitialized value $file in substr at /usr/local/bin/gropdf line 615,
<__ANONIO__> line 95. Use of uninitialized value $name in concatenation
(.) or string at /usr/local/bin/gropdf line 621,
Hi,
perhaps Dorai's shell is the culprit?
Can you run the following, actually just a variation of the first trial:
$ groff - -T pdf << EOF > myfile.pdf
.rd
This is some input, it will show in the pdf file.
EOF
As soon as the system waits for you to enter the lines beginning with
.rd, the prom
On Wed, Dec 16, 2020 at 08:30:33PM -0600, Dave Kemper wrote:
> On 12/15/20, Dorai Sitaram wrote:
> > Thanks Dave, for the suggestion. That doesn't seem to be the problem,
> > however, on my machine (Ubuntu 20.10). No-argument cat works as expected.
>
> Then something peculiar to the Ubuntu groff
On 12/15/20, Dorai Sitaram wrote:
> Thanks Dave, for the suggestion. That doesn't seem to be the problem,
> however, on my machine (Ubuntu 20.10). No-argument cat works as expected.
Then something peculiar to the Ubuntu groff seems to be behind this.
Ubuntu is a Debian-derived distro, and the co
Thanks Dave, for the suggestion. That doesn't seem to be the problem, however,
on my machine (Ubuntu 20.10). No-argument cat works as expected.
--dOn Tuesday, December 15, 2020, 04:50:01 PM EST, Dave Kemper
wrote:
On 12/15/20, Oliver Corff wrote:
> I have no other version at hand so
On 15/12/2020 20:52, Dorai Sitaram via wrote:
> Thanks, Oliver. I'm using
>
> GNU groff version 1.23.0.rc1.69-8e09f
>
> Tried your exact same file, and it just whizzes to completion without
> prompting for my input. Also on groff 1.22.4.
It works for me, on Manjaro's (Arch) groff-1.22.4, but on
On 12/15/20, Oliver Corff wrote:
> I have no other version at hand so I cannot check. Maybe you try 1.22.3,
Oliver,
I ran the simple example you posted using groff 1.22.4 and groff
1.23.0.rc1, and it behaved as you described under both versions. So
the problem does not appear to be related to t
Hi Dorai,
I have no other version at hand so I cannot check. Maybe you try 1.22.3,
it should be available in many software distributions.
Oliver.
On 15/12/2020 21:52, Dorai Sitaram via wrote:
Thanks, Oliver. I'm using
GNU groff version 1.23.0.rc1.69-8e09f
Tried your exact same file, and i
Thanks, Oliver. I'm using
GNU groff version 1.23.0.rc1.69-8e09f
Tried your exact same file, and it just whizzes to completion without prompting
for my input. Also on groff 1.22.4. Checked if I was using an alias for groff
that could screw things up: No. All my GROFF* environment variables lo
Hi again,
I tested the one-liner against all installed macro packages (man, mdoc,
me, mm, mom, ms), the request .rd works as expected.
Oliver.
On 15/12/2020 19:59, Dorai Sitaram via wrote:
groff.texi mentions the request .rd that's supposed to read user input mid-run,
but I can't seem to get
PS: My version is groff 1.22.3.
Oliver.
On 15/12/2020 20:17, Oliver Corff wrote:
Hi,
for me, it works as described in the info file.
Minimal working example: create a file "myfile.ro" which contains just
one line:
.rd
Say
$ groff myfile.ro > myfile.ps
As soon as you hit the terminal will
Hi,
for me, it works as described in the info file.
Minimal working example: create a file "myfile.ro" which contains just
one line:
.rd
Say
$ groff myfile.ro > myfile.ps
As soon as you hit the terminal will wait for input. Write, e.g.:
This is a line of text.
Hit twice, as groff needs a
groff.texi mentions the request .rd that's supposed to read user input mid-run,
but I can't seem to get it work at all. No prompt, just quite ignoration.
--d
21 matches
Mail list logo
