Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/templates/zerver/search_operators.html

96 lines
4.3 KiB
HTML
Raw Normal View History

Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
<div class="modal hide" id="search-operators" tabindex="-1" role="dialog"
aria-labelledby="search-operators-label" aria-hidden="true">
<div class="modal-header">
<button type="button" class="close" data-dismiss="modal" aria-hidden="true">×</button>
docs: Replace "search help" with "search operators". For better clarification and to avoid confusion with user documentation tab.
2017-02-01 02:44:19 +01:00
<h3 id="search-operators-label">{{ _('Search operators') }}</h3>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</div>
<div class="modal-body">
Fix duplicate HTML id: fmt_help_table. We replace the id with a class called help-table.
2017-01-11 22:51:51 +01:00
<table class="table table-striped table-condensed table-rounded table-bordered help-table">
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
<thead>
<tr>
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<th>{{ _('Operator') }}</th>
<th>{{ _('Effect') }}</th>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</tr>
</thead>
<tr>
<td class="operator">stream:<span class="operator_value">stream</span></td>
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<td class="definition">{{ _('Narrow to messages on stream') }} <span class="operator_value">stream</span></td>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</tr>
<tr>
<td class="operator">topic:<span class="operator_value">topic</span></td>
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<td class="definition">{{ _('Narrow to messages with topic') }} <span class="operator_value">topic</span></td>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</tr>
<tr>
<td class="operator">pm-with:<span class="operator_value">email</span></td>
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<td class="definition">{{ _('Narrow to private messages with') }} <span class="operator_value">email</span></td>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</tr>
Put sender: adjacent to pm-with in search help. (imported from commit 580079ba941252df8e19165f613a30ee9597e4c1)
2013-12-05 17:47:28 +01:00
<tr>
<td class="operator">sender:<span class="operator_value">email</span></td>
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<td class="definition">{{ _('Narrow to messages sent by') }} <span class="operator_value">email</span></td>
Put sender: adjacent to pm-with in search help. (imported from commit 580079ba941252df8e19165f613a30ee9597e4c1)
2013-12-05 17:47:28 +01:00
</tr>
Document sender:me syntax. (imported from commit 7c32ddc70528f110ba7d2f64637da0cc8eb0a0a6)
2013-12-05 18:10:43 +01:00
<tr>
<td class="operator">sender:me</td>
Period should be part of the translation.
2016-10-13 14:31:53 +02:00
<td class="definition">{{ _('Narrow to messages sent by you.') }}</td>
Document sender:me syntax. (imported from commit 7c32ddc70528f110ba7d2f64637da0cc8eb0a0a6)
2013-12-05 18:10:43 +01:00
</tr>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
<tr>
<td class="operator">near:<span class="operator_value">id</span></td>
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<td class="definition">{{ _('Center the view around message ID') }} <span class="operator_value">id</span></td>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</tr>
<tr>
<td class="operator">id:<span class="operator_value">id</span></td>
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<td class="definition">{{ _('Narrow to just message ID') }} <span class="operator_value">id</span></td>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</tr>
<tr>
Add is:alerted to search help. (imported from commit 0c545fb35af0040047fcf53c560941feee2da9ad)
2014-02-19 18:11:32 +01:00
<tr>
<td class="operator">is:alerted</td>
Period should be part of the translation.
2016-10-13 14:31:53 +02:00
<td class="definition">{{ _('Narrow to messages with alert words.') }}</td>
Add is:alerted to search help. (imported from commit 0c545fb35af0040047fcf53c560941feee2da9ad)
2014-02-19 18:11:32 +01:00
</tr>
Make search help more explicit for is:{mentioned,private,starred}. (imported from commit 736228d483372a571e5e07b0764da521febcc970)
2013-12-05 17:51:31 +01:00
<td class="operator">is:mentioned</td>
Period should be part of the translation.
2016-10-13 14:31:53 +02:00
<td class="definition">{{ _('Narrow to messages that mention you.') }}</td>
Make search help more explicit for is:{mentioned,private,starred}. (imported from commit 736228d483372a571e5e07b0764da521febcc970)
2013-12-05 17:51:31 +01:00
</tr>
<tr>
<td class="operator">is:private</td>
Period should be part of the translation.
2016-10-13 14:31:53 +02:00
<td class="definition">{{ _('Narrow to private messages.') }}</td>
Make search help more explicit for is:{mentioned,private,starred}. (imported from commit 736228d483372a571e5e07b0764da521febcc970)
2013-12-05 17:51:31 +01:00
</tr>
<tr>
<td class="operator">is:starred</td>
Period should be part of the translation.
2016-10-13 14:31:53 +02:00
<td class="definition">{{ _('Narrow to starred messages.') }}</td>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</tr>
search_operators: Document has: operators. These useful operators for finding messages with images/links/etc. have been available for a long time, but weren't documented.
2016-09-28 05:22:17 +02:00
<tr>
<td class="operator">has:link</td>
Period should be part of the translation.
2016-10-13 14:31:53 +02:00
<td class="definition">{{ _('Narrow to messages containing links.') }}</td>
search_operators: Document has: operators. These useful operators for finding messages with images/links/etc. have been available for a long time, but weren't documented.
2016-09-28 05:22:17 +02:00
</tr>
<tr>
<td class="operator">has:image</td>
Period should be part of the translation.
2016-10-13 14:31:53 +02:00
<td class="definition">{{ _('Narrow to messages containing images.') }}</td>
search_operators: Document has: operators. These useful operators for finding messages with images/links/etc. have been available for a long time, but weren't documented.
2016-09-28 05:22:17 +02:00
</tr>
<tr>
<td class="operator">has:attachment</td>
Period should be part of the translation.
2016-10-13 14:31:53 +02:00
<td class="definition">{{ _('Narrow to messages containing uploads.') }}</td>
search_operators: Document has: operators. These useful operators for finding messages with images/links/etc. have been available for a long time, but weren't documented.
2016-09-28 05:22:17 +02:00
</tr>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
<tr>
<td class="operator"><span class="operator_value">keyword</span></td>
Use block translation tag where appropriate.
2016-10-13 13:16:07 +02:00
<td class="definition">{% trans %}Search for <span class="operator_value"> keyword </span> in the topic or message content {% endtrans %}</td>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</tr>
Document negated topic searches. We don't have room in the dialog to show every variation of the negated search syntax. If we start by documenting negated topic searches, we may get some discovery on the negated search features without cluttering out the way more common search options. (imported from commit 3b2c2672d125788dc71a5eeb2b6f1e551380c62e)
2014-03-04 23:43:29 +01:00
<tr>
<td class="operator">-topic:<span class="operator_value">topic</span></td>
Use block translation tag where appropriate.
2016-10-13 13:16:07 +02:00
<td class="definition">{% trans %}Exclude messages with topic <span class="operator_value">topic</span>{% endtrans %}</td>
Document negated topic searches. We don't have room in the dialog to show every variation of the negated search syntax. If we start by documenting negated topic searches, we may get some discovery on the negated search features without cluttering out the way more common search options. (imported from commit 3b2c2672d125788dc71a5eeb2b6f1e551380c62e)
2014-03-04 23:43:29 +01:00
</tr>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</table>
Use block translation tag where appropriate.
2016-10-13 13:16:07 +02:00
{% trans %}
<p>You can use any combination of these search operators in a single query. For example:</p>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
<p>&nbsp; <span class="operator">stream:<span class="operator_value">streamname</span>
sender:<span class="operator_value">user@example.com</span>
<span class="operator_value">keyword</span></span></p>
Use block translation tag where appropriate.
2016-10-13 13:16:07 +02:00
<p>would search for messages sent by <span class="operator_value">user@example.com</span> to stream
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
<span class="operator_value">streamname</span>
Use block translation tag where appropriate.
2016-10-13 13:16:07 +02:00
containing the keyword <span class="operator_value">keyword</span>.</p>
{% endtrans %}
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</div>
<div class="modal-footer">
Convert Zulip to use Jinja2 templates. This results in a substantial performance improvement for all of Zulip's backend templates. Changes in templates: - Change `block.super` to `super()`. - Remove `load` tag because Jinja2 doesn't support it. - Use `minified_js()|safe` instead of `{% minified_js %}`. - Use `compressed_css()|safe` instead of `{% compressed_css %}`. - `forloop.first` -> `loop.first`. - Use `{{ csrf_input }}` instead of `{% csrf_token %}`. - Use `{# ... #}` instead of `{% comment %}`. - Use `url()` instead of `{% url %}`. - Use `_()` instead of `{% trans %}` because in Jinja `trans` is a block tag. - Use `{% trans %}` instead of `{% blocktrans %}`. - Use `{% raw %}` instead of `{% verbatim %}`. Changes in tools: - Check for `trans` block in `check-templates` instead of `blocktrans` Changes in backend: - Create custom `render_to_response` function which takes `request` objects instead of `RequestContext` object. There are two reasons to do this: 1. `RequestContext` is not compatible with Jinja2 2. `RequestContext` in `render_to_response` is deprecated. - Add Jinja2 related support files in zproject/jinja2 directory. It includes a custom backend and a template renderer, compressors for js and css and Jinja2 environment handler. - Enable `slugify` and `pluralize` filters in Jinja2 environment. Fixes #620.
2016-04-21 08:48:33 +02:00
<button class="btn btn-primary" data-dismiss="modal" aria-hidden="true">{{ _('Close') }}</button>
Add documentation on search operators. (imported from commit 9ed5692685b52d6e4d4f1a59c1b4cc0fde252ff2)
2013-12-02 22:51:03 +01:00
</div>
</div>