texlab doesn't autocomplete my acronyms #813
Labels
bug
Something isn't working
Comments
pfoerster
added a commit
that referenced
this issue
Nov 11, 2022
|
Thanks for the report. It looks like |
pfoerster
added
bug
|
Tried out from the latest github source and sorry... not yet. I still don't
see my acronyms...
BTW is there a way to make texlab return those candidates which literally
match what I already typed in?
I.e. I type doc and it returns everything that starts with 'doc' and not
'my-*do*-mat*c*'?
Thx, /PA
…On Fri, 11 Nov 2022 at 21:41, Patrick Förster ***@***.***> wrote:
Thanks for the report. It looks like texlab was missing some commands
from the acronym package.
Can you try f7b619d
<f7b619d>,
please?
—
Reply to this email directly, view it on GitHub
<#813 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZKU4DUUJ7MIAHJYOFETEDWH2VOXANCNFSM6AAAAAAR5OWO64>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
|
|
@paaguti Which command(s) are you using to define acronyms? Can you share one example definition, please?
Unfortunately, fuzzy matching is currently not (yet) configurable from the server side. |
|
I’m using the acronyms package with \acro & \acrodef. About fuzziness.. YES pls
Enviado desde mi iPhone
… El 12 nov 2022, a las 9:13, Patrick Förster ***@***.***> escribió:
@paaguti Which command(s) are you using to define acronyms? Can you share one example definition, please?
I.e. I type doc and it returns everything that starts with 'doc' and not
'my-do-matc'?
Unfortunately, fuzzy matching is currently not (yet) configurable from the server side. texlab is quite liberal in its matches because the client usually performs some filtering on its own afterwards but I can make it configurable (this should improve performance by a huge margin if you do not need the fuzziness).
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
pfoerster
added a commit
that referenced
this issue
Nov 12, 2022
pfoerster
removed
the
needs more info
Can you try again with 2c6bdf3, please? |
|
I don't know if the reason that I'm still not getting the \ac{} running is
because I'm on emacs and eglot... But sorry.. nothing yet :(
…On Sat, 12 Nov 2022 at 11:01, Patrick Förster ***@***.***> wrote:
I’m using the acronyms package with \acro & \acrodef.
Can you try again with 2c6bdf3
<2c6bdf3>,
please?
—
Reply to this email directly, view it on GitHub
<#813 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZKU4CXDGBL4BPXTIMSEA3WH5THLANCNFSM6AAAAAAR5OWO64>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
|
|
@paaguti Does the following example work on your machine?
|
|
No... it only gets my (ya)snippets: |
|
Hmm. Honestly, it looks like You can also try creating a log file using |
I don't know why it is analysing files in |
|
@paaguti Thanks for the log file.
The server is trying to build a dependency graph of all files that can be edited so it recursively walks up the directory tree to find a root file which includes one of the files of the current folder. |
installed with |
|
@paaguti Does this issue still occur with the newer versions? |
|
Hi Patrick, will test when I have time... currently overwhelmed with 'real
life' ;-)
I put it in my TODO...
Thanks for not forgetting, /PA
…On Sun, 12 Mar 2023 at 16:47, Patrick Förster ***@***.***> wrote:
@paaguti <https://github.com/paaguti> Does this issue still occur with
the newer versions?
—
Reply to this email directly, view it on GitHub
<#813 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZKU4GJD2WGG52CY2QJJQTW3XVZHANCNFSM6AAAAAAR5OWO64>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
|
|
Hi,
Woow... last release works smooth with no extra configuration on
Emacs/eglot. Eager to have time to fine tune it.
Thx, /PA
On Mon, 13 Mar 2023 at 07:19, Pedro Andres Aranda Gutierrez <
***@***.***> wrote:
… Hi Patrick, will test when I have time... currently overwhelmed with 'real
life' ;-)
I put it in my TODO...
Thanks for not forgetting, /PA
On Sun, 12 Mar 2023 at 16:47, Patrick Förster ***@***.***>
wrote:
> @paaguti <https://github.com/paaguti> Does this issue still occur with
> the newer versions?
>
> —
> Reply to this email directly, view it on GitHub
> <#813 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAZKU4GJD2WGG52CY2QJJQTW3XVZHANCNFSM6AAAAAAR5OWO64>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
|
netbsd-srcmastr
pushed a commit
to NetBSD/pkgsrc
that referenced
this issue
Apr 27, 2023
## [5.5.0] - 2023-04-16 ### Added - Allow optionally passing cursor position to `textDocument/build` request for use in forward search after building. Previously, the server had to guess the cursor position ([#475](latex-lsp/texlab#475)) - Add experimental `texlab.experimental.citationCommands` setting to allow extending the list of citation commands ([#832](latex-lsp/texlab#832)) - Add support for escaping placeholders in build arguments similar to forward search - Allow configuring completion matching algorithm ([#872](latex-lsp/texlab#872)) ### Fixed - Fix regression introduced in `v5.4.2` involving `texlab.cleanArtifacts` command. ## [5.4.2] - 2023-04-11 ### Fixed - Fix memory leak when editing documents over a long time ([#856](latex-lsp/texlab#856)) - Fix parsing parentheses in file paths ([#874](latex-lsp/texlab#874)) ## [5.4.1] - 2023-03-26 ### Fixed - Do not return symbols with empty names (e. g. sections without name) ([#870](latex-lsp/texlab#870)) - Repair `textDocument/formatting` request ([#871](latex-lsp/texlab#871)) ## [5.4.0] - 2023-03-12 ### Added - Add experimental settings to allow extending the list of special environments: - `texlab.experimental.mathEnvironments` - `texlab.experimental.enumEnvironments` - `texlab.experimental.verbatimEnvironments` - Add `texlab.changeEnvironment` workspace command ([#849](latex-lsp/texlab#849)) - Add `texlab.showDependencyGraph` workspace command ### Changed - Do not show caption or section names in label inlay hints ([#858](latex-lsp/texlab#858)) - Include more user-defined commands in command completion ### Fixed - Parse nested `\iffalse` blocks correctly ([#853](latex-lsp/texlab#853)) - Parse commands with multi-byte characters correctly ([#857](latex-lsp/texlab#857)) - Fix checking whether a document can be a root file ## [5.3.0] - 2023-02-25 ### Added - Allow filtering `textDocument/documentSymbols` using regular expressions specified via `texlab.symbols.allowedPatterns` and `texlab.symbols.ignoredPatterns` ([#851](latex-lsp/texlab#851)) ### Fixed - Do not use percent-encoded path when searching for PDF files during forward search ([#848](latex-lsp/texlab#848)) - Always return an empty list of code actions instead of returning "method not found" ([#850](latex-lsp/texlab#850)) ## [5.2.0] - 2023-01-29 ### Added - Include line numbers in build warnings when available ([#840](latex-lsp/texlab#840)) - Add `none` formatter to `texlab.latexFormatter` and `texlab.bibtexFormatter` options to allow disabling formatting ([#846](latex-lsp/texlab#846)) ### Fixed - Concatenate more than two lines of maximum length in build diagnostics ([#842](latex-lsp/texlab#842)) - Apply the correct range of references to labels when renaming ([#841](latex-lsp/texlab#841)) - Use `document` environment to detect root file instead of `\documentclass` ([#845](latex-lsp/texlab#845)) ## [5.1.0] - 2023-01-21 ### Added - Allow manually overriding the root directory using a `texlabroot`/`.texlabroot` marker file. See the wiki for more information. ([#826](latex-lsp/texlab#826), [#838](latex-lsp/texlab#838)) ### Deprecated - Deprecate `texlab.rootDirectory` setting in favor of `.texlabroot` files ### Fixed - Do not use `.git`, `.chktexrc`, `.latexmkrc` files/directories to determine the root directory ([#826](latex-lsp/texlab#826)) - Fix building documents without an explicit root directory ([#837](latex-lsp/texlab#837)) ## [5.0.0] - 2022-12-29 ### Changed - _BREAKING_: `texlab.rootDirectory` is now used as the folder path from which the compiler is executed relative to the main document. By default it is equal to `"."`. For more information, please visit the wiki. - Improve performance of completion by a huge margin due to a faster filtering method used internally - Do not discover project files beyond the provided workspace folders - Try to guess the root directory by checking for files such as `.latexmkrc` or `Tectonic.toml` if `texlab.rootDirectory` is not set ### Fixed - Update positions of reported build diagnostics when editing the affected line - Do not treat links to files as bidirectional by default. This prevents issues where `texlab` ends up compiling the wrong file in projects with shared files ([#806](latex-lsp/texlab#806), [#757](latex-lsp/texlab#757), [#679](latex-lsp/texlab#679)) - Fix coverage of directories which need to be watched for changes ([#502](latex-lsp/texlab#502), [#491](latex-lsp/texlab#491)) - Resolve links of the `import` package correctly - Use `filterText` of completion items when filtering internally ([#829](latex-lsp/texlab#829)) ## [4.3.2] - 2022-11-20 ### Fixed - Do not try to run the TeX engine on package files and fail the build instead ([#801](latex-lsp/texlab#801)) - Handle URIs with URL-encoded drive letters on Windows ([#802](latex-lsp/texlab#802)) - Parse BibTeX entries with unbalanced quotes correctly ([#809](latex-lsp/texlab#809)) - Provide completion for more acronym commands ([#813](latex-lsp/texlab#813)) - Fix parsing acronym definitions ([#813](latex-lsp/texlab#813)) ## [4.3.1] - 2022-10-22 ### Fixed - Do not crash with a stack overflow when trying to load packages with many internal dependencies ([#793](latex-lsp/texlab#793)) - Normalize drive letters of all document URIs - Fix parsing commands that take file paths as arguments ([#789](latex-lsp/texlab#789)) - Use the correct working directory and command line arguments when calling `latexindent` ([#645](latex-lsp/texlab#645)) - Fix publishing to CTAN ## [4.3.0] - 2022-09-25 ### Added - Add inlay hints for `\label{...}` ([#753](latex-lsp/texlab#753)) ### Fixed - Improve accuracy of the error locations reported by the TeX engine ([#738](latex-lsp/texlab#738)) - Reduce number of false positive errors reported by `texlab` ([#745](latex-lsp/texlab#745))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use
latexmkto recompile the project in parallel with Emacs (+eglot) as my editor. I was expecting that I would be able to get the acronyms defined in my project inside a\ac{}. But I don't see any of them.The text was updated successfully, but these errors were encountered: