aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/TODO
Commit message (Collapse)AuthorAgeFilesLines
* The mandoc(1) manual already mentions that -T man output modeIngo Schwarze2021-07-041-1/+6
| | | | | | | | | | neither supports tbl(7) nor eqn(7) input. If an input file contains such code anyway, tell the user rather than failing an assert(3)ion. Fixing a crash reported by Bjarni Ingi Gislason <bjarniig at rhi dot hi dot is> in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901636 which the Debian maintainer of mandoc, Michael at Stapelberg dot ch, forwarded to me.
* new TODO entry: HTML formatting of .nfIngo Schwarze2021-06-271-1/+6
|
* three new TODO itemsIngo Schwarze2021-06-261-1/+20
|
* tbl(7) layout "n" specifier for HTML outputIngo Schwarze2021-06-021-1/+7
|
* \s with arbitrary arg delimitersIngo Schwarze2021-05-121-1/+5
|
* double .TH in man(7)Ingo Schwarze2021-03-281-1/+5
|
* more about .Bd -unfilledIngo Schwarze2021-03-281-2/+7
|
* MANWIDTHIngo Schwarze2020-11-131-1/+7
|
* old groff_char(7) reported by kamil at NetBSDIngo Schwarze2020-11-121-1/+5
|
* error message simplifications requested by deraadt@Ingo Schwarze2020-10-261-1/+5
|
* assertion found in jes@'es afl run: .TS .if n .ceIngo Schwarze2020-09-071-1/+16
|
* more info from John Gardner about ASCII control chars in roff(7) inputIngo Schwarze2020-09-011-1/+2
|
* more details about ASCII control charactersIngo Schwarze2020-06-241-1/+5
|
* John Gardner: handling of ASCII control characters during inputIngo Schwarze2020-06-221-1/+15
|
* While we do not recommend the idiom ".Fl Fl long" for long optionsIngo Schwarze2020-04-261-5/+4
| | | | | | | | | | | because it is an abuse of semantic macros for device-specific presentational effects, this idiom is so widespread that it makes sense to convert it to the recommended ".Fl \-long" during the validation phase. For example, this improves HTML formatting in pages where authors have used the dubious .Fl Fl. Feature suggested by Steffen Nurpmeso <steffen at sdaoden dot eu> on freebsd-hackers.
* two new entries: "Fl Fl" to "Fl \-" in validation and eqn/tbl in -T manIngo Schwarze2020-02-151-1/+9
|
* delete the entry for a crash that was already fixedIngo Schwarze2020-01-191-9/+1
|
* distinction between .Vt and .VaIngo Schwarze2019-12-251-1/+6
|
* two new entries: make .Sh/.Ss parsed in mdoc(7)Ingo Schwarze2019-12-221-1/+9
| | | | and delete release number verification from groff_mdoc(7)
* want to get rid of the last style= attributes, suggested by bentley@Ingo Schwarze2019-11-101-1/+6
|
* .ce .if .B crash reported by espie@, and one other bugIngo Schwarze2019-11-091-1/+14
|
* Do not access a NULL pointer if a table contains a horizontal lineIngo Schwarze2019-06-111-1/+4
| | | | | | next to a table line having fewer columns than the table as a whole. Bug found by Stephen Gregoratto <dev at sgregoratto dot me> with aerc-config(5).
* In fs_lookup(), use stat(2) rather than access(2) to check file existence.Ingo Schwarze2019-05-031-7/+1
| | | | | | | | | | | Some mildly broken real-world packages on some operating systems contain dangling symlinks in manual page directories: pestering the user to run makewhatis(8) makes no sense because that won't help. On the other hand, missing read permissions deserve ugly error messages and are unlikely to occur in practice anyway. Fixing an issue reported by Lorenzo Beretta <loreb at github> as part of https://github.com/void-linux/void-packages/issues/9868 .
* In man(1) mode with a specific section requested,Ingo Schwarze2019-05-031-13/+1
| | | | | | | | | | | | | | | | try harder to find the best match. Use this order of preference: 1. The section in both the directory name and the file name matches exactly. 2. The section in the file name matches exactly. 3. The section in the directory name matches exactly. 4. Neither of them matches exactly. The latter can happen when mansearch() finds substring matches or when the second .Dt argument mismatches the dir and file names. Lorenzo Beretta <loreb at github> reported that this caused real problems on Void Linux, like "man 3 readline" showing readline(3m). See https://github.com/void-linux/void-packages/issues/9868 for details.
* In man(1) mode, i.e. when asking for a single manual page by name,Ingo Schwarze2019-04-301-7/+1
| | | | | | | | | | | | prefer file name matches over .Dt/.TH matches over first NAME matches over later NAME matches, but do not change the ordering for apropos(1) nor for man -a. This reverts main.c rev. 1.310 and mansearch.h rev. 1.29 and includes a partial revert of mansearch.c rev. 1.79. Regression reported by Lorenzo Beretta <loreb at github> as part of https://github.com/void-linux/void-packages/issues/9868 .
* issues found by Jan Stary in groffer(1) version 1.19Ingo Schwarze2019-04-231-1/+22
|
* new man(1) issues from Lorenzo Beretta <loreb at github>Ingo Schwarze2019-04-011-1/+25
|
* When the -S option is given to man(1) and the requested manual pageIngo Schwarze2019-03-041-10/+1
| | | | | | | | | | | | name is not found and the requested architecture is unknown, complain about the architecture rather than about the manual page name: $ man -S vax cpu man: Unknown architecture "vax". $ man -S sparc64 foobar man: No entry for foobar in the manual. Friendlier error message suggested by jmc@, who also OK'ed the patch.
* Fix the last straggler where the struct roff_node "line" memberIngo Schwarze2019-03-041-5/+1
| | | | | was abused to detect an input line break; instead, use the NODE_LINE flag to improve robustness.
* additional comments on two TODO itemsIngo Schwarze2019-03-041-4/+12
|
* Represent multiple subsequent .IP blocks having a consistentIngo Schwarze2019-03-021-6/+1
| | | | | | | | | head argument of *, \-, or \(bu as <ul> rather than as <dl>, using a bit of heuristics. Basic idea suggested by Dagfinn Ilmari Mannsaker <ilmari at github> in https://github.com/Debian/debiman/issues/67 and independently by <Pali dot Rohar at gmail dot com> on <discuss at mandoc dot bsd dot lv>.
* Wrap .Sh/.SH sections and .Ss/.SS subsections in HTML <section> elementsIngo Schwarze2019-03-011-8/+1
| | | | | | as recommended for accessibility by the HTML 5 standard. Triggered by a similar, but slightly different suggestion from Laura Morales <lauretas at mail dot com>.
* Format multiple subsequent .IP or multiple subsequent .TP/.TQIngo Schwarze2019-02-281-6/+1
| | | | | as a single <dl> list rather than opening a new list for each item; feature suggested by Pali dot Rohar at gmail dot com.
* Delete several entries that were already fixed.Ingo Schwarze2019-01-171-29/+2
| | | | | The two entries about dashes, hyphens, and minus signs are no longer relevant because we decided on a policy that is now documented.
* Two functional improvements to filling in terminal output.Ingo Schwarze2019-01-041-8/+1
| | | | | | | | | | | 1. Fully support no-fill mode in mdoc(7), even when invoked with low-level roff(7) .nf requests. As a side effect, this substantially simplifies the implementation of .Bd -unfilled and .Bd -literal. 2. Let .Bd -centered fill its text, using the new TERMP_CENTER flag. That finally fixes the long-standing bug that it used to operate in no-fill mode, which was known to be wrong for at least five years. This also simplifies the implementation of .Bd -centered considerably.
* Several improvements to escape sequence handling.Ingo Schwarze2018-12-151-11/+1
| | | | | | | | | | | | | | | | | | | | | | | * Add the missing special character \_ (underscore). * Partial implementations of \a (leader character) and \E (uninterpreted escape character). * Parse and ignore \r (reverse line feed). * Add a WARNING message about undefined escape sequences. * Add an UNSUPP message about unsupported escape sequences. * Mark \! and \? (transparent throughput) and \O (suppress output) as unsupported. * Treat the various variants of zero-width spaces as one-byte escape sequences rather than as special characters, to avoid defining bogus forms with square brackets. * For special characters with one-byte names, do not define bogus forms with square brackets, except for \[-], which is valid. * In the form with square brackets, undefined special characters do not fall back to printing the name verbatim, not even for one-byte names. * Starting a special character name with a blank is an error. * Undefined escape sequences never abort formatting of the input string, not even in HTML output mode. * Document the newly handled escapes, and a few that were missing. * Regression tests for most of the above.
* Better handle automatic column width assignments in the presence ofIngo Schwarze2018-11-291-6/+1
| | | | | | | | | | | | | | horizontal spans, by implementing a moderately difficult iterative algoritm. The benefit is that spans containing long text no longer cause an excessive width of their starting column. The result is likely not optimal, in particular in the presence of many spans overlapping in complicated ways nor when spans interact with equalizing or maximizing colums. But i doubt the practical usefulness of making this more complicated. Issue originally reported in synaptics(4), which now looks better, by tedu@ three years ago, and reminded by Pali Rohar this summer.
* In -T utf8 output mode, render tbl(7) borders with the UnicodeIngo Schwarze2018-11-281-10/+1
| | | | | | | | | | | | | box drawing characters, U+2500 to U+257F. Originally suggested by bentley@ four years ago, reminded this summer by Pali Rohar. Binary and decimal arithmetics are boring, so let's use some ternary arithmetics for a change. That said, some other aspects are too complicated for my liking, so this could use some polishing in the future.
* Let cells containing nothing but \^ extend the cell above.Ingo Schwarze2018-11-251-5/+1
| | | | Missing feature reported by Pali dot Rohar at gmail dot com.
* In tbl(7) -T html output,Ingo Schwarze2018-11-251-5/+5
| | | | | | | | | | span cells horizontally and vertically as requested by the layout. Does not handle spans requested in the data section yet. To be able to do this, record the number of rows spanned in the first data cell (struct tbl_dat) of a vertical span. Missing feature reported by Pali dot Rohar at gmail dot com.
* HTML formatting of .IPIngo Schwarze2018-11-251-1/+7
|
* Implement horizontal and vertical alignment of tbl(7) cell contentIngo Schwarze2018-11-241-5/+1
| | | | | in -T html output. This does not handle spanned cells yet. Missing feature reported by Pali dot Rohar at gmail dot com.
* in -man -Thtml, vertical spacing is required before .IPIngo Schwarze2018-10-251-1/+7
|
* Add an option -T html -O toc to add a brief table of contents nearIngo Schwarze2018-10-021-6/+1
| | | | | the top of HTML pages containing at least two non-standard sections. Suggested by Adam Kalisz and discussed with kristaps@ during EuroBSDCon 2018.
* Support a second argument to -O man,Ingo Schwarze2018-10-021-7/+1
| | | | | | selecting the format according to local existence of the file. Suggested by kristaps@ during EuroBSDCon 2018. Written on the train Frankfurt-Karlsruhe returning from EuroBSDCon.
* Render the eqn(7) "sqrt" function as U+221A in UTF-8 output.Ingo Schwarze2018-10-021-5/+2
| | | | | | This also agrees with what groff does. Suggested by an attendee of EuroBSDCon 2018 in Bucuresti. Written on the plane Bucuresti-Frankfurt returning from EuroBSDCon.
* feature suggestions from EuroBSDCon 2018Ingo Schwarze2018-09-231-1/+15
|
* Rudimentary implementation of the roff(7) .while request.Ingo Schwarze2018-08-241-5/+1
| | | | | | | | | | | Needed for example by groff_hdtbl(7). There are two limitations: It does not support nested .while requests yet, and each .while loop must start and end in the same scope. The roff_parseln() return codes are now more flexible and allow OR'ing options.
* Implement the roff(7) .shift and .return requests,Ingo Schwarze2018-08-231-2/+2
| | | | | | | | | | | | | | for example used by groff_hdtbl(7) and groff_mom(7). Also correctly interpolate arguments during nested macro execution even after .shift and .return, implemented using a stack of argument arrays. Note that only read.c, but not roff.c can detect the end of a macro execution, and the existence of .shift implies that arguments cannot be interpolated up front, so unfortunately, this includes a partial revert of roff.c rev. 1.337, moving argument interpolation back into the function roff_res().
* Mostly complete implementation of the 'c' (character available)Ingo Schwarze2018-08-191-7/+1
| | | | | | | | | | | roff conditional, except that the .char request still isn't supported and that behaviour differs from groff in many edge cases. But at least valid character names and numbers are now distinguished from invalid ones. This also fixes the bug that parsing of the 'c' conditional was incomplete, which resulted in leaking the tested character to the input parser at the beginning of the body when the condition was inverted.
generated by cgit v1.2.3-56-ge451 (git 2.39.0) at 2024-06-16 14:22:05 +0000