[bug #65800] bootstrap oddity: .gitignore discrepancy

[Dave]

URL:
  

 Summary: bootstrap oddity: .gitignore discrepancy
   Group: GNU roff
   Submitter: barx
   Submitted: Mon 27 May 2024 07:54:09 PM CDT
Category: Core
Severity: 2 - Minor
  Item Group: Build/Installation
  Status: None
 Privacy: Public
 Assigned to: None
 Open/Closed: Open
 Discussion Lock: Any
 Planned Release: None


___

Follow-up Comments:


---
Date: Mon 27 May 2024 07:54:09 PM CDT By: Dave 
I haven't built a groff since 1.23.  When I did so recently
(http://lists.gnu.org/r/groff/2024-05/msg00042.html), the first step produced
a query I hadn't seen in a groff build before.

$ ./bootstrap
/bin/mv: overwrite '.gitignore'?

I said "y" to this, and the result was that the top-level .gitignore file
gained a "/build-aux" line at the top, before the first comment.  The line
"/build-aux/" (with the trailing slash), already in the file in the "artifacts
expected in a clean tree" section, remained unaltered, so "/build-aux" now
appears twice, once with the trailing slash and once without.

This has no effect I could discern on the rest of the bootstrap or build.  I
don't know whether it constitutes a bug, but it seems weird for the bootstrap
script to require user input to continue, especially devoid of any context
about the significance of the decision, or even which of the tree's many
.gitignore files it refers to.







___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #65654] [preconv] want a warning if code '0xA0' is used in the input

[Dave]

Follow-up Comment #5, bug #65654 (group groff):

Correcting my earlier statement:

[comment #2 comment #2:]
> 0xA0 appears to refer to the Latin-1 character NO-BREAK SPACE
> (Unicode U+00A0)--but there is no reason to run preconv if the
> file is in Latin-1 encoding,

My Latin-1 (ISO 8859-1) blinders were on: the byte 0xA0 is also the no-break
space in encodings ISO 8859-2, ISO 8859-3, ISO 8859-4, etc., any of which
would require preconv.

> Nonetheless, his point remains:

This makes the preceding (mis)statement mostly moot, but I wanted to correct
the record.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #65654] [preconv] want a warning if code '0xA0' is used in the input

[Dave]

Follow-up Comment #4, bug #65654 (group groff):

This proposal (with the warning upgraded to a fatal error) has been offered as
one of the solutions to bug #65710.


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/

[bug #65710] [preconv] require disambiguation of U+00A0 on input

[Dave]

Follow-up Comment #2, bug #65710 (group groff):

[comment #0 original submission:]
> In my opinion preconv should either:
> 
> 1.  Fail and force the user to edit the input to make a real
> choice, eliminating U+00A0 in the input.

This option seems materially the same as the rejected bug #65654, except with
that bug's proposed warning upgraded to a fatal error.  (Granted, #65654 was
rejected a few days before bug #65693 (the current ticket's inciting report)
was opened.)


___

Reply to this item at:

  

___
Message sent via Savannah
https://savannah.gnu.org/