In our current implementation, loose lists and tight lists look the same visually. Loose lists are lists with blank lines between list items, and the contents of a list item should be enclosed in a paragraph tag in that case. For unordered lists, paragraph tags have a bottom margin in starlight and thus looses lists look much more spaced out than tight lists. That is not the behaviour we had in mind while writing the documentation, the reason we had all these loose lists is to make the documentation easy to write and read. So we attempt to remove all the blank lines and fix the problem at source. Since paragraph tags are used for other purposes in a list in starlight, it won't be a wise decision to let the source be as is and just change things in css, other expected behaviours might break in that case. See this topic for more details: https://chat.zulip.org/#narrow/channel/19-documentation/topic/new.20help.20center.3A.20regressions/near/2226084 All the changes were made by a one-off script which has not been commited to the repo. The script wasn't perfect and could not decide between blank lines that make a list loose vs blank lines necessary for a sub-list or a code block inside a list item. A manual review of all the changes was done before making this commit to ensure that no unintended changes were made to the help center files.
2.8 KiB
Mention a user or group
{!mentions-intro.md!}
!!! tip ""
If you edit a message, adding or removing mentions will update message
notifications. [Learn more](/help/edit-a-message#message-notifications).
Mention a user or group
From the compose box
{start_tabs}
{!start-composing.md!}
-
Type
@
followed by a few letters from a name or email address. -
Pick the appropriate user or user group from the autocomplete.
{end_tabs}
From the user list
{start_tabs}
{!right-sidebar-user-card.md!}
-
Select Copy mention syntax to add it to your clipboard.
-
Paste the user's mention syntax in the compose box.
{end_tabs}
Via a message
{start_tabs}
-
Click on a user's profile picture or name on a message they sent to open their user card.
-
Select Reply mentioning user to start a reply to the conversation with a mention inserted into the compose box.
{end_tabs}
Silently mention a user
A silent mention allows you to refer to a user without triggering a
notification. Silent mentions start with @_
instead of @
.
{start_tabs}
{!start-composing.md!}
-
Type
@_
followed by a few letters from a name or email address. -
Pick the appropriate user or user group from the autocomplete.
{end_tabs}
Mention all topic participants
Using the @**topic**
mention, you can mention everyone who has previously
participated in the topic by sending a message or
reacting with an emoji. This lets you notify just those
who have already engaged in the conversation.
Users can disable notifications for @**topic**
mentions by:
- Disabling notifications for wildcard mentions globally or for individual channels.
- Muting the topic or channel.
Mention everyone on a channel
You can mention everyone on a channel with the @**all**
mention (or,
equivalently, @**everyone**
or @**channel**
). It's best to use these mentions
only when your message requires timely attention from many channel subscribers.
An organization can be configured to
restrict wildcard mentions in large channels.
Users can disable notifications for @**all**
, @**everyone**
, and
@**channel**
mentions by:
- Disabling notifications for wildcard mentions globally or for individual channels.
- Muting the topic or channel.
Examples
{!mentions-examples.md!}