[llvm-branch-commits] [clang-tools-extra-branch] r354997 - Merging r354777, r354778, r354779, r354786, r354865, and r354992

Hans Wennborg via llvm-branch-commits llvm-branch-commits at lists.llvm.org
Wed Feb 27 08:18:46 PST 2019


Author: hans
Date: Wed Feb 27 08:18:46 2019
New Revision: 354997

URL: http://llvm.org/viewvc/llvm-project?rev=354997&view=rev
Log:
Merging r354777, r354778, r354779, r354786, r354865, and r354992

------------------------------------------------------------------------
r354777 | gribozavr | 2019-02-25 13:48:52 +0100 (Mon, 25 Feb 2019) | 9 lines

Removed an unhelpful comment in index.rst

Reviewers: ilya-biryukov

Subscribers: arphaman, jdoerfert, cfe-commits

Tags: #clang

Differential Revision: https://reviews.llvm.org/D58602
------------------------------------------------------------------------

------------------------------------------------------------------------
r354778 | gribozavr | 2019-02-25 13:49:27 +0100 (Mon, 25 Feb 2019) | 7 lines

Fixed grammar in index.rst

Subscribers: arphaman, cfe-commits

Tags: #clang

Differential Revision: https://reviews.llvm.org/D58601
------------------------------------------------------------------------

------------------------------------------------------------------------
r354779 | gribozavr | 2019-02-25 14:03:44 +0100 (Mon, 25 Feb 2019) | 9 lines

Updated the documentation build instructions for the current CMake build system

Reviewers: ilya-biryukov

Subscribers: cfe-commits

Tags: #clang

Differential Revision: https://reviews.llvm.org/D58603
------------------------------------------------------------------------

------------------------------------------------------------------------
r354786 | gribozavr | 2019-02-25 14:43:48 +0100 (Mon, 25 Feb 2019) | 9 lines

Moved clangd docs to a separate directory in preparation to restructure them into multiple files

Reviewers: ilya-biryukov

Subscribers: ioeric, MaskRay, jkorous, arphaman, kadircet, jdoerfert, cfe-commits

Tags: #clang

Differential Revision: https://reviews.llvm.org/D58607
------------------------------------------------------------------------

------------------------------------------------------------------------
r354865 | kadircet | 2019-02-26 12:08:04 +0100 (Tue, 26 Feb 2019) | 11 lines

[clangd] Update docs to mention YCM integration and new LSP features

Reviewers: gribozavr

Reviewed By: gribozavr

Subscribers: ilya-biryukov, ioeric, MaskRay, jkorous, arphaman, cfe-commits

Tags: #clang

Differential Revision: https://reviews.llvm.org/D56718
------------------------------------------------------------------------

------------------------------------------------------------------------
r354992 | gribozavr | 2019-02-27 16:53:05 +0100 (Wed, 27 Feb 2019) | 13 lines

Added more detailed documentation for clangd

Summary:
The text was written mostly by Sam McCall, screenshots are mostly made
by me.

Reviewers: ilya-biryukov

Subscribers: ioeric, MaskRay, jkorous, arphaman, kadircet, jdoerfert, cfe-commits

Tags: #clang

Differential Revision: https://reviews.llvm.org/D58710
------------------------------------------------------------------------

