Template talk:See also
This is a Talk page - please see the documentation about using talk pages. Add newer comments below older ones, sign comments using four tildes (
~~~~), and indent successive comments with colons (:).
Add new sections at the bottom of the page, under a heading (== ==). Please remember to mark sections as "open for discussion" using {{talk|open}}, so they will show up in the list of open discussions.emdash vs endash
Shouldn't this template use emdash (—) instead of an endash (–)? Sounds better in my opinion, from a grammatical point of view. Brenton (contribs · email · talk) 05:50, 19 May 2017 (UTC)
- It probably should use the emdash. That being said, places on the wiki that are not using this See also template are probably using a hypen, which would probably look odd side-by-side with the See also template. My vote would be for converting when the majority of the articles get upgraded to using the See also. This would be so that the articles stay visually consistent. :) --Maffblaster (talk) 05:09, 5 June 2017 (UTC)
Articles starting with :/
Sorry, couldn't find out how to use it for /etc/portage/patches, result looks like /etc/portage/patches — provide a way to apply patches to package source code when sources are extracted before installation.
--Charles17 (talk) 15:22, 31 July 2017 (UTC)
- Use {{See also|/etc/portage/patches}}. If i find a way to keep the same syntax for it (with colon), i will be mentioning it here later.
- --Cronolio (talk) 17:24, 31 July 2017 (UTC)
Multiple article descriptions
Multiple article descriptions are displayed when using the See also template with certain pages. For example /etc/portage/make.conf:
/etc/portage/make.conf — the main configuration file used to customize the Portage environment on a global level., the location Portage keeps binary packages.
This happens because /etc/portage/make.conf transcludes DISTDIR which has its own article description property. Is this intended behavior?--BT (talk) 09:17, 10 June 2019 (UTC)
- BT , no, it was not my intention when creating the template for it to display more than one description. My time is limited, so I'll post this discussion in our IRC channel to see if anyone has time to look into a fix. Perhaps it can be something for Brian Evans (Grknight) or Cronolio . --Maffblaster (talk) 16:19, 10 June 2019 (UTC)
- Yes, it was transcluded from DISTDIR. See diff for example how to manage it. Also usefull special page. --Cronolio (talk) 17:41, 10 June 2019 (UTC)
Links that include relative paths break description
Links that include relative paths (the / character) appear to break the See also template. For example:
Code:
* {{See also|Filesystem/Security|text=Filesystem security}}
Is rendered like:
- Filesystem security — one of the basic means to harden a system.
This should be fixed if possible. --Maffblaster (talk) 18:52, 3 July 2020 (UTC)
- This appears to have been fixed at some point. --Maffblaster (talk) 22:32, 22 August 2022 (UTC)
TODO: Support for a #section link
In the See also section of the Terminal emulator article, someone wanted the See also template to understand a #section link. This isn't a bad idea... opening this discussion in the event someone would like to add this support. --Maffblaster (talk) 08:28, 12 July 2023 (UTC)