| Age | Commit message (Collapse) | Author |
|---|
|
Change-Id: I9f583937da2cf49fc9013d9e36d63fff312ccb92
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/131495
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
Tested-by: Jenkins
|
|
Change-Id: I6f69439465b2968c5ab3900dbb9d5591c1c1f800
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/127360
Tested-by: Jenkins
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
|
|
It is for multi-root workspaces. Use hardcoded subdirectory paths
instead. Also see commit 411e8c24a289649797c679afc084113f7f61667a
author Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
date Fri Feb 12 12:29:18 2021 +0100
vscode: make it work better when srcdir=buildir and add mac lldb config
The problem it was addressing (VSCode unable to use second folder
name that points to the same location) is still unresolved upstream.
Fixing my mistake in commit 986e946d0cf3a6f61873efc09bab8c5e07c04f80
author Mike Kaganski <mike.kaganski@collabora.com>
date Wed Dec 15 14:19:31 2021 +0100
VSCode IDE integration: add safe path for pretty printers
This change reverts it partially.
Change-Id: I6a6db189f587288f6eee0d9a5051bd9d8cf5a055
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/127359
Tested-by: Mike Kaganski <mike.kaganski@collabora.com>
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
|
|
and also tell it to always add newline at EOF to be consistent with
traditional editors like vim and others
Change-Id: Iba7e9a3778229c72c06981bd95460980f8c4e9d6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/127333
Tested-by: Jenkins
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
|
|
Change-Id: Iefc9cb27f6ac84958a002e395bd631eb0590f022
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/127274
Tested-by: Jenkins
Reviewed-by: Julien Nabet <serval2412@yahoo.fr>
|
|
to be consistent with the other ide integrations and to take care of the
extra step of running "make vim-ide-integration" to create the
compile_commands.json file required by the vscode integration.
Not using the autogenerated file created by configure directly might
also spare some users from having their own additions overridden
Change-Id: Ibb269197dc84f607b28ddad03adc919864e0c040
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126860
Tested-by: Jenkins
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
|
|
Change-Id: I900ea4aef58fddb21f8bf3cb8264d9c8d9169a9c
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/126873
Tested-by: Jenkins
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
|
|
Change-Id: I7cc8efa94f75581d30047abf5c401b68741fb2a1
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/116342
Tested-by: Jenkins
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
|
|
Change-Id: I770d97b409cd42b4ef697fbde352cb147fa3a995
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/115807
Tested-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
|
|
Change-Id: I75b7104c98d187353bc3950ad51877f10ae04760
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/110838
Tested-by: Jenkins
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
|
|
Not having settings directly stored in .vscode directory in the
repository/having the files ignored there is a problem when you build in
a separate builddirectory and you regularly do a full reset of your
sourcedir using "git clean -fdx" and similar. If you had any
folder-settings, you'd lose them that way.
VS Code doesn't really have a mechanism to include and then extend
repository defaults, but it has three different tiers where settings are
pulled from: folder, workspace and user
For LibreOffice core repository there are no folder settings as our
.vscode is not populated (or at least it is not stable), a user can of
course place a settings.json or other configuration files in their
checkout, just with the "git clean" problem mentioned above.
This patch adds a workspace configuration - that file can be stored
anywhere and instead references the folders to use as configuration
items. If you want to add your own launch configuration or tasks: you
can just store it on your desktop, and can completely wipe out your
builddir as well as prune your srcdir - if you reuse the same paths for
your next build, you can simply reopen that workspace file and have all
your settings applied.
Having it part of the core repository and created by configure from the
template is thus just a convenience thing - it has a launch-in-debugger
rule and settings for code search/browsing that should be all that's
needed/all that's specific to LibreOffice at least.
Change-Id: I8625d83d0c30c2668b99ec672c651c3d35258ca5
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/107655
Reviewed-by: Ilmari Lauhakangas <ilmari.lauhakangas@libreoffice.org>
Reviewed-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
Tested-by: Christian Lohmaier <lohmaier+LibreOffice@googlemail.com>
|