Added:
    clang-tools-extra/branches/release_80/docs/_static/
      - copied from r354992, clang-tools-extra/trunk/docs/_static/
    clang-tools-extra/branches/release_80/docs/_templates/
      - copied from r354992, clang-tools-extra/trunk/docs/_templates/
    clang-tools-extra/branches/release_80/docs/clangd/
      - copied from r354786, clang-tools-extra/trunk/docs/clangd/
    clang-tools-extra/branches/release_80/docs/clangd/ApplyClangTidyFixInVSCode.gif
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/ApplyClangTidyFixInVSCode.gif
    clang-tools-extra/branches/release_80/docs/clangd/ApplyFixInVSCode.gif
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/ApplyFixInVSCode.gif
    clang-tools-extra/branches/release_80/docs/clangd/CodeCompletionInEmacsCompanyMode.png
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/CodeCompletionInEmacsCompanyMode.png
    clang-tools-extra/branches/release_80/docs/clangd/CodeCompletionInSublimeText.png
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/CodeCompletionInSublimeText.png
    clang-tools-extra/branches/release_80/docs/clangd/CodeCompletionInVSCode.png
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/CodeCompletionInVSCode.png
    clang-tools-extra/branches/release_80/docs/clangd/CodeCompletionInYCM.png
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/CodeCompletionInYCM.png
    clang-tools-extra/branches/release_80/docs/clangd/CodeCompletionInsertsNamespaceQualifiersInVSCode.gif
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/CodeCompletionInsertsNamespaceQualifiersInVSCode.gif
    clang-tools-extra/branches/release_80/docs/clangd/DeveloperDocumentation.rst
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/DeveloperDocumentation.rst
    clang-tools-extra/branches/release_80/docs/clangd/DiagnosticsInEmacsEglot.png
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/DiagnosticsInEmacsEglot.png
    clang-tools-extra/branches/release_80/docs/clangd/ErrorsInVSCode.png
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/ErrorsInVSCode.png
    clang-tools-extra/branches/release_80/docs/clangd/Extensions.rst
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/Extensions.rst
    clang-tools-extra/branches/release_80/docs/clangd/Features.rst
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/Features.rst
    clang-tools-extra/branches/release_80/docs/clangd/FindAllReferencesInVSCode.gif
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/FindAllReferencesInVSCode.gif
    clang-tools-extra/branches/release_80/docs/clangd/FormatSelectionInVSCode.gif
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/FormatSelectionInVSCode.gif
    clang-tools-extra/branches/release_80/docs/clangd/GoToDefinitionInVSCode.gif
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/GoToDefinitionInVSCode.gif
    clang-tools-extra/branches/release_80/docs/clangd/Installation.rst
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/Installation.rst
    clang-tools-extra/branches/release_80/docs/clangd/NavigationWithBreadcrumbsInVSCode.gif
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/NavigationWithBreadcrumbsInVSCode.gif
    clang-tools-extra/branches/release_80/docs/clangd/OutlineInVSCode.png
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/OutlineInVSCode.png
    clang-tools-extra/branches/release_80/docs/clangd/SignatureHelpInVSCode.gif
      - copied unchanged from r354992, clang-tools-extra/trunk/docs/clangd/SignatureHelpInVSCode.gif
Modified:
    clang-tools-extra/branches/release_80/   (props changed)
    clang-tools-extra/branches/release_80/docs/README.txt
    clang-tools-extra/branches/release_80/docs/clangd.rst
    clang-tools-extra/branches/release_80/docs/clangd/index.rst
    clang-tools-extra/branches/release_80/docs/conf.py
    clang-tools-extra/branches/release_80/docs/index.rst

Propchange: clang-tools-extra/branches/release_80/
------------------------------------------------------------------------------
--- svn:mergeinfo (original)
+++ svn:mergeinfo Wed Feb 27 08:18:46 2019
@@ -1 +1 @@
-/clang-tools-extra/trunk:351463,351466-351468,351531,351686,351738,351788,352040,352231,353327,353422,354505,354765,354957
+/clang-tools-extra/trunk:351463,351466-351468,351531,351686,351738,351788,352040,352231,353327,353422,354505,354765,354777-354779,354786,354865,354957,354992

Modified: clang-tools-extra/branches/release_80/docs/README.txt
URL: http://llvm.org/viewvc/llvm-project/clang-tools-extra/branches/release_80/docs/README.txt?rev=354997&r1=354996&r2=354997&view=diff
==============================================================================
--- clang-tools-extra/branches/release_80/docs/README.txt (original)
+++ clang-tools-extra/branches/release_80/docs/README.txt Wed Feb 27 08:18:46 2019
@@ -1,11 +1,10 @@
--------------------------------------------------------------
-Documentation for the tools of clang-tools-extra repo project
--------------------------------------------------------------
+----------------------------------
+Documentation in clang-tools-extra
+----------------------------------
 
-Sphinx and doxygen documentation is generated by executing make.
+To generate documentation in HTML format from files in clang-tools-extra/docs,
+build the docs-clang-tools-html target.
 
