Re: [bug #55449] [PATCH] Use FILENAME_MAX in maxfilename.cpp

Ingo Schwarze wrote in <20201021231159.ge12...@athene.usta.de>: ... |Now, arguably, if pathconf(3) fails, which can easily happen if the |input argument is garbage, the function should not return (size_t)-1, |which is a large value. ... |Anyone willing to fix this particular bug? I have

Re: [bug #55449] [PATCH] Use FILENAME_MAX in maxfilename.cpp

Hi Carsten, Carsten Kunze hat am 21. Oktober 2020 um 21:23 geschrieben: > How about at first using pathconf(3) with the constant _PC_NAME_MAX > to determine the file name length (for a specfific path) and using > the constants only when pathconf returns -1? The file already does that, if

[bug #55449] [PATCH] Use FILENAME_MAX in maxfilename.cpp

Update of bug #55449 (project groff): Status: Need Info => Fixed Open/Closed:Open => Closed ___ Follow-up Comment #6: Pushed in

[bug #59317] [PATCH] doc/groff.texi cosmetic cleanup

URL: Summary: [PATCH] doc/groff.texi cosmetic cleanup Project: GNU troff Submitted by: barx Submitted on: Wed 21 Oct 2020 04:14:05 PM CDT Category: Core Severity: 2 -

Re: [bug #55449] [PATCH] Use FILENAME_MAX in maxfilename.cpp

I forgot it need to compile on Windows--sorry for the noise. > Carsten Kunze hat am 21. Oktober 2020 um 21:23 > geschrieben: > > > How about at first using pathconf(3) with the constant _PC_NAME_MAX to > determine the file name length (for a specfific path) and using the constants > only

Re: [bug #55449] [PATCH] Use FILENAME_MAX in maxfilename.cpp

How about at first using pathconf(3) with the constant _PC_NAME_MAX to determine the file name length (for a specfific path) and using the constants only when pathconf returns -1? > Ingo Schwarze hat am 21. Oktober 2020 um 18:43 > geschrieben: > > > Update of bug #55449 (project groff): >

[bug #55449] [PATCH] Use FILENAME_MAX in maxfilename.cpp

Follow-up Comment #5, bug #55449 (project groff): Yes, the patch works, thanks. ___ Reply to this item at: ___ Message sent via Savannah

[bug #55449] [PATCH] Use FILENAME_MAX in maxfilename.cpp

Update of bug #55449 (project groff): Assigned to:None => schwarze Planned Release:None => 1.23 ___ Follow-up Comment #4: The patch #45943 is

[bug #55449] [PATCH] Use FILENAME_MAX in maxfilename.cpp

Follow-up Comment #3, bug #55449 (project groff): Granted, the patch was tested, and works in the port of Groff I use every day since that report. But maybe you wanted a "second opinion"? ___ Reply to this item at:

[bug #55335] [PATCH] preconv produces CR CR LF end-of-line on MS-Windows

Follow-up Comment #2, bug #55335 (project groff): You mean, someone other than myself? ___ Reply to this item at: ___ Message sent via Savannah

Re: [bug #42233] [PATCH] wcwidth(3) used on UCS4/UTF-32 codepoints

|Steffen has withdrawn most/all of his other patches and even after reading I do not know what this has to do with this bug. |this report a few times I'm not clear on what exactly the problem is supposed |to be. | |The "solution", "drop gnulib", is not likely, especially not during an RC

[bug #55557] [PATCH] gropdf, gpinyin, gperl, glilypond, hyphenex can execute arbitrary commands

Follow-up Comment #4, bug #7 (project groff): Commit 2fc912f0751320a1fba0094dded38e2df46d1dbe fixed this for gropdf. I remember finding a case where the patch caused a problem with multiple input files. ___ Reply to this item at:

[bug #52983] [PATCH] troffrc: Define register 'F' to avoid warnings

Update of bug #52983 (project groff): Severity: 2 - Minor => 1 - Wish Item Group: Warning/Suspicious behaviour => New feature Status:None => Wont Fix Assigned

[bug #57218] [PATCH] Reproducible builds support is broken and embeds timezone

Follow-up Comment #3, bug #57218 (project groff): > I guess we could have a register \n[.utc] which is normally zero but is set to 1 if SOURCE_DATE_EPOCH is in the environment. After thinking about that for 60 more seconds, I retract it. It would mean having to insert a layer on top of all

[bug #57218] [PATCH] Reproducible builds support is broken and embeds timezone

Update of bug #57218 (project groff): Severity: 3 - Normal => 5 - Blocker Status:None => Need Info ___ Follow-up Comment #2: I nominate this as a

[bug #56694] [PATCH] troff mixes malloc / delete[]

Update of bug #56694 (project groff): Severity: 3 - Normal => 4 - Important Status:None => In Progress Assigned to:None => gbranden

[bug #55695] [PATCH] Troff outputs garbled file names on MS-Windows

Update of bug #55695 (project groff): Status:None => Need Info ___ Follow-up Comment #1: Do we have someone with access to a Windows machine to test this on? Eli filed it almost

[bug #55557] [PATCH] gropdf, gpinyin, gperl, glilypond, hyphenex can execute arbitrary commands

Update of bug #7 (project groff): Severity: 4 - Important => 6 - Security Summary: [PATCH] gropdf can execute arbitrary commands => [PATCH] gropdf,gpinyin,gperl,glilypond,hyphenex can execute arbitrary commands

[bug #55449] [PATCH] Use FILENAME_MAX in maxfilename.cpp

Update of bug #55449 (project groff): Status:None => Need Info ___ Follow-up Comment #2: Do we have someone with access to a Windows machine to test this on? Eli filed it almost

[bug #55335] [PATCH] preconv produces CR CR LF end-of-line on MS-Windows

Update of bug #55335 (project groff): Status:None => Need Info ___ Follow-up Comment #1: Do we have someone with access to a Windows machine to test this on? Eli filed it almost

[bug #55320] [PATCH] tmac/an-old.tmac: Add a warning about a missing .RS or an extra .RE

Update of bug #55320 (project groff): Severity: 3 - Normal => 1 - Wish Status:None => Confirmed Assigned to:None => gbranden

[bug #55299] [PATCH] "groff -v -e -s -t" produces garbled output on MS-Windows

Update of bug #55299 (project groff): Status:None => Need Info ___ Follow-up Comment #1: Do we have someone with access to a Windows machine to test this on? Eli filed it almost

[bug #55091] [PATCH] stop stripping comments and spaces from installed macro packages

Follow-up Comment #3, bug #55091 (project groff): I second "skipping the stripper" as an early item of business after 1.23 final. ___ Reply to this item at:

[bug #51303] [PATCH] Remove blanks at the end of lines

Update of bug #51303 (project groff): Status:None => Fixed Assigned to:None => gbranden Open/Closed:Open => Closed Planned Release:

[bug #51065] [PATCH] Remove repeated words in "contrib/..." and untangle some paragraphs

Update of bug #51065 (project groff): Status: In Progress => Fixed Open/Closed:Open => Closed Planned Release:None => 1.23

[bug #45034] [PATCH] mdoc(7): add support for the mdocmx(7) reference extension

Update of bug #45034 (project groff): Assigned to:None => schwarze ___ Reply to this item at: ___

[bug #45034] [PATCH] mdoc(7): add support for the mdocmx(7) reference extension

Update of bug #45034 (project groff): Category:None => Macro - mdoc Item Group:None => New feature ___ Reply to this item at:

[bug #44289] [PATCH] nroff script -E option

Update of bug #44289 (project groff): Status: In Progress => Fixed Assigned to:schwarze => gbranden Open/Closed:Open => Closed

[bug #44018] [PATCH] gtroff hangs in environment::possibly_break_line with -mja

Update of bug #44018 (project groff): Severity: 3 - Normal => 4 - Important Status:None => Fixed Assigned to:None => gbranden Open/Closed:

[bug #42978] [PATCH] tbl does not restore the tab settings

Update of bug #42978 (project groff): Item Group: New feature => Incorrect behaviour Status: Confirmed => Fixed Assigned to:None => gbranden Open/Closed:

[bug #42515] [PATCH] clean up macro name spaces regarding "need_eo_{h, tl}"

Update of bug #42515 (project groff): Category: Macro - man => Macro - others Assigned to:None => gbranden Summary: [PATCH] clean up an-old.tmac namespace => [PATCH] clean up macro name spaces