sapling/eden/scm/edenscm/mercurial/templates/monoblue/search.tmpl

{header}
    <title>{repo|escape}: Search</title>
    <link rel="alternate" type="application/atom+xml" href="{url|urlescape}atom-log" title="Atom feed for {repo|escape}"/>
    <link rel="alternate" type="application/rss+xml" href="{url|urlescape}rss-log" title="RSS feed for {repo|escape}"/>
</head>

<body>
<div id="container">
    <div class="page-header">
        <h1 class="breadcrumb"><a href="/">Mercurial</a> {pathdef%breadcrumb} / search</h1>

        {searchform}

        <ul class="page-nav">
            <li><a href="{url|urlescape}summary{sessionvars%urlparameter}">summary</a></li>
            <li><a href="{url|urlescape}shortlog{sessionvars%urlparameter}">shortlog</a></li>
            <li><a href="{url|urlescape}log{sessionvars%urlparameter}">changelog</a></li>
            <li><a href="{url|urlescape}graph{sessionvars%urlparameter}">graph</a></li>
            <li><a href="{url|urlescape}tags{sessionvars%urlparameter}">tags</a></li>
            <li><a href="{url|urlescape}bookmarks{sessionvars%urlparameter}">bookmarks</a></li>
            <li><a href="{url|urlescape}branches{sessionvars%urlparameter}">branches</a></li>
            <li><a href="{url|urlescape}file{sessionvars%urlparameter}">files</a></li>
            {archives%archiveentry}
            <li><a href="{url|urlescape}help{sessionvars%urlparameter}">help</a></li>
        </ul>
    </div>

    <h2 class="no-link no-border">searching for {query|escape}</h2>
    {entries}

{footer}
monoblue: use newer template syntax everywhere 2009-05-15 12:47:05 +04:00			`{header}`
			`<title>{repo\|escape}: Search</title>`
hgweb: urlescape all urls, HTML escape repo/tag/branch/... names Without this, repository paths or names containing e.g. & characters or html tags yielded strange results, possibly allowing cross-site scripting attacks. 2013-02-01 23:43:35 +04:00			`<link rel="alternate" type="application/atom+xml" href="{url\|urlescape}atom-log" title="Atom feed for {repo\|escape}"/>`
			`<link rel="alternate" type="application/rss+xml" href="{url\|urlescape}rss-log" title="RSS feed for {repo\|escape}"/>`
added monoblue hgweb theme 2008-10-08 21:52:22 +04:00			`</head>`

			`<body>`
			`<div id="container">`
			`<div class="page-header">`
hgweb: add a "URL breadcrumb" to the index and repository pages The purpose of this change is to make it much easier to navigate up the repository tree when the hg web server is used to serve more than one repository. A "URL breadcrumb" is a path where each of the path items can be clicked to go to the corresponding path page. This lets you go up the folder hierarchy very quickly. For example, when showing the list of repositories in http://myserver/myteams/myprojects, the following "breadcrumb" will be shown: Mercurial > myteams > myprojects Clicking on "myprojects" reloads the page. Clicking on "myteams" goes up one folder. Clicking on the leftmost "Mercurial" goes to the server root. This "breadcrumb" also appears on all repository pages. For example on the summary page of the repository at http://myserver/myteams/myprojects/myrepo the following will be shown: Mercurial > myteams > myprojects > myrepo / summary This change has been applied to all templates that already had a link to the main repository page (i.e. gitweb, monoblue, paper and coal) plus to the index page of the spartan template. In order to make the breadcumb links stand out the some of the template styles have been customized. 2012-11-28 23:21:26 +04:00			`<h1 class="breadcrumb"><a href="/">Mercurial</a> {pathdef%breadcrumb} / search</h1>`
added monoblue hgweb theme 2008-10-08 21:52:22 +04:00
hgweb: consolidate search form for monoblue Same deal as for paper. 2017-06-09 23:41:10 +03:00			`{searchform}`
added monoblue hgweb theme 2008-10-08 21:52:22 +04:00
			`<ul class="page-nav">`