-Sphinx html files can be generated separately using make html.
+To generate documentation from the source code using Doxygen, build the
+doxygen-clang-tools target.
 
-Doxygen html files can also be generated using make doxygen.
-
-The generated documentation will be placed in _build/html.

Modified: clang-tools-extra/branches/release_80/docs/clangd.rst
URL: http://llvm.org/viewvc/llvm-project/clang-tools-extra/branches/release_80/docs/clangd.rst?rev=354997&r1=354996&r2=354997&view=diff
==============================================================================
--- clang-tools-extra/branches/release_80/docs/clangd.rst (original)
+++ clang-tools-extra/branches/release_80/docs/clangd.rst Wed Feb 27 08:18:46 2019
@@ -1,161 +1 @@
-============
-Clangd
-============
-
-.. contents::
-
-.. toctree::
-   :maxdepth: 1
-
-:program:`Clangd` is an implementation of the `Language Server Protocol
-<https://github.com/Microsoft/language-server-protocol>`_ leveraging Clang.
-Clangd's goal is to provide language "smartness" features like code completion,
-find references, etc. for clients such as C/C++ Editors.
-
-Using Clangd
-==================
-
-:program:`Clangd` is not meant to be used by C/C++ developers directly but
-rather from a client implementing the protocol. A client would be typically
-implemented in an IDE or an editor.
-
-At the moment, `Visual Studio Code <https://code.visualstudio.com/>`_ is mainly
-used in order to test :program:`Clangd` but more clients are likely to make
-use of :program:`Clangd` in the future as it matures and becomes a production
-quality tool. If you are interested in trying :program:`Clangd` in combination
-with Visual Studio Code, you can start by `installing Clangd`_ or
-`building Clangd`_, then open Visual Studio Code in the clangd-vscode folder and
-launch the extension.
-
-Installing Clangd
-==================
-
-Packages are available for debian-based distributions, see the `LLVM packages
-page <http://apt.llvm.org/>`_. :program:`Clangd` is included in the
-`clang-tools` package.
-However, it is a good idea to check your distribution's packaging system first
-as it might already be available.
-
-Otherwise, you can install :program:`Clangd` by `building Clangd`_ first.
-
-Building Clangd
-==================
-
-You can follow the instructions for `building Clang
-<https://clang.llvm.org/get_started.html>`_ but "extra Clang tools" is **not**
-optional.
-
-Current Status
-==================
-
-Many features could be implemented in :program:`Clangd`.
-Here is a list of features that could be useful with the status of whether or
-not they are already implemented in :program:`Clangd` and specified in the
-Language Server Protocol. Note that for some of the features, it is not clear
-whether or not they should be part of the Language Server Protocol, so those
-features might be eventually developed outside :program:`Clangd` or as an
-extension to the protocol.
-
-+-------------------------------------+------------+----------+
-| C/C++ Editor feature                |  LSP       |  Clangd  |
-+=====================================+============+==========+
-| Formatting                          | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Completion                          | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Diagnostics                         | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Fix-its                             | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Go to Definition                    | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Signature Help                      | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Document Highlights                 | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Rename                              | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Source hover                        | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Find References                     | Yes        |   No     |
-+-------------------------------------+------------+----------+
-| Code Lens                           | Yes        |   No     |
-+-------------------------------------+------------+----------+
-| Document Symbols                    | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Workspace Symbols                   | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Syntax and Semantic Coloring        | No         |   No     |
-+-------------------------------------+------------+----------+
-| Code folding                        | No         |   No     |
-+-------------------------------------+------------+----------+
-| Call hierarchy                      | No         |   No     |
-+-------------------------------------+------------+----------+
-| Type hierarchy                      | No         |   No     |
-+-------------------------------------+------------+----------+
-| Organize Includes                   | No         |   No     |
-+-------------------------------------+------------+----------+
-| Quick Assist                        | No         |   No     |
-+-------------------------------------+------------+----------+
-| Extract Local Variable              | No         |   No     |
-+-------------------------------------+------------+----------+
-| Extract Function/Method             | No         |   No     |
-+-------------------------------------+------------+----------+
-| Hide Method                         | No         |   No     |
-+-------------------------------------+------------+----------+
-| Implement Method                    | No         |   No     |
-+-------------------------------------+------------+----------+
-| Gen. Getters/Setters                | No         |   No     |
-+-------------------------------------+------------+----------+
-
-Editor Integration
-==================
-
-Any full-featured Language Server Protocol Client implementation should work
-with :program:`Clangd`. This `list
-<https://langserver.org/#implementations-client>`_ contains information about
-extensions and plugins that are known to work for different editors.
-
-Vim Integration
----------------
-
-LanguageClient-neovim
-~~~~~~~~~~~~~~~~~~~~~
-
-One of the options of using :program:`Clangd` in :program:`vim` (or
-:program:`nvim`) is to utilize `LanguageClient-neovim
-<https://github.com/autozimu/LanguageClient-neovim>`_ plugin. Please see the
-`Clangd Wiki page
-<https://github.com/autozimu/LanguageClient-neovim/wiki/Clangd>`_ for
-instructions.
-
-VSCode Integration
-------------------
-
-:program:`VSCode` provides `vscode-clangd
-<https://marketplace.visualstudio.com/items?itemName=llvm-vs-code-extensions.vscode-clangd>`_
-which is published in Visual Studio Marketplace and can be installed direcetly
-from :program:`VSCode`.
-
-Emacs Integration
------------------
-
-:program:`Emacs` provides `lsp-mode <github.com/emacs-lsp/lsp-mode>`_ and
-`Eglot <https://github.com/joaotavora/eglot>`_ plugins for LSP integration.
-
-Getting Involved
-==================
-
-A good place for interested contributors is the `Clangd developer mailing list
-<http://lists.llvm.org/mailman/listinfo/clangd-dev>`_. For discussions with the
-broader community on topics not only related to Clangd, use
-`Clang developer mailing list
-<http://lists.llvm.org/mailman/listinfo/cfe-dev>`_.
-If you're also interested in contributing patches to :program:`Clangd`, take a
-look at the `LLVM Developer Policy
-<http://llvm.org/docs/DeveloperPolicy.html>`_ and `Code Reviews
-<http://llvm.org/docs/Phabricator.html>`_ page. Contributions of new features
-to the `Language Server Protocol
-<https://github.com/Microsoft/language-server-protocol>`_ itself would also be
-very useful, so that :program:`Clangd` can eventually implement them in a
-conforming way.
+:orphan:

