What is the LSP Symbols tab for?

[Sturm0]

It doesn't seem to work on my system. The normal symbols tab works just fine.
Maybe is another case of what you mentioned on the other thread : "a result of some intermediate state of the plugin when proper Geany API for LSP was missing"

[techee]

What language server are you using? Symbols coming from the language server should appear there. The Symbols tab is populated by Geany's ctags-based parsers and has nothing to do with LSP. There's an open PR trying to unify the two here: geany/geany#3910

[Sturm0]

I'm using clangd
Ubuntu clangd version 18.1.3 (1ubuntu1)
Features: linux+grpc
Platform: x86_64-pc-linux-gnu

I attach some images just in case:

Maybe I have something misconfigured?

[techee]

Have you actually enabled LSP for your C your project? What does Tools->LSP Client->Server Initialize Responses say? clangd requires the compile_commands.json file inside the build directory of your project - its creation depends on what build system you use. Meson creates it for you after meson setup build, for autotools you have to use something like https://github.com/rizsotto/Bear.

[Sturm0]

I just generated the compile_commands.json as follows:
mkdir build; bear --output build/compile_commands.json -- make -C ./TPSP/src/
I have the following in my configuration:

[C]
# By default, clangd expects compile_commands.json inside the 'build' directory
# of your project. You can create it using either 'meson setup build' if your
# project uses meson or e.g. using:
#     mkdir build; bear --output build/compile_commands.json -- make
# if your project uses some other build tool (you need to install the bear tool
# first). The compile_commands.json file has to be manually regenerated when
# the build is modified in any way, such as a file is added/removed.
cmd=clangd
semantic_tokens_enable=true
initialization_options={"compilationDatabasePath":  "/home/Sturm0/Escritorio/UBA/arquitectura_y_organización_del_computador/tp-sp-null/build"}
formatting_options={ "tabSize": 4, "insertSpaces": false }
command_1_regex=Apply fix:.*
#rpc_log=stdout
#rpc_log_full=true
#show_server_stderr=true

Tools->LSP Client->Server Initialize Responses:

{

"clangd":
{
  "capabilities" : {
    "astProvider" : true,
    "callHierarchyProvider" : true,
    "clangdInlayHintsProvider" : true,
    "codeActionProvider" : {
      "codeActionKinds" : [
        "quickfix",
        "refactor",
        "info"
      ]
    },
    "compilationDatabase" : {
      "automaticReload" : true
    },
    "completionProvider" : {
      "resolveProvider" : false,
      "triggerCharacters" : [
        ".",
        "<",
        ">",
        ":",
        "\"",
        "/",
        "*"
      ]
    },
    "declarationProvider" : true,
    "definitionProvider" : true,
    "documentFormattingProvider" : true,
    "documentHighlightProvider" : true,
    "documentLinkProvider" : {
      "resolveProvider" : false
    },
    "documentOnTypeFormattingProvider" : {
      "firstTriggerCharacter" : "\n",
      "moreTriggerCharacter" : []
    },
    "documentRangeFormattingProvider" : true,
    "documentSymbolProvider" : true,
    "executeCommandProvider" : {
      "commands" : [
        "clangd.applyFix",
        "clangd.applyTweak"
      ]
    },
    "foldingRangeProvider" : true,
    "hoverProvider" : true,
    "implementationProvider" : true,
    "inactiveRegionsProvider" : true,
    "inlayHintProvider" : true,
    "memoryUsageProvider" : true,
    "referencesProvider" : true,
    "renameProvider" : true,
    "selectionRangeProvider" : true,
    "semanticTokensProvider" : {
      "full" : {
        "delta" : true
      },
      "legend" : {
        "tokenModifiers" : [
          "declaration",
          "definition",
          "deprecated",
          "deduced",
          "readonly",
          "static",
          "abstract",
          "virtual",
          "dependentName",
          "defaultLibrary",
          "usedAsMutableReference",
          "usedAsMutablePointer",
          "constructorOrDestructor",
          "userDefined",
          "functionScope",
          "classScope",
          "fileScope",
          "globalScope"
        ],
        "tokenTypes" : [
          "variable",
          "variable",
          "parameter",
          "function",
          "method",
          "function",
          "property",
          "variable",
          "class",
          "interface",
          "enum",
          "enumMember",
          "type",
          "type",
          "unknown",
          "namespace",
          "typeParameter",
          "concept",
          "type",
          "macro",
          "modifier",
          "operator",
          "bracket",
          "label",
          "comment"
        ]
      },
      "range" : false
    },
    "signatureHelpProvider" : {
      "triggerCharacters" : [
        "(",
        ")",
        "{",
        "}",
        "<",
        ">",
        ","
      ]
    },
    "standardTypeHierarchyProvider" : true,
    "textDocumentSync" : {
      "change" : 2,
      "openClose" : true,
      "save" : true
    },
    "typeDefinitionProvider" : true,
    "typeHierarchyProvider" : true,
    "workspaceSymbolProvider" : true
  },
  "serverInfo" : {
    "name" : "clangd",
    "version" : "Ubuntu clangd version 18.1.3 (1ubuntu1) linux+grpc x86_64-pc-linux-gnu"
  }
}
}

However, nothing appears in "LSP symbols". Maybe I configured that bear thing wrong, it's the first time I've used it (I didn't even know it existed)

[techee]

Hmm, interesting. So try the following - first check that document_symbols_enable=true is set in the [all] section. Then, uncomment the rpc_log=stdout line for the server, run Geany from the terminal and check the output in the terminal. You should see

[09:15:59.138] C --> S  req:   textDocument/documentSymbol
...
... <- various unrelated stuff in between
...
[09:15:59.829] C <-- S  resp:  textDocument/documentSymbol (691 ms)

This should appear every time you modify a C document - the client requests symbols from the server and the server sends the response back.

If you see this, you can try the full log by rpc_log_full=true - the result may be a little too verbose so you might need to redirect it to a file. In the file, you should see a full json communication between the client and the server. Please post the contents of both textDocument/documentSymbol requests and responses here so I can have a look at them. The response should contain the symbols that would appear in the LSP Symbols tab.

[Sturm0]

I just went to the all section and found this:

# Whether LSP should be used for displaying symbols in the sidebar. At the
# moment there is no Geany support for this feature so it can be left disabled
#as it doesn't work anyway.
document_symbols_enable=false

Maybe I have an old version and a newer version does support it.

[techee]

Maybe I have an old version and a newer version does support it.

Nope, it has always been set to true:

https://github.com/techee/geany-lsp/blame/master/lsp/data/lsp.conf

You've probably changed it while playing with the plugin.

[Sturm0]

But according to this it seems that it was "false" and it was in b017489 that you changed it to true and also changed the text above:
b017489

It also appears here as "false":
https://github.com/techee/geany-lsp/blame/c6c21460d88b2988cc17dbc3556029a6ec0b6d4d/lsp/data/lsp.conf

[techee]

Ah, OK, you are right - so it was probably the older version of the file in your case then.