bugGNU troff - Bugs: bug #62938, [grops] search multiple...

 
 

bug #62938: [grops] search multiple "download" files as gropdf does

Submitter:  G. Branden Robinson <gbranden>
Submitted:  Mon 22 Aug 2022 12:02:07 PM UTC
 
Category:  Driver grops Severity:  1 - Wish
Item Group:  Feature change Status:  None
Privacy:  Public Assigned to:  None
Open/Closed:  Open Planned Release:  None
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       No canned response available

 

Sat 17 Sep 2022 01:26:32 PM UTC, comment #3: 

All you say makes sense.

My comment reads as I intended it; however, I was going by only the information posted in #62950, which amounts to a quote from Deri proposing changing only the search order, and a statement of agreement from you.  Digging back into the linked email thread, I see a somewhat more extensive change is discussed there, so the design of the #62950 fix is not as settled as I had presumed in comment #1.

tl;dr: Ignore me.

Dave <barx>
Project Member
Sat 17 Sep 2022 01:27:44 AM UTC, comment #2: 

Hi Dave,

comment #1:

> This bug lists bug #62950 as a dependency, but that bug seems to have consensus on how gropdf should work, and it seems like this bug depends on that design decision rather than on a fix for it.


I'm confused.  Is there a "not" missing from the foregoing?

My intention with this ticket was simply to, once consensus on how gropdf should work was reached, to duplicate the logic in grops as far as that makes sense.

In principle, these could be grouped together as one ticket, or grops revisions could be undertaken first.

But (A) there are separate Savannah categories for the two output drivers, (B) the two implementations are not technologically coupled--we could ship a revised gropdf and and unrevised grops in groff 1.23, for example, and (C) I expect it to be easier to prototype the revised behavior in gropdf.

Am I making any sense?  😅

G. Branden Robinson <gbranden>
Project Administrator
Mon 12 Sep 2022 09:39:21 PM UTC, comment #1: 

This bug lists bug #62950 as a dependency, but that bug seems to have consensus on how gropdf should work, and it seems like this bug depends on that design decision rather than on a fix for it.

Dave <barx>
Project Member
Mon 22 Aug 2022 12:02:07 PM UTC, original submission:  

We're still firming up exactly what "as gropdf does" means, but it would be really nice to get this consistent before releasing 1.23 since we still are not delivering the all-singing, all-dancing, all-font-file-format-converting, automatic-font-description-generating killer font integration tool that every groff user has wanted forever.

See https://lists.gnu.org/archive/html/groff/2022-08/msg00185.html and follow-ups for a discussion, along with some confusion arising from just how frustrating this situation is.

G. Branden Robinson <gbranden>
Project Administrator

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Digest:
   bug dependencies.

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by barx (Posted a comment)
  • -email is unavailable- added by gbranden (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

     

     

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-08-24 gbranden Dependencies- Depends on bugs #62950

    Back to the top

    Powered by Savane 3.9