Modified: clang-tools-extra/branches/release_80/docs/clangd/index.rst
URL: http://llvm.org/viewvc/llvm-project/clang-tools-extra/branches/release_80/docs/clangd/index.rst?rev=354997&r1=354786&r2=354997&view=diff
==============================================================================
--- clang-tools-extra/branches/release_80/docs/clangd/index.rst (original)
+++ clang-tools-extra/branches/release_80/docs/clangd/index.rst Wed Feb 27 08:18:46 2019
@@ -1,180 +1,27 @@
-============
-Clangd
-============
-
-.. contents::
+======
+clangd
+======
 
 .. toctree::
    :maxdepth: 1
 
-:program:`Clangd` is an implementation of the `Language Server Protocol
-<https://github.com/Microsoft/language-server-protocol>`_ leveraging Clang.
-Clangd's goal is to provide language "smartness" features like code completion,
-find references, etc. for clients such as C/C++ Editors.
-
-Using Clangd
-==================
-
-:program:`Clangd` is not meant to be used by C/C++ developers directly but
-rather from a client implementing the protocol. A client would be typically
-implemented in an IDE or an editor.
-
-At the moment, `Visual Studio Code <https://code.visualstudio.com/>`_ is mainly
-used in order to test :program:`Clangd` but more clients are likely to make
-use of :program:`Clangd` in the future as it matures and becomes a production
-quality tool. If you are interested in trying :program:`Clangd` in combination
-with Visual Studio Code, you can start by `installing Clangd`_ or
-`building Clangd`_, then open Visual Studio Code in the clangd-vscode folder and
-launch the extension.
-
-Installing Clangd
-==================
-
-Packages are available for debian-based distributions, see the `LLVM packages
-page <https://apt.llvm.org/>`_. :program:`Clangd` is included in the
-`clang-tools` package.
-However, it is a good idea to check your distribution's packaging system first
-as it might already be available.
-
-Otherwise, you can install :program:`Clangd` by `building Clangd`_ first.
-
-Building Clangd
-==================
-
-You can follow the instructions for `building Clang
-<https://clang.llvm.org/get_started.html>`_ but "extra Clang tools" is **not**
-optional.
-
-Current Status
-==================
-
-Many features could be implemented in :program:`Clangd`.
-Here is a list of features that could be useful with the status of whether or
-not they are already implemented in :program:`Clangd` and specified in the
-Language Server Protocol. Note that for some of the features, it is not clear
-whether or not they should be part of the Language Server Protocol, so those
-features might be eventually developed outside :program:`Clangd` or as an
-extension to the protocol.
-
-+-------------------------------------+------------+----------+
-| C/C++ Editor feature                |  LSP       |  Clangd  |
-+=====================================+============+==========+
-| Formatting                          | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Completion                          | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Diagnostics                         | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Fix-its                             | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Go to Definition                    | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Signature Help                      | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Document Highlights                 | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Rename                              | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Source hover                        | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Find References                     | Yes        |   No     |
-+-------------------------------------+------------+----------+
-| Code Lens                           | Yes        |   No     |
-+-------------------------------------+------------+----------+
-| Document Symbols                    | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Workspace Symbols                   | Yes        |   Yes    |
-+-------------------------------------+------------+----------+
-| Syntax and Semantic Coloring        | No         |   No     |
-+-------------------------------------+------------+----------+
-| Code folding                        | No         |   No     |
-+-------------------------------------+------------+----------+
-| Call hierarchy                      | No         |   No     |
-+-------------------------------------+------------+----------+
-| Type hierarchy                      | No         |   No     |
-+-------------------------------------+------------+----------+
-| Organize Includes                   | No         |   No     |
-+-------------------------------------+------------+----------+
-| Quick Assist                        | No         |   No     |
-+-------------------------------------+------------+----------+
-| Extract Local Variable              | No         |   No     |
-+-------------------------------------+------------+----------+
-| Extract Function/Method             | No         |   No     |
-+-------------------------------------+------------+----------+
-| Hide Method                         | No         |   No     |
-+-------------------------------------+------------+----------+
-| Implement Method                    | No         |   No     |
-+-------------------------------------+------------+----------+
-| Gen. Getters/Setters                | No         |   No     |
-+-------------------------------------+------------+----------+
-
-Editor Integration
-==================
-
-Any full-featured Language Server Protocol Client implementation should work
-with :program:`Clangd`. This `list
-<https://langserver.org/#implementations-client>`_ contains information about
-extensions and plugins that are known to work for different editors.
-
-Vim Integration
----------------
-
-LanguageClient-neovim
-~~~~~~~~~~~~~~~~~~~~~
-
-One of the options of using :program:`Clangd` in :program:`vim` (or
-:program:`nvim`) is to utilize `LanguageClient-neovim
-<https://github.com/autozimu/LanguageClient-neovim>`_ plugin. Please see the
-`Clangd Wiki page
-<https://github.com/autozimu/LanguageClient-neovim/wiki/Clangd>`_ for
-instructions.
-
-VSCode Integration
-------------------
-
-:program:`VSCode` provides `vscode-clangd
-<https://marketplace.visualstudio.com/items?itemName=llvm-vs-code-extensions.vscode-clangd>`_
-which is published in Visual Studio Marketplace and can be installed direcetly
-from :program:`VSCode`.
-
-Emacs Integration
------------------
-
-:program:`Emacs` provides `lsp-mode <github.com/emacs-lsp/lsp-mode>`_ and
-`Eglot <https://github.com/joaotavora/eglot>`_ plugins for LSP integration.
-
-Project-wide Index
-==================
-
-By default :program:`Clangd` only has a view on symbols coming from files you
-are currently editing. You can extend this view to whole project by providing a
-project-wide index to :program:`Clangd`.
-
-There are two ways you can generate a project-wide index for clangd:
-
-- Passing experimental `-background-index` commandline argument, which will
-  incrementally build an index of projects that you work on and make use of that
-  in clangd automatically.
-- Generate an index file using `clangd-indexer
-  <https://github.com/llvm-mirror/clang-tools-extra/blob/master/clangd/indexer/IndexerMain.cpp>`_
-  Afterwards you can pass generated index file to clangd using
-  `-index-file=/path/to/index_file`.  *Note that clangd-indexer isn't included
-  alongside clangd in the standard clang-tools package. You will likely have to
-  build from source to use this option*
-
-Getting Involved
-==================
-
-A good place for interested contributors is the `Clangd developer mailing list
-<https://lists.llvm.org/mailman/listinfo/clangd-dev>`_. For discussions with the
-broader community on topics not only related to Clangd, use
-`Clang developer mailing list
-<https://lists.llvm.org/mailman/listinfo/cfe-dev>`_.
-If you're also interested in contributing patches to :program:`Clangd`, take a
-look at the `LLVM Developer Policy
-<https://llvm.org/docs/DeveloperPolicy.html>`_ and `Code Reviews
-<https://llvm.org/docs/Phabricator.html>`_ page. Contributions of new features
-to the `Language Server Protocol
-<https://github.com/Microsoft/language-server-protocol>`_ itself would also be
-very useful, so that :program:`Clangd` can eventually implement them in a
-conforming way.
+   Installation
+   Features
+
+What is clangd?
+===============
+
+clangd understands your C++ code and adds smart features to your editor: code
+completion, compile errors, go-to-definition and more.
+
+clangd is a language server that implements the `Language Server Protocol
+<https://github.com/Microsoft/language-server-protocol>`__; it can work with
+many editors through a plugin.  Here's Visual Studio Code with the clangd
+plugin, demonstrating code completion:
+
+.. image:: CodeCompletionInVSCode.png
+   :align: center
+   :alt: Code completion in VSCode
+
+clangd is based on the `Clang <https://clang.llvm.org>`__ C++ compiler, and is
+part of the `LLVM <https://llvm.org>`__ project.