hgweb: urlescape all urls, HTML escape repo/tag/branch/... names Without this, repository paths or names containing e.g. & characters or html tags yielded strange results, possibly allowing cross-site scripting attacks. 2013-02-01 23:43:35 +04:00			`<li><a href="{url\|urlescape}summary{sessionvars%urlparameter}">summary</a></li>`
			`<li><a href="{url\|urlescape}shortlog{sessionvars%urlparameter}">shortlog</a></li>`
			`<li><a href="{url\|urlescape}log{sessionvars%urlparameter}">changelog</a></li>`
hgweb: don't point graph links at tip hash where it doesn't make sense Some pages, e.g. bookmarks, help and summary don't have a meaningful revision context: they always either show information about tip or about the whole repo (and not about any specific changeset). And error pages can just show hgweb error messages, not related to any repo or changeset. When monoblue style was added in f9c487618909, however, all graph links had tried to point at some hash, and on such pages as described above it didn't make sense. On error pages '{node\|short}' is empty string anyway. Of course, it worked, but seeing such pages without revision context provide links with hashes is a bit confusing (unless you keep current tip hash in your head at all times) and wasn't consistent with other template styles, other pages in monoblue and even other links on the same page. Let's just link to '/graph', which is equal to '/graph/tip'. 2015-06-12 11:09:59 +03:00			`<li><a href="{url\|urlescape}graph{sessionvars%urlparameter}">graph</a></li>`
hgweb: urlescape all urls, HTML escape repo/tag/branch/... names Without this, repository paths or names containing e.g. & characters or html tags yielded strange results, possibly allowing cross-site scripting attacks. 2013-02-01 23:43:35 +04:00			`<li><a href="{url\|urlescape}tags{sessionvars%urlparameter}">tags</a></li>`
			`<li><a href="{url\|urlescape}bookmarks{sessionvars%urlparameter}">bookmarks</a></li>`
			`<li><a href="{url\|urlescape}branches{sessionvars%urlparameter}">branches</a></li>`
hgweb: don't point file links at tip hash where it doesn't make sense Some pages, e.g. bookmarks, help and summary don't have a meaningful revision context: they always either show information about tip or about the whole repo (and not about any specific changeset). And error pages can just show hgweb error messages, not related to any repo or changeset. Having a hash in the links worked (even when '{node\|short}' resolved to an empty string on error pages), but seeing pages without revision context provide links with hashes is a bit confusing (unless you keep current tip hash in your head at all times) and not consistent with other template styles and other links on the same page: they don't have a hash. Let's just link to '/file', which is equal to '/file/tip'. 2015-06-12 13:34:10 +03:00			`<li><a href="{url\|urlescape}file{sessionvars%urlparameter}">files</a></li>`
hgweb: move archive entries outside of <li> in monoblue style archiveentry already includes surrounding <li></li>, so putting archive entries inside <li> element produced incorrect markup. 2015-01-09 17:53:38 +03:00			`{archives%archiveentry}`
hgweb: urlescape all urls, HTML escape repo/tag/branch/... names Without this, repository paths or names containing e.g. & characters or html tags yielded strange results, possibly allowing cross-site scripting attacks. 2013-02-01 23:43:35 +04:00			`<li><a href="{url\|urlescape}help{sessionvars%urlparameter}">help</a></li>`
added monoblue hgweb theme 2008-10-08 21:52:22 +04:00			`</ul>`
			`</div>`

monoblue: use newer template syntax everywhere 2009-05-15 12:47:05 +04:00			`<h2 class="no-link no-border">searching for {query\|escape}</h2>`
			`{entries}`
added monoblue hgweb theme 2008-10-08 21:52:22 +04:00
monoblue: use newer template syntax everywhere 2009-05-15 12:47:05 +04:00			`{footer}`