[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #65980] [troff] diagnose why directory operands can't be opened
|
From: |
G. Branden Robinson |
|
Subject: |
[bug #65980] [troff] diagnose why directory operands can't be opened |
|
Date: |
Sun, 14 Jul 2024 07:49:16 -0400 (EDT) |
Follow-up Comment #4, bug #65980 (group groff):
Oh and of course a symbolic link, perhaps the second most obvious sort of
*roff input file after the regular type.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65980>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
- [bug #65980] emit (better) diagnostics on bad input files, Dave, 2024/07/12
- [bug #65980] [troff] emit diagnostic on unreadable input files, G. Branden Robinson, 2024/07/13
- [bug #65980] [troff] emit diagnostic on unreadable input files, G. Branden Robinson, 2024/07/13
- [bug #65980] [troff] diagnose why directory operands can't be opened, G. Branden Robinson, 2024/07/14
- [bug #65980] [troff] diagnose why directory operands can't be opened, G. Branden Robinson, 2024/07/14
- [bug #65980] [troff] diagnose why directory operands can't be opened,
G. Branden Robinson <=
- [bug #65980] [troff] diagnose why directory operands can't be opened, G. Branden Robinson, 2024/07/14
- [bug #65980] [troff] diagnose why directory operands can't be opened, Dave, 2024/07/14
- [bug #65980] [troff] diagnose why directory operands can't be opened, G. Branden Robinson, 2024/07/30