Modified: clang-tools-extra/branches/release_80/docs/conf.py
URL: http://llvm.org/viewvc/llvm-project/clang-tools-extra/branches/release_80/docs/conf.py?rev=354997&r1=354996&r2=354997&view=diff
==============================================================================
--- clang-tools-extra/branches/release_80/docs/conf.py (original)
+++ clang-tools-extra/branches/release_80/docs/conf.py Wed Feb 27 08:18:46 2019
@@ -121,7 +121,7 @@ html_theme = 'haiku'
 # Add any paths that contain custom static files (such as style sheets) here,
 # relative to this directory. They are copied after the builtin static files,
 # so a file named "default.css" will overwrite the builtin "default.css".
-html_static_path = []
+html_static_path = ['_static']
 
 # If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
 # using the given strftime format.

Modified: clang-tools-extra/branches/release_80/docs/index.rst
URL: http://llvm.org/viewvc/llvm-project/clang-tools-extra/branches/release_80/docs/index.rst?rev=354997&r1=354996&r2=354997&view=diff
==============================================================================
--- clang-tools-extra/branches/release_80/docs/index.rst (original)
+++ clang-tools-extra/branches/release_80/docs/index.rst Wed Feb 27 08:18:46 2019
@@ -1,14 +1,9 @@
-.. Extra Clang Tools documentation master file, created by
-   sphinx-quickstart on Wed Feb 13 10:00:18 2013.
-   You can adapt this file completely to your liking, but it should at least
-   contain the root `toctree` directive.
-
 .. title:: Welcome to Extra Clang Tools's documentation!
 
 Introduction
 ============
 Welcome to the clang-tools-extra project which contains extra tools built using
-Clang's tooling API's.
+Clang's tooling APIs.
 
 .. toctree::
    :maxdepth: 1
@@ -25,7 +20,8 @@ Contents
    modularize
    pp-trace
    clang-rename
-   clangd
+   clangd/index
+   clangd/DeveloperDocumentation
    clang-doc
 
 




More information about the llvm-branch-commits mailing list