| Ticket UUID: | a127bf6415cbfa420ed96dcb9144ab4263f1e6b | ||
| Title: | auto_path is documented in two manpages | ||
| Type: | Bug | Created on: | 2026-06-04 08:28:54 |
| Submitter: | apnadkarni | Assigned to: | nobody |
| Subsystem: | 38. Init - Library - Autoload | Severity: | Minor |
| Priority: | 5 Medium | Last modified: | 2026-06-16 16:38:36 |
| Status: | Pending | Closed by: | nobody |
| Resolution: | Fixed | Closed on: | |
| Version: | |||
| Description: | ||||
|
The auto_path variable is documented in both library.n and tclvars.n with slightly different (not conflicting) information in each. Should be merged. Leaving it to Torsten to decide on the best location :-) | ||||
| User Comments: | ||||
tberg added on 2026-06-16 13:33:32:
This cannot be resolved unambiguously as both manual pages mix things. It is not only Judging from the NAME of the manual pages, these are the topics:
So, in an ideal situation, the library page should only document what comes from the Tcl library whereas the tclvars page should take the rest, i.e. what comes from Tcl directly (disregarding the Tcl library). However, these two cannot be separated. So, what is the most natural place? Let's keep it in tclvars.n as it is not solely the Tcl library but also the core that has a role here. Also, tclvars.n is the manual page where I have now kept the documentation in tclvars_n and removed the slightly shorter one from library.n. Where What should we do about the others ( apnadkarni added on 2026-06-16 16:38:36:
Good catch, did not realize In the case of For similar reasons, For me, the location of the description is not as important as avoiding duplication so I'm ok with whichever page you think is appropriate. | ||||
